Arch Linux

ipreston

Member

Registered: 2020-10-23

Posts: 1

nut-monitor service times out on one machine

Hi everyone,

I have two machines running Arch. I'm trying to get both of them to monitor a NUT server running off my synology NAS. I've installed nut on both of them and added a monitor line to /etc/nut/upsmon.conf. For both machines if I run upsc ups@<the synology address> I get a response back with details on the UPS status. On one machine I've enabled and started nut-monitor.service with no problem. On the other machine it fails to start with a timeout. I'm completely stumped what the difference could be. I wrote the configuration as an ansible playbook so I can't think of any obvious reason they'd be configured differently. The only difference between the machines that I can think of is that the one that's failing is using the lts kernel and the other isn't, but that seems like a red herring. Both have nut 2.7.4-3 installed. The errors from starting the service don't give me any clues, at least not in the places I'm checking.

When I try and start the service I get this:

Job for nut-monitor.service failed because a timeout was exceeded.
See "systemctl status nut-monitor.service" and "journalctl -xe" for details.

the status output is the following:

● nut-monitor.service - Network UPS Tools - power device monitor and shutdown controller
     Loaded: loaded (/usr/lib/systemd/system/nut-monitor.service; enabled; vendor preset: disabled)
     Active: failed (Result: timeout) since Wed 2020-12-30 17:40:09 America; 7min ago
    Process: 52079 ExecStart=/usr/bin/upsmon (code=exited, status=0/SUCCESS)

Dec 30 17:38:39 mars systemd[1]: nut-monitor.service: Can't open PID file /run/nut/upsmon.pid (yet?) after start: Operation not permitted
Dec 30 17:38:39 mars upsmon[52079]: fopen /run/nut/upsmon.pid: No such file or directory
Dec 30 17:38:39 mars upsmon[52079]: UPS: ups@laconia (slave) (power value 1)
Dec 30 17:38:39 mars upsmon[52079]: Using power down flag file /etc/killpower
Dec 30 17:38:39 mars upsmon[52080]: Startup successful
Dec 30 17:38:39 mars upsmon[52081]: writepid: fopen /run/nut/upsmon.pid: No such file or directory
Dec 30 17:40:09 mars systemd[1]: nut-monitor.service: start operation timed out. Terminating.
Dec 30 17:40:09 mars upsmon[52081]: Signal 15: exiting
Dec 30 17:40:09 mars systemd[1]: nut-monitor.service: Failed with result 'timeout'.
Dec 30 17:40:09 mars systemd[1]: Failed to start Network UPS Tools - power device monitor and shutdown controller.

I've done a ton of googling about the /run/nut/upsmon.pid issue and haven't found anything useful. A couple of very old posts talking about needing to update to an earlier version of nut than I'm running.

Here's the journalctl output:

Dec 30 17:38:39 mars upsmon[52080]: Startup successful
Dec 30 17:38:39 mars upsmon[52081]: writepid: fopen /run/nut/upsmon.pid: No such file or directory
Dec 30 17:40:09 mars systemd[1]: nut-monitor.service: start operation timed out. Terminating.
Dec 30 17:40:09 mars upsmon[52081]: Signal 15: exiting
Dec 30 17:40:09 mars systemd[1]: nut-monitor.service: Failed with result 'timeout'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ The unit nut-monitor.service has entered the 'failed' state with result 'timeout'.
Dec 30 17:40:09 mars systemd[1]: Failed to start Network UPS Tools - power device monitor and shutdown controller.

I'm at a loss here. Any suggestions for things to try? Additional information I can provide to help troubleshoot?

Thanks in advance.