Hi,
Does anyone know if there is something in Proxmox that would prevent NUT from work correctly?
I've got a set of config files i usually drop onto systems, that i adjust slightly dependent on needs, but for some reason they just do not want to work with Proxmox systems.
I do get the note in the log about the system now being on battery power, but then it literally does nothing.
So the systems are definitely able to see the state changes from the system hosting the UPS.
There's also nothing untoward in the log for
To be clear on my objective - each system shuts down on a different % level.
If anyone can shed some light on what's going on, it would be much appreciated.
Thanks!
---
Below are my current nut configs, for reference -
nut.conf
ups.conf - note, set at 90 for testing purposes
upsmon.conf - note, FINALDELAY set to 5 for testing
upssched-cmd
upssched.conf
I have also tested upssched.conf with
Does anyone know if there is something in Proxmox that would prevent NUT from work correctly?
I've got a set of config files i usually drop onto systems, that i adjust slightly dependent on needs, but for some reason they just do not want to work with Proxmox systems.
I do get the note in the log about the system now being on battery power, but then it literally does nothing.
So the systems are definitely able to see the state changes from the system hosting the UPS.
There's also nothing untoward in the log for
service nut-monitor statusother than a "Could not find PID file to see if previous upsmon instance is already running!" noteTo be clear on my objective - each system shuts down on a different % level.
If anyone can shed some light on what's going on, it would be much appreciated.
Thanks!
---
Below are my current nut configs, for reference -
nut.conf
Code:
MODE=netclientups.conf - note, set at 90 for testing purposes
Code:
battery.charge.low = 90upsmon.conf - note, FINALDELAY set to 5 for testing
Code:
RUN_AS_USER root
MONITOR ups01@1.2.3.4 1 client supersecret slave
MINSUPPLIES 1
SHUTDOWNCMD "/sbin/shutdown -h now"
NOTIFYCMD /usr/sbin/upssched
POWERDOWNFLAG /etc/killpower
POLLFREQ 15
POLLFREQALERT 5
#HOSTSYNC 15
RBWARNTIME 43200
NOCOMMWARNTIME 120
DEADTIME 45
FINALDELAY 5
# Notification Messages
NOTIFYMSG ONLINE "UPS %s on line power"
NOTIFYMSG ONBATT "UPS %s on battery"
NOTIFYMSG LOWBATT "UPS %s battery is low"
NOTIFYMSG FSD "UPS %s: forced shutdown in progress"
NOTIFYMSG COMMOK "Communications with UPS %s established"
NOTIFYMSG COMMBAD "Communications with UPS %s lost"
NOTIFYMSG SHUTDOWN "Auto logout and shutdown proceeding"
NOTIFYMSG REPLBATT "UPS %s battery needs to be replaced"
NOTIFYMSG NOCOMM "UPS %s is unavailable"
NOTIFYMSG NOPARENT "upsmon parent process died - shutdown impossible"
# Notification Actions
NOTIFYFLAG ONLINE SYSLOG+WALL+EXEC
NOTIFYFLAG ONBATT SYSLOG+WALL+EXEC
NOTIFYFLAG LOWBATT SYSLOG+WALL
NOTIFYFLAG FSD SYSLOG+WALL+EXEC
NOTIFYFLAG COMMOK SYSLOG+WALL+EXEC
NOTIFYFLAG COMMBAD SYSLOG+WALL+EXEC
NOTIFYFLAG SHUTDOWN SYSLOG+WALL+EXEC
NOTIFYFLAG REPLBATT SYSLOG+WALL
NOTIFYFLAG NOCOMM SYSLOG+WALL+EXEC
NOTIFYFLAG NOPARENT SYSLOG+WALLupssched-cmd
Code:
#!/bin/sh
case $1 in
onbatt)
logger -t upssched-cmd "UPS running on battery"
;;
earlyshutdown)
logger -t upssched-cmd "UPS on battery too long, early shutdown"
/usr/sbin/upsmon -c fsd
;;
shutdowncritical)
logger -t upssched-cmd "UPS on battery critical, forced shutdown"
/usr/sbin/upsmon -c fsd
;;
upsgone)
logger -t upssched-cmd "UPS has been gone too long, can't reach"
;;
*)
logger -t upssched-cmd "Unrecognized command: $1"
;;
esacupssched.conf
Code:
CMDSCRIPT /etc/nut/upssched-cmd
PIPEFN /etc/nut/upssched.pipe
LOCKFN /etc/nut/upssched.lockAT 90% "shutdowncritical"