dmacias72 / nut-unraid Goto Github PK

Im trying to start NUT using the below technique and im getting this error:

root@PPNHOST:~# /etc/rc.d/rc.nut start
Writing nut config
Updating permissions...
Network UPS Tools - UPS driver controller 2.7.4.1
/usr/libexec/nut/snmp-ups: error while loading shared libraries: libcrypto.so.1: cannot open shared object file: No such file or directory
Driver failed to start (exit status=127)

Lost UPS after running for a while, NUT plugin shows running, but no UPS device shows
After re-plugging and unplugging the USB, restart the NUT plugin and enable it normally

Scanning for UPS...

[nutdev1]
driver = "usbhid-ups"
port = "auto"
vendorid = "051D"
productid = "0002"
product = "BK650M2-CH"
serial = "9B2019A13037"
vendor = "American Power Conversion"
bus = "001"

Feb 1 11:03:10 Tower upsmon[14759]: Poll UPS [[email protected]] failed - Data stale
Feb 1 11:03:11 Tower usbhid-ups[13944]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround
Feb 1 11:03:13 Tower usbhid-ups[13944]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround
Feb 1 11:03:15 Tower usbhid-ups[13944]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround
Feb 1 11:03:15 Tower upsmon[14759]: Poll UPS [[email protected]] failed - Data stale
Feb 1 11:03:17 Tower usbhid-ups[13944]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround
Feb 1 11:03:19 Tower usbhid-ups[13944]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround
Feb 1 11:03:20 Tower upsmon[14759]: Poll UPS [[email protected]] failed - Data stale
Feb 1 11:03:21 Tower usbhid-ups[13944]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround
Feb 1 11:03:23 Tower usbhid-ups[13944]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround
Feb 1 11:03:25 Tower usbhid-ups[13944]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround
Feb 1 11:03:25 Tower upsmon[14759]: Poll UPS [[email protected]] failed - Data stale
Feb 1 11:03:27 Tower usbhid-ups[13944]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround
Feb 1 11:03:29 Tower usbhid-ups[13944]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround
Feb 1 11:03:30 Tower upsmon[14759]: Poll UPS [[email protected]] failed - Data stale
Feb 1 11:03:31 Tower usbhid-ups[13944]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround
Feb 1 11:03:33 Tower usbhid-ups[13944]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround
Feb 1 11:03:35 Tower usbhid-ups[13944]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround
Feb 1 11:03:35 Tower upsmon[14759]: Poll UPS [[email protected]] failed - Data stale
Feb 1 11:03:37 Tower usbhid-ups[13944]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround
Feb 1 11:03:39 Tower usbhid-ups[13944]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround
Feb 1 11:03:40 Tower upsmon[14759]: Poll UPS [[email protected]] failed - Data stale
Feb 1 11:03:41 Tower usbhid-ups[13944]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround
Feb 1 11:03:43 Tower usbhid-ups[13944]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround
Feb 1 11:03:45 Tower usbhid-ups[13944]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround
Feb 1 11:03:45 Tower upsmon[14759]: Poll UPS [[email protected]] failed - Data stale
Feb 1 11:03:47 Tower usbhid-ups[13944]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround
Feb 1 11:03:49 Tower usbhid-ups[13944]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround
Feb 1 11:03:50 Tower upsmon[14759]: Poll UPS [[email protected]] failed - Data stale
Feb 1 11:03:51 Tower usbhid-ups[13944]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround
Feb 1 11:03:53 Tower usbhid-ups[13944]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround
Feb 1 11:03:55 Tower usbhid-ups[13944]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround
Feb 1 11:03:55 Tower upsmon[14759]: Poll UPS [[email protected]] failed - Data stale
Feb 1 11:03:57 Tower usbhid-ups[13944]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround

Can we please fix this? Haven't seen an improvement since the custom-case commit was reverted.

i have a ton of these in the log:

Unraid 6.5.3
Cyber Power PR750LCDRT1U

