NUT 2.8.1 when?

dennypage

Yeah, I kind'a agree. It just seems there are lots of users with different UPS's and pfSense boxes than me that has the same problem.

FWIW, I think most of the "I have disconnect issues" were the result of the various USB bugs introduced in NUT 2.8.0.

In your specific case, on the software side the first thing I would try is setting the reconnect time:

waitbeforereconnect=5. This goes would go in the Extra Arguments to driver section. You can experiment with larger or smaller values (1-15). The default is 0.

I would also relax the pollinterval value:

pollinterval=5. This goes into the "Additional configuration lines for upsmon.conf" section. You can experiment with larger values. The default is 2.

If you increase the pollinterval significantly, say 10 or more, you should also increase pollfreq:

pollfreq=60. This goes would go in the Extra Arguments to driver section. The default is 30.

Last resort, I would also try setting the pollonly flag:

pollonly. This goes would go in the Extra Arguments to driver section. The default is disabled.

On the hardware side, you can try introducing a USB hub in-between the host and the UPS. This often masks questionable USB implementations. A powered hub is usually better.

keyser

@Gertjan First interesting info:

ugen1.2: <EATON 5S> at usbus1, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON (20mA)

{
UE_CONTROL_OK : 8949
UE_ISOCHRONOUS_OK : 0
UE_BULK_OK : 0
UE_INTERRUPT_OK : 0
UE_CONTROL_FAIL : 0
UE_ISOCHRONOUS_FAIL : 0
UE_BULK_FAIL : 0
UE_INTERRUPT_FAIL : 5604
}

Seems I have no successfull interrupts… wonder what that indicates ?

keyser

@Gertjan DEADTIME has no effect on the notifications about the unavailable UPS when the 5 sec USB disconnect/reconnect happens

keyser

@Gertjan Regardless what I do I cannot get usbdump to output any data. Even “usbdump -v” with no specifics does not output anything.

keyser

@Gertjan When the disconnect happens, I get the following in my firewall log:

2024-04-07 04:09:24.000
notify_monitor.php: Message sent to xxx@xxxxxxxxxx.xx OK
2024-04-07 04:08:54.000
Communications with UPS eaton5sc established
2024-04-07 04:08:52.000
UPS [eaton5sc] data is no longer stale
2024-04-07 04:08:52.000
notify_monitor.php: Message sent to xxx@xxxxxxxxxx.xx OK
2024-04-07 04:08:49.000
Communications with UPS eaton5sc lost
2024-04-07 04:08:49.000
Poll UPS [eaton5sc] failed - Data stale
2024-04-07 04:08:48.000
ugen1.2: <EATON 5S> at usbus1
2024-04-07 04:08:47.000
libusb1: Could not open any HID devices: no USB buses found
2024-04-07 04:08:46.000
ugen1.2: <EATON 5S> at usbus1 (disconnected)
2024-04-07 04:08:45.000
libusb1: Could not open any HID devices: insufficient permissions on everything
2024-04-07 04:08:45.000
Data for UPS [eaton5sc] is stale - check driver

dennypage

@keyser said in NUT 2.8.1 when?:

@Gertjan Regardless what I do I cannot get usbdump to output any data. Even “usbdump -v” with no specifics does not output anything.

I think a slight mistake. The output that shown for "usbconfig dump_stats" is actually the output for "usbconfig" (without dump_stats).

FWIW, since you are able re-connect almost immediately to the ups, I don't believe that you will be able to effectively capture the output of usbconfig by hand at the appropriate moment to provide meaningful information. And if you did, I suspect that it would boil down to "there is no usb ups device."

The command usbdump is a slightly different thing. This is something that you would want running before, and during, the time when the disconnect actually happens. Not sure that this is worth the effort though as the most likely outcome is again "there is no usb ups device."

You can certainly run usbdump, but it would probably be more productive to run the driver in debug mode (see later posts in the main 2.8.1 thread for examples). However based upon what you have posted, the most likely outcome is again "there is no usb ups device."

You might want to explore the Advanced section items I suggested a few posts above.