pae-id/Proxomox - NUT Client.md

Last active February 26, 2025 15:00

Star (42) You must be signed in to star a gist
Fork (15) You must be signed in to fork a gist

Select an option

Learn more about clone URLs
Clone this repository at <script src="https://gist.github.com/pae-id/ab99feb66822dc1a975c.js"></script>
Save pae-id/ab99feb66822dc1a975c to your computer and use it in GitHub Desktop.

Download ZIP

Proxomox - NUT Client.md

Raw

Proxomox - NUT Client.md

Configuring Proxmox VE node as client for remote NUT server

Network UPS Tools User Manual

apt-get install nut

Edit /etc/nut/nut.conf:

MODE=netclient

Edit /etc/nut/upsmon.conf: MONITOR <system> <powervalue> <username> <password> ("master"|"slave"):

MONITOR [email protected] 1 upsmon password slave

Start monitoring:

upsmon start

To check UPS status: upsc <name> for direct attached units or upsc <name>@<address> for remote

upsc [email protected]

So i did test over the cmd : upsmon -c fsd , and the proxmox box as client do shutdown. But if communication fail it don't do anything, it just if the ups get the battery dead. I do see other config as :

nano /etc/nut/upsmon.conf

MONITOR [email protected] 1 upsmon secret slave

MINSUPPLIES 1
SHUTDOWNCMD "/sbin/shutdown -h"
NOTIFYCMD /usr/sbin/upssched
POLLFREQ 2
POLLFREQALERT 1
HOSTSYNC 15
DEADTIME 15
# MAXAGE 24   //mean?
POWERDOWNFLAG /etc/killpower

# Notification message:
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 events : go syslog - broadcast msg - exec .script?
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+WALL

RBWARNTIME 43200
NOCOMMWARNTIME 600
FINALDELAY 5

-=-=-=-=-
sudo nano /etc/nut/upssched.conf

# scheduler to shutdown
CMDSCRIPT /etc/nut/upssched-cmd
PIPEFN /etc/nut/upssched.pipe
LOCKFN /etc/nut/upssched.lock

# timer in sec
AT ONBATT * START-TIMER onbatt 30
AT ONLINE * CANCEL-TIMER onbatt online
AT ONBATT * START-TIMER earlyshutdown 30
AT LOWBATT * EXECUTE onbatt
AT COMMBAD * START-TIMER commbad 30
AT COMMOK * CANCEL-TIMER commbad commok
AT NOCOMM * EXECUTE commbad
AT SHUTDOWN * EXECUTE powerdown
# AT SHUTDOWN * EXECUTE powerdown

is a script is needed ? Do you have an example or you just used nut at when no more power in the ups, then the proxmox box go for shutoff ?

Author

pae-id commented May 27, 2023

No other scripts in my setup. It is a graceful shutdown including all VMs.
Client performs action based on server configuration.
My server is NUT service inside TrueNAS VM. It is configured to shutdown after N minutes of ONBATT state.

If communication is lost NUT should spam you with e-mails until it is fixed, but there must be a valid account configured for each system's e-mail MTA (e.g. postfix)

pae-id/Proxomox - NUT Client.md

Select an option

No results found