[Nut-upsuser] usbhid-ups becomes unresponsive after extended period

Gary digimon0327 at msn.com
Tue Feb 8 23:37:56 GMT 2022

OS name and version: Ubuntu 20.04.3 LTS
NUT Version: 2.7.4 (installed via apt-get)
USB communication driver: 0.33
Subdriver: APC HID 0.96
Device: APC Back-UPS 550

The usbhid-ups driver seems to stop responding/serving data to upsd after running it for a few hours. It works initially when starting the NUT service but would stop working after a while. It would start working again for a bit if I restart it (sudo upsdrvctl start)

In my syslog, I would get these error messages once it stops working.

Feb  8 15:20:43 internal upsmon[25307]: UPS [ups1 at localhost]: connect failed: Connection failure: Connection timed out
Feb  8 15:20:43 internal upsmon[25307]: UPS ups1 at localhost is unavailable

Reading the log, the upshid-ups log stops updating after a while. For example, in this log, it would keep updating until 8282 seconds but nothing appears in the log afterwards. The command I use to capture the log is:
/usr/lib/nut/usbhid-ups -DDDDD -a ups1 > /var/log/usbhid_log 2>&1 &

Log file:

The troubleshooting steps I have done include:
- Works without issue: Connecting to a different VM (but on same hardware, cable port, usb passthrough) running FreeBSD 12.3 and NUT
--- So it doesn't seem to be an issue with hardware, cable, or VM passthrough issue

The setup:
- APC Back-UPS connected via USB to USB port on machine, passthrough via ESXi to guest VM

Greatly appreciate any insights.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/nut-upsuser/attachments/20220208/823e16ab/attachment.htm>

More information about the Nut-upsuser mailing list