[Nut-upsuser] is POWERDOWNFLAG for primary or secondaries?

[Dan Langille]

Hello,

After a recent upgrade from 2.8.2 to 2.8.4, a restart of upsmon gave this message:


---
% sudo service nut_upsmon restart
Network UPS Tools upsmon 2.8.4 release
Starting nut_upsmon.
Network UPS Tools upsmon 2.8.4 release
UPS: ups04 at gw01.int.example.org (secondary) (power value 1)
UPS: heartbeat (monitoring only)
No POWERDOWNFLAG value was configured in /usr/local/etc/nut/upsmon.conf!
POWERDOWNFLAG should be a path to file that is normally writeable for root user, and remains at least readable late in shutdown after all unmounting completes.
---


Background: The UPS is connected to gw01 mentioned above; the above host is a secondary.

Reading docs, it seems that POWERDOWNFLAG is meant for primaries, not secondaries.

'and a POWERDOWNFLAG if this machine is a "primary" system connected to the UPS and drives its late-shutdown power-off command in case of an emergency.'

re: https://networkupstools.org/docs/man/upsmon.conf.html


Am I doing this wrong? This is my secondary configuration


---
[20:29 r730-01 dvl /usr/local/etc/nut] % sudo cat upsmon.conf.6958.2025-04-02 at 22:46:09~ 
# Ansible managed

MONITOR ups04 at gw01.int.example.org    1 r730-01         myrealpassword secondary
MONITOR heartbeat                     0 local-heartbeat myrealpassword primary
SHUTDOWNCMD /sbin/shutdown -h +0
NOTIFYCMD ONLINE EXEC
NOTIFYCMD ONBATT EXEC
NOTIFYCMD /usr/local/sbin/upssched
---


The line I later added, and which silenced the messages, is:

POWERDOWNFLAG /var/run/nut-killpower

I chose that line because that directory is cleared upon OS restart:

re https://networkupstools.org/docs/user-manual.chunked/ar01s06.html 

"... /etc/killpower, or preferably be /var/run/nut/killpower or /run/nut/killpower in a temporary file system that disappears after reboot"

Thank you.

-- 
  Dan Langille
  dan at langille.org