OPNsense Forum
English Forums => General Discussion => Topic started by: HFsi on July 02, 2018, 08:39:52 pm
-
Hi all!
I´ve just installed nut plugin, my UPS is well detected, but the service fails to start.
Here is the log:
Jul 2 15:18:23 root: /usr/local/etc/rc.d/nut_upsmon: WARNING: failed to start nut_upsmon
Jul 2 15:18:23 root: /usr/local/etc/rc.d/nut: WARNING: failed precmd routine for nut
Jul 2 15:15:10 kernel: ugen0.2: <American Power Conversion Back-UPS RS 900G FW879.L4 .I USB FWL4> at usbus0
Any tips for debugging?
Thanks!
-
Is this a production machine or can it be rebootet some time?
-
One thing that tripped me up when I first used Nut was that I had spaces in the UPS name, which I learned doesn’t work. Do you happen to have any spaces in your UPS name?
-
Really? I thought I put a validator on this or did you start with a Dev version?
-
One thing that tripped me up when I first used Nut was that I had spaces in the UPS name, which I learned doesn’t work. Do you happen to have any spaces in your UPS name?
Fixed my problem. Thanks.
-
I started with the Dev version.
-
I already saw there's no validator. I'll add one so a space and special chars are denied.
-
My UPS name is "BR900".
I get this on System: Log Files: Configd
configd.py: [563d2a24-c52f-4f97-a982-4e296ea97c5f] Script action failed with Command '/usr/local/bin/upsc 'BR900@127.0.0.1'' returned non-zero exit status 1 at Traceback (most recent call last): File "/usr/local/opnsense/service/modules/processhandler.py", line 479, in execute stdout=output_stream, stderr=error_stream) File "/usr/local/lib/python2.7/subprocess.py", line 190, in check_call raise CalledProcessError(retcode, cmd) CalledProcessError: Command '/usr/local/bin/upsc 'BR900@127.0.0.1'' returned non-zero exit status 1
But the UPS is found
-
What happens when you execute this command via CLI?
-
Well, I finally gave up on this because I made it work through Home Assistant...
Now comes the part of the automation to shutdown all my devices in the case of a power shortage
-
Then you should configure OPNsense as netclient to shutdown itself
-
Thanks for the tip, my approach was more difficult
-
:) :)
Will you provide some detail? Version? Error? UPS model?
-
I´m now using NUT 1.3 as netclient and works fine, but I don´t see any configuration for shutting down OPN
-
I´m now using NUT 1.3 as netclient and works fine, but I don´t see any configuration for shutting down OPN
Uhm .. me too .. I forgot some parts in templating, sorry.
-
Finally I get it done through an API Call