Cursorily, your two LISTEN directives for same IP address can be
conflicting (one grabs the port another one wants)... And/or some service
dependencies (After/Wants/Requires in systemd) in your package are not set
up to start nut-server after surely having passed the network-online
milestone and
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
I have 3 Raspberry Pi NUT 2.8.1 systems running PI OS. (Debian 11 and 12)
All three systems have a heartbeat-timer failure approximately 15 minutes after
starting NUT. No subsequent failures. Any ideas on what is happening?
Dan
heartbeat.conf
Description: heartbeat.conf
upssched.cmd
