Thanks for your replies
Tried putting killpower file (with upsmon-shutdown-file string) in /run/nut/killpower since upsmon.conf has :- POWERDOWNFLAG "/run/nut/killpower" and nothing happens - even tried in /etc/killpower and adjusted POWERDOWNFLAG Its as though only a part of the nut "system" is working, especially on the primary (no syslogs, no walls, no calling of the upssched-cmd script (no logs)) I'm sure some of the errors shown in the /var/log/messages are possible problems ? Aug 10 12:46:29 ipfire usbhid-ups[2155]: Listening on socket /var/state/ups/usbhid-ups-apc Aug 10 12:46:29 ipfire usbhid-ups[2159]: Startup successful Aug 10 12:46:29 ipfire usbhid-ups[2159]: upsnotify: notify about state NOTIFY_STATE_READY_WITH_PID with libsystemd: was requested, but not running as a service unit now, will not spam more about it Aug 10 12:46:29 ipfire usbhid-ups[2159]: upsnotify: failed to notify about state NOTIFY_STATE_READY_WITH_PID: no notification tech defined, will not spam more about it Aug 10 12:46:29 ipfire usbhid-ups[2159]: upsnotify: logged the systemd watchdog situation once, will not spam more about it Aug 10 12:46:29 ipfire upsd[2160]: listening on 0.0.0.0 port 3493 Aug 10 12:46:29 ipfire upsd[2160]: Connected to UPS [apc]: usbhid-ups-apc Aug 10 12:46:29 ipfire upsd[2160]: Found 1 UPS defined in ups.conf Aug 10 12:46:29 ipfire usbhid-ups[2159]: sock_connect: enabling asynchronous mode (auto) Aug 10 12:46:29 ipfire upsd[2161]: Startup successful Aug 10 12:46:29 ipfire upsd[2161]: upsnotify: notify about state NOTIFY_STATE_READY_WITH_PID with libsystemd: was requested, but not running as a service unit now, will not spam more about it Aug 10 12:46:29 ipfire upsd[2161]: upsnotify: failed to notify about state NOTIFY_STATE_READY_WITH_PID: no notification tech defined, will not spam more about it Aug 10 12:46:29 ipfire upsd[2161]: upsnotify: logged the systemd watchdog situation once, will not spam more about it Aug 10 12:46:29 ipfire upsmon[2163]: Startup successful Aug 10 12:46:29 ipfire upsmon[2163]: OS user = not found ________________________________________ From: Nut-upsuser <[email protected]> on behalf of Robert Nichols via Nut-upsuser <[email protected]> Sent: Monday, August 10, 2026 02:52 To: [email protected] <[email protected]> Subject: Re: [Nut-upsuser] UPS not shutting down, no syslogs; no wall messages plus other problems On 8/9/26 09:24, Greg Troxel via Nut-upsuser wrote: > The secondary shut down due to lack of comms from primary. > > The primary appears to have noticed it should shutdown but something is > not right. > > Generally the system up/down scripts need to notice that the killpower > flag file has been set. That requires a lot of things, including that > the filesystem it is written to have the right permissions and that it > still be mounted. > > You should be able to test by first getting a shell as user nut, and > then "touch /var/run/nut/killpower". If that doesn't work, figure out > why and fix that before continuing. Then run the shutdown command > manually. According to some hard-to-find docs, that file will be ignored unless it contains the magic string "upsmon-shutdown-file" (without the quotes, of course). That string is found in the file /usr/sbin/upsmon. -- Bob Nichols "NOSPAM" is really part of my email address. Do NOT delete it. _______________________________________________ Nut-upsuser mailing list [email protected] https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser _______________________________________________ Nut-upsuser mailing list [email protected] https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser
