Roger Price
2024-Mar-28 16:29 UTC
[Nut-upsuser] Heartbeat timer failure 15 minutes after startup
On Thu, 28 Mar 2024, Dan Grostick via Nut-upsuser wrote:> All three systems have a heartbeat-timer failure approximately 15 minutes > after starting NUT. No subsequent failures. Any ideas on what is happening?I've seen the timers: heartbeat.conf has two 300 sec timers, upssched.cmd looks like what is often called upssched.conf and has a 660 sec timer. So it looks as if the heartbeat has worked once, after 10 min. Do you have a file upssched.conf? I would expect upssched.cmd (perhaps upssched-cmd) to contain a script. Roger
Dan Grostick
2024-Mar-29 20:21 UTC
[Nut-upsuser] Heartbeat timer failure 15 minutes after startup
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. Dan ________________________________ From: Nut-upsuser <nut-upsuser-bounces+danpower2023=outlook.com at alioth-lists.debian.net> on behalf of Roger Price via Nut-upsuser <nut-upsuser at alioth-lists.debian.net> Sent: Thursday, March 28, 2024 12:29 PM To: Dan Grostick via Nut-upsuser <nut-upsuser at alioth-lists.debian.net> Subject: Re: [Nut-upsuser] Heartbeat timer failure 15 minutes after startup On Thu, 28 Mar 2024, Dan Grostick via Nut-upsuser wrote:> All three systems have a heartbeat-timer failure approximately 15 minutes > after starting NUT. No subsequent failures. Any ideas on what is happening?I've seen the timers: heartbeat.conf has two 300 sec timers, upssched.cmd looks like what is often called upssched.conf and has a 660 sec timer. So it looks as if the heartbeat has worked once, after 10 min. Do you have a file upssched.conf? I would expect upssched.cmd (perhaps upssched-cmd) to contain a script. Roger _______________________________________________ Nut-upsuser mailing list Nut-upsuser at alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://alioth-lists.debian.net/pipermail/nut-upsuser/attachments/20240329/1f9f6a44/attachment.htm> -------------- next part -------------- A non-text attachment was scrubbed... Name: upssched.conf Type: application/octet-stream Size: 1230 bytes Desc: upssched.conf URL: <http://alioth-lists.debian.net/pipermail/nut-upsuser/attachments/20240329/1f9f6a44/attachment.obj> -------------- next part -------------- A non-text attachment was scrubbed... Name: upssched-cmd Type: application/octet-stream Size: 5450 bytes Desc: upssched-cmd URL: <http://alioth-lists.debian.net/pipermail/nut-upsuser/attachments/20240329/1f9f6a44/attachment-0001.obj>
Roger Price
2024-Mar-29 21:06 UTC
[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.If you speed up the heartbeat by reducing the timers in heartbeat.conf from 300 to 150, and the timer in upssched.conf from 660 to 360, does the failure still occcur after 15 minutes? Roger
Apparently Analagous Threads
- Heartbeat timer failure 15 minutes after startup
- Heartbeat timer failure 15 minutes after startup
- Heartbeat timer failure 15 minutes after startup
- Heartbeat timer failure 15 minutes after startup
- Dummy-ups cycles between online and onbatt every 5 minutes. (Nut 2.8.0)