NUT suddenly stops working every app. 6 minutes

j.koopmann

@dennypage said in NUT suddenly stops working every app. 6 minutes:

This is not related to usbhid-ups. The protocol error in question is between upsmon and upsd. usbhid-ups does not communicate directly with upsmon.

Agreed.

If you see this again, run upsc, which also talks directly with upsd, and confirm that you can see values for the UPS.

Good hint. Thanks. Will do!

In general, this is indicative of a bug in NUT itself. What version of pfSense and NUT are you running? Do you see any other log entries for upsd or upsmon in the system log?

Again: Agreed and my thesis from the start. :-)

24.11-RELEASE
nut package 2.8.2_4

dennypage

@j-koopmann said in NUT suddenly stops working every app. 6 minutes:

Again: Agreed and my thesis from the start. :-)

24.11-RELEASE
nut package 2.8.2_4

I see that this information was discussed above. I've been traveling the past three plus weeks, so it's been hard to keep track of things. Sorry.

dennypage

@j-koopmann Checking on the prior issue for a moment... Were you able to implement a quirk? Are you still having issues with usbhid-ups?

j.koopmann

@dennypage I honestly never had a problem with usbhid-ups (so I believe). Whenever I start it it immediately recognizes my UPS. It is currently running as user nut and I never installed a quirk.

upsmon 75628 - - Signal 15: exiting
upsd 24479 - - Signal 15: exiting

But these are due to interface WAN IP changes that restart all services.

At one point other the other I get

psmon 89561 - - UPS [Keller]: connect failed: Connection failure: Connection refused

(even though usbhid-ups seems to be running) and
then

<27>1 2025-06-26T08:48:50.206377+02:00 pfSenseHills.koopmann.local upsmon 89561 - - UPS [Keller]: connect failed: Connection failure: Connection refused
<27>1 2025-06-26T08:48:55.275466+02:00 pfSenseHills.koopmann.local upsmon 89561 - - Set password on [Keller] failed - got [PASSWORD 66da6bc012db26058161]
<27>1 2025-06-26T08:49:00.279702+02:00 pfSenseHills.koopmann.local upsmon 89561 - - Poll UPS [Keller] failed - Protocol error
<27>1 2025-06-26T08:49:05.280772+02:00 pfSenseHills.koopmann.local upsmon 89561 - - Poll UPS [Keller] failed - Protocol error
<27>1 2025-06-26T08:49:10.285154+02:00 pfSenseHills.koopmann.local upsmon 89561 - - Poll UPS [Keller] failed - Protocol error
<27>1 2025-06-26T08:49:15.287439+02:00 pfSenseHills.koopmann.local upsmon 89561 - - Poll UPS [Keller] failed - Protocol error
<27>1 2025-06-26T08:49:20.292291+02:00 pfSenseHills.koopmann.local upsmon 89561 - - Poll UPS [Keller] failed - Protocol error
<27>1 2025-06-26T08:49:25.301818+02:00 pfSenseHills.koopmann.local upsmon 89561 - - Poll UPS [Keller] failed - Protocol error
<27>1 2025-06-26T08:49:30.303758+02:00 pfSenseHills.koopmann.local upsmon 89561 - - Poll UPS [Keller] failed - Protocol error
<27>1 2025-06-26T08:49:35.304766+02:00 pfSenseHills.koopmann.local upsmon 89561 - - Poll UPS [Keller] failed - Protocol error
<27>1 2025-06-26T08:49:40.308262+02:00 pfSenseHills.koopmann.local upsmon 89561 - - Poll UPS [Keller] failed - Protocol error
<27>1 2025-06-26T08:49:45.323762+02:00 pfSenseHills.koopmann.local upsmon 89561 - - Poll UPS [Keller] failed - Protocol error
<27>1 2025-06-26T08:49:50.325535+02:00 pfSenseHills.koopmann.local upsmon 89561 - - Poll UPS [Keller] failed - Protocol error
<27>1 2025-06-26T08:49:55.330127+02:00 pfSenseHills.koopmann.local upsmon 89561 - - Poll UPS [Keller] failed - Protocol error
<27>1 2025-06-26T08:50:00.337898+02:00 pfSenseHills.koopmann.local upsmon 89561 - - Poll UPS [Keller] failed - Protocol error
<27>1 2025-06-26T08:50:05.343880+02:00 pfSenseHills.koopmann.local upsmon 89561 - - Poll UPS [Keller] failed - Protocol error
<27>1 2025-06-26T08:50:10.367770+02:00 pfSenseHills.koopmann.local upsmon 89561 - - Poll UPS [Keller] failed - Protocol error
<27>1 2025-06-26T08:50:15.370222+02:00 pfSenseHills.koopmann.local upsmon 89561 - - Poll UPS [Keller] failed - Protocol error
<27>1 2025-06-26T08:50:20.473811+02:00 pfSenseHills.koopmann.local upsmon 89561 - - Poll UPS [Keller] failed - Protocol error
<27>1 2025-06-26T08:50:25.475779+02:00 pfSenseHills.koopmann.local upsmon 89561 - - Poll UPS [Keller] failed - Protocol error
<29>1 2025-06-26T08:50:25.475839+02:00 pfSenseHills.koopmann.local upsmon 89561 - - UPS Keller is unavailable
<27>1 2025-06-26T08:50:30.480347+02:00 pfSenseHills.koopmann.local upsmon 89561 - - Poll UPS [Keller] failed - Protocol error

dennypage

@j-koopmann said in NUT suddenly stops working every app. 6 minutes:

<27>1 2025-06-26T08:48:50.206377+02:00 pfSenseHills.koopmann.local upsmon 89561 - - UPS [Keller]: connect failed: Connection failure: Connection refused
<27>1 2025-06-26T08:48:55.275466+02:00 pfSenseHills.koopmann.local upsmon 89561 - - Set password on [Keller] failed - got [PASSWORD 66da6bc012db26058161]

Okay, that is entertaining to say the least. Does "66da6bc012db26058161" happen to be the locally generated password for local-monitor?

The next time the protocol error happens, would you please report the start time of the upsd and upsmon processes, plus the mod time and contents of these two files:

/usr/local/etc/nut/upsd.users 
/usr/local/etc/nut/upsmon.conf

After capturing that information, run

/usr/local/sbin/upsd -c reload

and see if the protocol error stops.

If it doesn't, then run

/usr/local/sbin/upsmon -c reload

and see if that stops it.

Thanks.

j.koopmann

@dennypage said in NUT suddenly stops working every app. 6 minutes:

Okay, that is entertaining to say the least. Does "66da6bc012db26058161" happen to be the locally generated password for local-monitor?

I have not the slightest idea! Never seen this before!!!!

Rest: Will be delighted to do so! Thanks for the instructions.