I upgraded to 2.8.2 and this continues to happen on all three installations.
Once the initial failure occurs, it doesn't occur again. It seems as if the
initial value for heart-beat-timer isn't being set... Once it fails, it appears
that it is being set.
upsd is running.
----------------------
heartbeat.conf
ups.status: OL
TIMER 300
ups.status: OB
TIMER 300
---------------------------
root@rpinut:/etc/nut# systemctl status nut-server
● nut-server.service - Network UPS Tools - power devices information server
Loaded: loaded (/lib/systemd/system/nut-server.service; disabled; preset:
enabled)
Active: active (running) since Sun 2024-08-04 03:44:46 EDT; 1h 56min ago
Process: 545869 ExecStartPre=/usr/bin/systemd-tmpfiles --create
/usr/lib/tmpfiles.d/nut-common-tmpfiles.conf (code=exited, status=0/SUCCESS)
Process: 545871 ExecStartPost=/bin/grep -E Units|Max open files
/proc/${MAINPID}/limits (code=exited, status=0/SUCCESS)
Main PID: 545870 (upsd)
Tasks: 1 (limit: 9247)
CPU: 749ms
CGroup: /system.slice/nut-server.service
└─545870 /usr/sbin/upsd -F
Aug 04 03:44:46 rpinut upsd[545870]: Connected to UPS [ups]: usbhid-ups-ups
Aug 04 03:44:46 rpinut upsd[545870]: Found 2 UPS defined in ups.conf
Aug 04 03:44:46 rpinut upsd[545870]: Running as foreground process, not saving
a PID file
Aug 04 03:44:46 rpinut nut-server[545870]: Running as foreground process, not
saving a PID file
Aug 04 03:44:46 rpinut nut-server[545870]: upsnotify: failed to notify about
state 2: no notification tech defined, will not spam more about it
Aug 04 03:44:46 rpinut upsd[545870]: upsnotify: failed to notify about state 2:
no notification tech defined, will not spam more about it
Aug 04 03:44:47 rpinut nut-server[545870]: User [email protected]
logged into UPS [ups]
Aug 04 03:44:47 rpinut upsd[545870]: User [email protected] logged into
UPS [ups]
Aug 04 03:44:47 rpinut nut-server[545870]: User [email protected] logged
into UPS [heartbeat]
Aug 04 03:44:47 rpinut upsd[545870]: User [email protected] logged into
UPS [heartbeat]
----------------------------
root@rpinut:/etc/nut# upsc -L
ups: APS BR1600G UPS
heartbeat: Heart beat verfication of NUT
----------------------
root@rpinut:/etc/nut# ps -e|grep upsd
545747 ? 00:00:00 cupsd
545870 ? 00:00:00 upsd
-------------------------
________________________________
From: Nut-upsuser
<nut-upsuser-bounces+danpower2023=outlook....@alioth-lists.debian.net> on
behalf of Roger Price <[email protected]>
Sent: Friday, March 29, 2024 6:15 PM
To: Dan Grostick via Nut-upsuser <[email protected]>
Subject: Re: [Nut-upsuser] Heartbeat timer failure 15 minutes after startup
On Fri, 29 Mar 2024, Dan Grostick wrote:
> It is consistently happening 14-15 minutes after starting. Please see attached
> upssched-cmd and upssched.conf. I don't have a upssched.cmd. The binary
> upssched is used.
After the heartbeat failure, is upsd still running? Does the command "upsc -L"
report the UPS's? If you use systemd, what does the command "systemctl status
nut-server" report?
Roger
_______________________________________________
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
