[Nut-upsuser] howto force shutdown if nut-snmp Communications lost

Heiko L. HL at fh-lausitz.de
Tue Dec 30 21:56:42 UTC 2014

>> Howto force shutdown if nut-snmp Communications lost?
>> My 1. suggestion was option DEADTIME, but seem to be information only. (s. below)
> DEADTIME expiration is a critical condition if the UPS is on battery when comms are lost, otherwise you are correct, it is only
> informative.
> What about a NOTIFYCMD script that checks for COMMBAD or NOCOMM? (passed in $NOTIFYTYPE) You will also need to set the EXEC
> flag on that event.

Thanks for you answer.


but i found any problems:

- nut send NOCOMM, but ups not reachable if switch rebooted
- nut configured 2 ups, but nut send NOCOMM if 1 ups down

Iam written 2 tools [1][2]

Details and variants see [3]

Infos are welcome.

regards Heiko

[1] http://www2.fh-lausitz.de/launic/comp/misc/ups/nut.notifycmd.sh
[2] http://www2.fh-lausitz.de/launic/comp/misc/ups/nut.pingups.sh
[3] http://www2.fh-lausitz.de/launic/comp/misc/ups/141230.nut.snmp.comm_lost.variants.txt

More information about the Nut-upsuser mailing list