On Sun, 29 Aug 2021, Nathan Dehnel via Nut-upsuser wrote:
The systemd service fails even though the output seems to indicate that nut-monitor is communicating successfully with the UPS. Aug 16 23:45:52 gentoodesktop upsmon[1944]: 12.457065 Logged into UPS heartbeat@localhost Aug 16 23:45:52 gentoodesktop upsmon[1944]: 12.457104 pollups: heartbeat@localhost Aug 16 23:45:52 gentoodesktop upsmon[1944]: 12.457110 get_var: heartbeat@localhost / status Aug 16 23:45:52 gentoodesktop upsmon[1944]: 12.457142 parse_status: [OL] Aug 16 23:45:52 gentoodesktop upsmon[1944]: 12.457148 parsing: [OL] Aug 16 23:45:52 gentoodesktop upsmon[1944]: 12.457151 ups_on_line: heartbeat@localhost (first time) Aug 16 23:45:52 gentoodesktop upsmon[1944]: 12.457154 Current power value: 1 Aug 16 23:45:52 gentoodesktop upsmon[1944]: 12.457157 Minimum power value: 1
It's not central to your problem, but a heartbeat should have a power value of 0 in the MONITOR declaration.
Aug 16 23:47:12 gentoodesktop systemd[1]: nut-monitor.service: start operation timed out. Terminating. Aug 16 23:47:12 gentoodesktop upsmon[1944]: 91.852466 Signal 15: exiting Aug 16 23:47:12 gentoodesktop upsmon[1944]: 91.852486 Dropping connection to UPS [tripplite1@pfsense] Aug 16 23:47:12 gentoodesktop upsmon[1944]: 91.852556 Dropping connection to UPS [heartbeat@localhost] Aug 16 23:47:12 gentoodesktop upsmon[1944]: Network UPS Tools upsmon 2.7.4 Aug 16 23:47:12 gentoodesktop systemd[1]: nut-monitor.service: Failed with result 'timeout'.
Where does this systemd timer come from? Could we see the file nut-monitor.service ?
Roger _______________________________________________ Nut-upsuser mailing list Nut-upsuser@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser
