Latest News:
*New 11.2 series Release:
2019-06-20: XigmaNAS 11.2.0.4.6766 - released!

*New 12.0 series Release:
2019-06-20: XigmaNAS 12.0.0.4.6766 - released!

We really need "Your" help on XigmaNAS https://translations.launchpad.net/xigmanas translations. Please help today!

Producing and hosting XigmaNAS costs money Please consider donating for our project so that we can continue to offer you the best.
We need your support! eg: PAYPAL

SOLVED: "usbhid-ups: libusb_get_interrupt: Unknown error" with Eaton 5S 1600 UPS

Uninterruptable Power Supply service using NUT.
Forum rules
Set-Up GuideFAQsForum Rules
Post Reply
nas4me2
NewUser
NewUser
Posts: 9
Joined: 21 Mar 2017 07:47
Status: Offline

SOLVED: "usbhid-ups: libusb_get_interrupt: Unknown error" with Eaton 5S 1600 UPS

#1

Post by nas4me2 » 25 Jun 2018 17:41

Just upgraded to 11.1.0.4 - Atomics (revision 5606) from rev 4616 (well, via FreeNAS 0.6, 0.7, iX0.8/8.x, iX9.x, back to Nas4Free 10.x, 11.x - a sordid past :)

Noticed after a while a *lot* of errors in the daemon.log, every 2 seconds repeating:

Code: Select all

Jun 25 22:50:08 nas4free usbhid-ups[2666]: libusb_get_interrupt: Unknown error
Jun 25 22:50:10 nas4free usbhid-ups[2666]: libusb_get_interrupt: Unknown error
Jun 25 22:50:12 nas4free usbhid-ups[2666]: libusb_get_interrupt: Unknown error
Jun 25 22:50:14 nas4free usbhid-ups[2666]: libusb_get_interrupt: Unknown error
None of these errors occurred under 4616. Prior versions did not have the UPS.

The UPS is an Eaton 5S 1600 using the usbhid-ups driver. The port was set to auto previously.

Set it to ugen1.4 per usbconfig output - no change.

Removed the boot USB flash drive from the same usb controller/hub as UPS and moved it to the motherboard socket (on separate usb controller - verified with usbconfig) - no change.

After 18k+ log messages in a few hours, in desperation I removed the entry for forwarding remote syslog entries for the daemon facility.

Read the post at https://www.nas4free.org/forums/viewtop ... =46&t=9112 but here the error is slightly different and also a different UPS, so the solution there (maxreport option) did not apply.

However, managed to spot an option that seemed reasonable to try - and it has solved the problem.

Add to the ups additional parameters:

Code: Select all

pollonly

Code: Select all

/usr/local/libexec/nut/usbhid-ups -h
...
Don't use interrupt pipe, only use polling : -x pollonly
Solved.

Supermicro A1SRi/Atom C2758/32GB ECC/zfs mirror/6 jails/2 VMs/2 bridges/4 vlans/4GBe+IPMI/Logitech Music Server/NextCloud/Alfresco/Postgres/Proxy+Cache/Joomla/aptcacher-ng/graylog/~30-35watts

Post Reply

Return to “UPS”