[Nut-upsuser] Belkin USB UPS Not Turning Off

David White whitedavidp at yahoo.com
Wed Jan 1 19:49:48 GMT 2020

On 1/1/2020 2:21 AM, Roger Price wrote:
> On Tue, 31 Dec 2019, David White wrote:
>> ... But it did not actually turn off the UPS at all. The UPS kept
>> beeping and I had to turn it off manually.
>> I thought that NUT would handle this. But perhaps it cannot for my
>> unit? Or perhaps I have things improperly configured? Any suggestions?
>> Thanks and happy new year!
>>         ########### /etc/nut/upsmon.conf ###########
>> MONITOR belkinusb at localhost 1 local_mon ********* master
>> SHUTDOWNCMD "/sbin/shutdown -h +0"
>> NOTIFYCMD /home/android/nutShutdown.sh
>> POWERDOWNFLAG /etc/killpower
>> NOTIFYMSG ONBATT        "UPS %s on battery"
>>         ########### /etc/nut/upssched.conf ###########
>> CMDSCRIPT /bin/upssched-cmd
> Happy New Year David!, The command "/sbin/upsdrvctl shutdown" turns off
> the UPS unit, but this is not being executed.  How do you plan to shut
> down on power failure?  Will you wait for upsd's [LB] status or use a
> timer?  The simplest is to wait for [LB], but the upsmon.conf contains
> no declarations for NOTIFYFLAG LOWBATT.
> The script /home/android/nutShutdown.sh will be called when wall power
> fails, but nut-report was unable to show its contents.  Should
> nutShutdown.sh perform the system shutdown?
> Perhaps a more complete set of NOTIFYFLAG and NOTIFYMSG declarations
> will make things clearer.  I would also recommend adding the SYSLOG
> option to the declarations.
> Do you shutdown using systemd?
> Roger

Hi Roger and, as always, thanks!

I really do not want to wait very long before shutting down things on 
this UPS. What I think I am doing (or at least trying to do) is to 
execute a script on the host machine when the UPS is detected by NUT to 
be on battery power.

That script sleeps 20 seconds to ensure that this was not just a power 
blip (which happens here often) but a real power outage. After 20 
seconds, the script checks the UPS status via upsc and if it is no 
longer OB, power is deemed restored and the script exits.

If, after 20 seconds, UPS status remains OB then the event is deemed a 
true power outage and I want to shut down what I can cleanly. To do 
this, the script issues remote shutdown commands to a set of network 
connected devices also living on this UPS (but sadly not able to run 
NUT). As its final step, it issues a command to shut the host machine down.

It seems from what you say above, I need to issue "/sbin/upsdrvctl 
shutdown" in there somewhere - obviously before I shut the host machine 
down. I will have to test this to see exactly what that command does. 
When run w/out arguments, the usage says shutdown shuts down UPS 
drivers. I am not clear if this means that the UPS itself will be 
powered off or if simply NUT is shutdown.


More information about the Nut-upsuser mailing list