Aug 13 07:29:35 SERVER usbhid-ups[4240]: nut_libusb_get_report: Input/Output Error
Aug 13 07:29:35 SERVER usbhid-ups[4240]: nut_libusb_get_report: Input/Output Error
Aug 13 07:29:35 SERVER usbhid-ups[4240]: nut_libusb_get_report: Input/Output Error
Aug 13 07:31:11 SERVER usbhid-ups[4240]: nut_libusb_get_string: Input/Output Error
Aug 13 07:31:41 SERVER usbhid-ups[4240]: nut_libusb_get_report: Input/Output Error
Aug 13 07:31:43 SERVER usbhid-ups[4240]: nut_libusb_get_report: Input/Output Error
Aug 13 07:32:47 SERVER usbhid-ups[4240]: nut_libusb_get_report: Input/Output Error
Aug 13 07:33:01 SERVER usbhid-ups[4240]: nut_libusb_get_report: Input/Output Error
Aug 13 07:33:09 SERVER usbhid-ups[4240]: nut_libusb_get_report: Input/Output Error
Aug 13 07:34:07 SERVER usbhid-ups[4240]: nut_libusb_get_report: Input/Output Error
Aug 13 07:34:23 SERVER usbhid-ups[4240]: nut_libusb_get_report: Input/Output Error
Aug 13 07:35:11 SERVER usbhid-ups[4240]: nut_libusb_get_report: Input/Output Error
Aug 13 07:37:03 SERVER usbhid-ups[4240]: nut_libusb_get_string: Pipe error
Aug 13 07:37:03 SERVER usbhid-ups[4240]: nut_libusb_get_report: Input/Output Error
Aug 13 07:37:03 SERVER usbhid-ups[4240]: nut_libusb_get_report: Input/Output Error
Aug 13 07:37:03 SERVER usbhid-ups[4240]: nut_libusb_get_report: Input/Output Error
Aug 13 07:37:35 SERVER usbhid-ups[4240]: nut_libusb_get_string: Pipe error
Aug 13 07:38:39 SERVER usbhid-ups[4240]: nut_libusb_get_string: Input/Output Error
Aug 13 07:39:17 SERVER usbhid-ups[4240]: nut_libusb_get_report: Input/Output Error
Aug 13 07:39:31 SERVER usbhid-ups[4240]: nut_libusb_get_report: Input/Output Error
Aug 13 07:39:49 SERVER usbhid-ups[4240]: nut_libusb_get_report: Input/Output Error
Aug 13 07:40:15 SERVER usbhid-ups[4240]: nut_libusb_get_report: Input/Output Error
Aug 13 07:40:15 SERVER usbhid-ups[4240]: nut_libusb_get_report: Input/Output Error
Aug 13 07:40:29 SERVER usbhid-ups[4240]: nut_libusb_get_report: Input/Output Error
Aug 13 07:40:39 SERVER usbhid-ups[4240]: nut_libusb_get_report: Input/Output Error
Aug 13 07:41:51 SERVER usbhid-ups[4240]: nut_libusb_get_report: Input/Output Error
Aug 13 07:41:59 SERVER usbhid-ups[4240]: nut_libusb_get_report: Input/Output Error
Aug 13 07:42:22 SERVER usbhid-ups[4240]: nut_libusb_get_string: Input/Output Error
Aug 13 07:42:22 SERVER usbhid-ups[4240]: nut_libusb_get_report: Input/Output Error
Aug 13 07:42:22 SERVER usbhid-ups[4240]: nut_libusb_get_report: Input/Output Error
Aug 13 07:43:06 SERVER usbhid-ups[4240]: nut_libusb_get_report: Input/Output Error
Aug 13 07:43:44 SERVER usbhid-ups[4240]: nut_libusb_get_report: Input/Output Error
Aug 13 07:44:02 SERVER usbhid-ups[4240]: nut_libusb_get_report: Input/Output Error
Aug 13 07:44:42 SERVER usbhid-ups[4240]: nut_libusb_get_report: Input/Output Error
Aug 13 07:45:04 SERVER usbhid-ups[4240]: nut_libusb_get_report: Input/Output Error
Aug 13 07:46:38 SERVER usbhid-ups[4240]: nut_libusb_get_report: Input/Output Error
Aug 13 07:46:40 SERVER usbhid-ups[4240]: nut_libusb_get_report: Input/Output Error
Aug 13 07:47:46 SERVER usbhid-ups[4240]: nut_libusb_get_report: Input/Output Error

I'm using NUT with some Eaton backup power device.
Using driver Bcmxcp_usb I can see status "ALARM Online". Detected as POWERWARE UPS 500i
It works just fine and if power is offline, I got notifications.

But few days later, 5-10 it just stops working, and all info not visible just looks like USB cable unplugged.
Status line where was "ALARM Online" become empty.
When I detect it I go to NUT settings and press "Reload" button.
Each time it helps and status starts to work again to "ALARM Online".

It happened already more than 5 times for me.

I hope to get this bug fixed, or get help or any advice how to make it reloaded each time it gone automatically.

Continued from networkupstools/nut#618

The ups I use is LADIS H1000M, which connects unraid host via USB and uses blazer_usb protocol. After the nut setting is set, the host can be turned off by power failure, but the ups cannot be turned off.

My UPS had issues fixed with it by a recent merge to the NUT codebase:
networkupstools/nut#1280

I know it is an awful lot to ask but:

Is there any chance you could build a newer version and that this plug-in could pull this more recent build of NUT so that I could have the fix?

Many thanks for your work!