Jump to content

[Plugin] NUT v2 - Network UPS Tools

dmacias

By dmacias
in Plugin Support

Recommended Posts

Recommended

Posted by Rysz,

Please install Network UPS Tools (NUT) for UNRAID by Rysz from Community Applications. The older plugins (including the one in the first post of this topic) are deprecated/now unsupported.

Please read before installing NUT

Recommended by Rysz

0 reactions

Go to this post
Recommended

Posted by Rysz,

If you are using "powertop", this is known to cause instabilities with some UPS (changing the auto-hibernation of USB devices). If not, continue reading...   USB connectivity problems (data staleness, timeouts, ...) are incredibly hard if not impossible to diagnose remotely. They can stem from a multitude of factors because of the many parts involved in the equation (USB cable, port, bus, driver, implementation, ...). Common reasons have included broken USB cables (could attempt new US

USB connection instabilities, timeouts and staleness

Recommended by Rysz

0 reactions

Go to this post
teufelhunden Noob

teufelhunden

Posted
Posted (edited)

I have a American Power Conversion  Smart-UPS C 1500. This device is recoginzed when connecting it to my unraid server via USB. When trying to set up the plugin though I keep getting these errors in the logs. 
Feb 24 22:34:16 Hermes root: Using subdriver: APC HID 0.100
Feb 24 22:34:16 Hermes root: Network UPS Tools - Generic HID driver 0.52 (2.8.1.1)
Feb 24 22:34:16 Hermes root: USB communication driver (libusb 1.0) 0.46
Feb 24 22:34:16 Hermes root: nut_libusb_get_report: Input/Output Error
Feb 24 22:34:16 Hermes root: Can't initialize data from HID UPS
Feb 24 22:34:16 Hermes root: Driver failed to start (exit status=1)

 

I'm trying to use this as a network server so I can also shut down my pfsense box with it. I tried looking around and this is a brand new USB cable and connected to a  USB 2.0 port on this X13SAE-F motherboard. 

 

Any ideas. 

Edited by teufelhunden
Link to comment
  • Replies 1.4k
  • Created
  • Last Reply

Top Posters In This Topic

Popular Days

Top Posters In This Topic

Popular Days

Popular Posts

SimonF
SimonF

I am stopping updates for my version of the plugin. Update to the latest version 2023.09.17 and then you can remove my version and install Rysz's from CA and it will retain your configs.   T

dmacias
dmacias

NUT plugin v2 for unRAID 6.1+   NUT - Network UPS Tools - http://www.networkupstools.org/   Based on the original NUT plugin by macester Original thread https://forums.lime-technology.com/topic/

SimonF
SimonF

Released 2023.07.26, @ich777 is creating a new package for me to use, and I want to look to move to 2.8 as the default version but will need to check upgrade path works ok.

Posted Images

Rysz Enthusiast

Rysz

Posted
Posted (edited)
3 hours ago, teufelhunden said:

I have a American Power Conversion  Smart-UPS C 1500. This device is recoginzed when connecting it to my unraid server via USB. When trying to set up the plugin though I keep getting these errors in the logs. 
Feb 24 22:34:16 Hermes root: Using subdriver: APC HID 0.100
Feb 24 22:34:16 Hermes root: Network UPS Tools - Generic HID driver 0.52 (2.8.1.1)
Feb 24 22:34:16 Hermes root: USB communication driver (libusb 1.0) 0.46
Feb 24 22:34:16 Hermes root: nut_libusb_get_report: Input/Output Error
Feb 24 22:34:16 Hermes root: Can't initialize data from HID UPS
Feb 24 22:34:16 Hermes root: Driver failed to start (exit status=1)

 

I'm trying to use this as a network server so I can also shut down my pfsense box with it. I tried looking around and this is a brand new USB cable and connected to a  USB 2.0 port on this X13SAE-F motherboard. 

 

Any ideas. 

 

How do you know it is recognized?

Do you also have the APC UPS daemon activated (see "UPS Settings")?

If so please make sure to disable it as it cannot function alongside of NUT.

 

Also, have you tried another USB port yet, sometimes another USB port works better?

Please post the "NUT Debug Package" here (you can download it under "NUT Settings").

 

Last (but try everything else first) you can try changing the NUT backend to "legacy (2.7.4 stable") in "NUT Settings" and restart the server afterwards for the change to become effective. Some UPS work better with the older versions of NUT and your UPS was reported working with 2.7.4. according to the NUT website.

 

Edited by Rysz
Link to comment
teufelhunden Noob

teufelhunden

Posted
Posted
44 minutes ago, Rysz said:

 

How do you know it is recognized?

Do you also have the APC UPS daemon activated (see "UPS Settings")?

If so please make sure to disable it as it cannot function alongside of NUT.

 

Also, have you tried another USB port yet, sometimes another USB port works better?

Please post the "NUT Debug Package" here (you can download it under "NUT Settings").

 

Last (but try everything else first) you can try changing the NUT backend to "legacy (2.7.4 stable") in "NUT Settings" and restart the server afterwards for the change to become effective. Some UPS work better with the older versions of NUT and your UPS was reported working with 2.7.4. according to the NUT website.

 

It was showing when using sudo nut-scanner -U. I got it to work though. I don't know how. 

Link to comment
Rysz Enthusiast

Rysz

Posted
Posted
33 minutes ago, teufelhunden said:

It was showing when using sudo nut-scanner -U. I got it to work though. I don't know how. 

 

Glad you got it to work - probably was just a USB hiccup that caused it the first time.

Link to comment
tmodev Noob

tmodev

Posted
Posted (edited)

Hello,  I am trying to use a CyberPower UPS. Initially it was working, and the UPS was detected. However, recently it starting crashing for whatever reason. If i run Auto Config, the UPS is detected. However the driver fails to start with the following error messages

  

Feb 26 09:50:25 tmosrv root: Network UPS Tools - Generic HID driver 0.52 (2.8.1)
Feb 26 09:50:25 tmosrv root: USB communication driver (libusb 1.0) 0.46
Feb 26 09:50:25 tmosrv root: libusb1: Could not open any HID devices: insufficient permissions on everything
Feb 26 09:50:25 tmosrv root: No matching HID UPS found
Feb 26 09:50:25 tmosrv root: Driver failed to start (exit status=1)
Feb 26 09:50:25 tmosrv root: Network UPS Tools - UPS driver controller 2.8.1
Feb 26 09:50:26 tmosrv root: Writing NUT configuration...
Feb 26 09:50:27 tmosrv kernel: usb 1-4: new low-speed USB device number 30 using xhci_hcd
Feb 26 09:50:27 tmosrv kernel: hid-generic 0003:0764:0501.001A: hiddev96,hidraw0: USB HID v1.10 Device [CPS VP1000ELCD] on usb-0000:00:14.0-4/input0
Feb 26 09:50:35 tmosrv kernel: usb 1-4: USB disconnect, device number 30
Feb 26 09:50:38 tmosrv kernel: usb 1-4: new low-speed USB device number 31 using xhci_hcd
Feb 26 09:50:38 tmosrv kernel: hid-generic 0003:0764:0501.001B: hiddev96,hidraw0: USB HID v1.10 Device [CPS VP1000ELCD] on usb-0000:00:14.0-4/input0
Feb 26 09:50:43 tmosrv root: Updating permissions for NUT...
Feb 26 09:50:43 tmosrv root: Checking if the NUT Runtime Statistics Module should be enabled...
Feb 26 09:50:43 tmosrv root: Disabling the NUT Runtime Statistics Module...
Feb 26 09:50:44 tmosrv root: Stopping the NUT services... 
Feb 26 09:50:46 tmosrv kernel: usb 1-4: USB disconnect, device number 31
Feb 26 09:50:46 tmosrv root: Network UPS Tools - UPS driver controller 2.8.1
Feb 26 09:50:49 tmosrv kernel: usb 1-4: new low-speed USB device number 32 using xhci_hcd
Feb 26 09:50:49 tmosrv kernel: hid-generic 0003:0764:0501.001C: hiddev96,hidraw0: USB HID v1.10 Device [CPS VP1000ELCD] on usb-0000:00:14.0-4/input0
Feb 26 09:50:57 tmosrv kernel: usb 1-4: USB disconnect, device number 32
Feb 26 09:50:59 tmosrv flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update
Feb 26 09:51:00 tmosrv kernel: usb 1-4: new low-speed USB device number 33 using xhci_hcd
Feb 26 09:51:00 tmosrv kernel: hid-generic 0003:0764:0501.001D: hiddev96,hidraw0: USB HID v1.10 Device [CPS VP1000ELCD] on usb-0000:00:14.0-4/input0
Feb 26 09:51:08 tmosrv kernel: usb 1-4: USB disconnect, device number 33
Feb 26 09:51:11 tmosrv kernel: usb 1-4: new low-speed USB device number 34 using xhci_hcd
Feb 26 09:51:11 tmosrv kernel: hid-generic 0003:0764:0501.001E: hiddev96,hidraw0: USB HID v1.10 Device [CPS VP1000ELCD] on usb-0000:00:14.0-4/input0
Feb 26 09:51:19 tmosrv kernel: usb 1-4: USB disconnect, device number 34
Feb 26 09:51:22 tmosrv kernel: usb 1-4: new low-speed USB device number 35 using xhci_hcd
Feb 26 09:51:22 tmosrv kernel: hid-generic 0003:0764:0501.001F: hiddev96,hidraw0: USB HID v1.10 Device [CPS VP1000ELCD] on usb-0000:00:14.0-4/input0

 

 

I tried reinstalling, rebooting, an older version (2.8 of the nut driver) but nothing seem to work. Any ideas what issue it could be?

 

EDIT: Running nut-scanner -U gives me 

root@tmosrv:~# nut-scanner -U
Cannot load XML library (libneon.so) : file not found. XML search disabled.
Cannot load IPMI library (libfreeipmi.so) : file not found. IPMI search disabled.
Scanning USB bus.
[nutdev1]
        driver = "usbhid-ups"
        port = "auto"
        vendorid = "0764"
        productid = "0501"
        product = "VP1000ELCD"
        serial = ""
        vendor = "CPS"
        bus = "001"
        device = "063"
        busport = "004"
        ###NOTMATCHED-YET###bcdDevice = "0002"

# WARNING: <empty> "serial" reported in some devices: nutdev1

 

Edited by tmodev
Update
Link to comment
Rysz Enthusiast

Rysz

Posted
Posted (edited)
5 minutes ago, tmodev said:

Hello,  I am trying to use a CyberPower UPS. Initially it was working, and the UPS was detected. However, recently it starting crashing for whatever reason. If i run Auto Config, the UPS is detected. However the driver fails to start with the following error messages

  

Feb 26 09:50:25 tmosrv root: Network UPS Tools - Generic HID driver 0.52 (2.8.1)
Feb 26 09:50:25 tmosrv root: USB communication driver (libusb 1.0) 0.46
Feb 26 09:50:25 tmosrv root: libusb1: Could not open any HID devices: insufficient permissions on everything
Feb 26 09:50:25 tmosrv root: No matching HID UPS found
Feb 26 09:50:25 tmosrv root: Driver failed to start (exit status=1)
Feb 26 09:50:25 tmosrv root: Network UPS Tools - UPS driver controller 2.8.1
Feb 26 09:50:26 tmosrv root: Writing NUT configuration...
Feb 26 09:50:27 tmosrv kernel: usb 1-4: new low-speed USB device number 30 using xhci_hcd
Feb 26 09:50:27 tmosrv kernel: hid-generic 0003:0764:0501.001A: hiddev96,hidraw0: USB HID v1.10 Device [CPS VP1000ELCD] on usb-0000:00:14.0-4/input0
Feb 26 09:50:35 tmosrv kernel: usb 1-4: USB disconnect, device number 30
Feb 26 09:50:38 tmosrv kernel: usb 1-4: new low-speed USB device number 31 using xhci_hcd
Feb 26 09:50:38 tmosrv kernel: hid-generic 0003:0764:0501.001B: hiddev96,hidraw0: USB HID v1.10 Device [CPS VP1000ELCD] on usb-0000:00:14.0-4/input0
Feb 26 09:50:43 tmosrv root: Updating permissions for NUT...
Feb 26 09:50:43 tmosrv root: Checking if the NUT Runtime Statistics Module should be enabled...
Feb 26 09:50:43 tmosrv root: Disabling the NUT Runtime Statistics Module...
Feb 26 09:50:44 tmosrv root: Stopping the NUT services... 
Feb 26 09:50:46 tmosrv kernel: usb 1-4: USB disconnect, device number 31
Feb 26 09:50:46 tmosrv root: Network UPS Tools - UPS driver controller 2.8.1
Feb 26 09:50:49 tmosrv kernel: usb 1-4: new low-speed USB device number 32 using xhci_hcd
Feb 26 09:50:49 tmosrv kernel: hid-generic 0003:0764:0501.001C: hiddev96,hidraw0: USB HID v1.10 Device [CPS VP1000ELCD] on usb-0000:00:14.0-4/input0
Feb 26 09:50:57 tmosrv kernel: usb 1-4: USB disconnect, device number 32
Feb 26 09:50:59 tmosrv flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update
Feb 26 09:51:00 tmosrv kernel: usb 1-4: new low-speed USB device number 33 using xhci_hcd
Feb 26 09:51:00 tmosrv kernel: hid-generic 0003:0764:0501.001D: hiddev96,hidraw0: USB HID v1.10 Device [CPS VP1000ELCD] on usb-0000:00:14.0-4/input0
Feb 26 09:51:08 tmosrv kernel: usb 1-4: USB disconnect, device number 33
Feb 26 09:51:11 tmosrv kernel: usb 1-4: new low-speed USB device number 34 using xhci_hcd
Feb 26 09:51:11 tmosrv kernel: hid-generic 0003:0764:0501.001E: hiddev96,hidraw0: USB HID v1.10 Device [CPS VP1000ELCD] on usb-0000:00:14.0-4/input0
Feb 26 09:51:19 tmosrv kernel: usb 1-4: USB disconnect, device number 34
Feb 26 09:51:22 tmosrv kernel: usb 1-4: new low-speed USB device number 35 using xhci_hcd
Feb 26 09:51:22 tmosrv kernel: hid-generic 0003:0764:0501.001F: hiddev96,hidraw0: USB HID v1.10 Device [CPS VP1000ELCD] on usb-0000:00:14.0-4/input0

 

 

I tried reinstalling, rebooting, an older version (2.8 of the nut driver) but nothing seem to work. Any ideas what issue it could be?

 

EDIT: Running nut-scanner -U gives me 

root@tmosrv:~# nut-scanner -U
Cannot load XML library (libneon.so) : file not found. XML search disabled.
Cannot load IPMI library (libfreeipmi.so) : file not found. IPMI search disabled.
Scanning USB bus.
[nutdev1]
        driver = "usbhid-ups"
        port = "auto"
        vendorid = "0764"
        productid = "0501"
        product = "VP1000ELCD"
        serial = ""
        vendor = "CPS"
        bus = "001"
        device = "063"
        busport = "004"
        ###NOTMATCHED-YET###bcdDevice = "0002"

# WARNING: <empty> "serial" reported in some devices: nutdev1

 


Can you try another USB port and see if it works then - make sure to "Reset Config" first.

If it doesn't, perhaps you have another USB cable around that you could try?

 

Edited by Rysz
Link to comment
tmodev Noob

tmodev

Posted
Posted (edited)
1 hour ago, Rysz said:


Can you try another USB port and see if it works then - make sure to "Reset Config" first.

If it doesn't, perhaps you have another USB cable around that you could try?

 

i tried now various usb ports but i had no luck. I dont have another USB Cable. Is there anything else i could try?

 

When i run nut-scanner i get this... 

root@tmosrv:/etc/nut# nut-scanner
Cannot load XML library (libneon.so) : file not found. XML search disabled.
Cannot load IPMI library (libfreeipmi.so) : file not found. IPMI search disabled.
Scanning USB bus.
No start IP, skipping SNMP
No start IP, skipping NUT bus (old connect method)
Scanning NUT bus (avahi method).
[nutdev1]
        driver = "usbhid-ups"
        port = "auto"
        vendorid = "0764"
        productid = "0501"
        product = "VP1000ELCD"
        serial = ""
        vendor = "CPS"
        bus = "001"
        device = "070"
        busport = "002"
        ###NOTMATCHED-YET###bcdDevice = "0002"

# WARNING: <empty> "serial" reported in some devices: nutdev1

 

What is the ahavi method?

Edited by tmodev
Link to comment
Rysz Enthusiast

Rysz

Posted
Posted (edited)
42 minutes ago, tmodev said:

i tried now various usb ports but i had no luck. I dont have another USB Cable. Is there anything else i could try?

 

When i run nut-scanner i get this... 

root@tmosrv:/etc/nut# nut-scanner
Cannot load XML library (libneon.so) : file not found. XML search disabled.
Cannot load IPMI library (libfreeipmi.so) : file not found. IPMI search disabled.
Scanning USB bus.
No start IP, skipping SNMP
No start IP, skipping NUT bus (old connect method)
Scanning NUT bus (avahi method).
[nutdev1]
        driver = "usbhid-ups"
        port = "auto"
        vendorid = "0764"
        productid = "0501"
        product = "VP1000ELCD"
        serial = ""
        vendor = "CPS"
        bus = "001"
        device = "070"
        busport = "002"
        ###NOTMATCHED-YET###bcdDevice = "0002"

# WARNING: <empty> "serial" reported in some devices: nutdev1

 

What is the ahavi method?

 

That's just the device discovery method.

Did you try "Reset Config" and "Auto Config" afterwards?

It seems to detect the UPS but somehow isn't able to connect to it.

 

Please also post the NUT Debug Package (can be found under "NUT Settings")

But I'm pretty sure it's the cable if it worked fine before and suddenly keeps dropping out.

 

Edited by Rysz
Link to comment
Rysz Enthusiast

Rysz

Posted
Posted
3 minutes ago, tmodev said:

 

Yes i did Reset the config each time.

 

 

nut-debug-20240226120152.zip 12.7 kB · 0 downloads

 

Configuration looks good and shouldn't cause issues, you'll have to try a new USB cable I'm afraid.

Usually is one of these reason if things worked well before and start dropping out (more likely to less likely):

  • NUT settings recently changed around
  • UPS settings recently changed around
  • UPS firmware or NUT backend recently updated
  • USB cable between Unraid machine and UPS faulty or dead
  • USB port on Unraid machine faulty or dead
  • USB port on UPS faulty or dead
  • USB controller on UPS faulty or dead
  • USB controller on Unraid machine faulty or dead
  • Unraid version recently updated & now HW compatibility/driver issue
  • Like 1
Link to comment
tmodev Noob

tmodev

Posted
Posted (edited)
2 hours ago, Rysz said:

 

Configuration looks good and shouldn't cause issues, you'll have to try a new USB cable I'm afraid.

Usually is one of these reason if things worked well before and start dropping out (more likely to less likely):

  • NUT settings recently changed around
  • UPS settings recently changed around
  • UPS firmware or NUT backend recently updated
  • USB cable between Unraid machine and UPS faulty or dead
  • USB port on Unraid machine faulty or dead
  • USB port on UPS faulty or dead
  • USB controller on UPS faulty or dead
  • USB controller on Unraid machine faulty or dead
  • Unraid version recently updated & now HW compatibility/driver issue

 

Thanks. Ill try to get a replacement and try again :/

 

 

Update: I tried now additonal cables and got the same result. In the syslog i always see that it was found but then disconnected?

  

b 26 12:49:55 tmosrv kernel: usb 1-9: new low-speed USB device number 21 using xhci_hcd
Feb 26 12:49:55 tmosrv kernel: hid-generic 0003:0764:0501.03E7: hiddev96,hidraw0: USB HID v1.10 Device [CPS VP1000ELCD] on usb-0000:00:14.0-9/input0
Feb 26 12:50:03 tmosrv kernel: usb 1-9: USB disconnect, device number 21
Feb 26 12:50:03 tmosrv flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update
Feb 26 12:50:06 tmosrv kernel: usb 1-9: new low-speed USB device number 22 using xhci_hcd
Feb 26 12:50:06 tmosrv kernel: hid-generic 0003:0764:0501.03E8: hiddev96,hidraw0: USB HID v1.10 Device [CPS VP1000ELCD] on usb-0000:00:14.0-9/input0
Feb 26 12:50:14 tmosrv kernel: usb 1-9: USB disconnect, device number 22
Feb 26 12:50:17 tmosrv kernel: usb 1-9: new low-speed USB device number 23 using xhci_hcd
Feb 26 12:50:17 tmosrv kernel: hid-generic 0003:0764:0501.03E9: hiddev96,hidraw0: USB HID v1.10 Device [CPS VP1000ELCD] on usb-0000:00:14.0-9/input0
Feb 26 12:50:23 tmosrv emhttpd: cmd: /usr/local/emhttp/plugins/nut/scripts/nutscan
Feb 26 12:50:25 tmosrv kernel: usb 1-9: USB disconnect, device number 23
Feb 26 12:50:28 tmosrv kernel: usb 1-9: new low-speed USB device number 24 using xhci_hcd
Feb 26 12:50:28 tmosrv kernel: hid-generic 0003:0764:0501.03EA: hiddev96,hidraw0: USB HID v1.10 Device [CPS VP1000ELCD] on usb-0000:00:14.0-9/input0
Feb 26 12:50:36 tmosrv kernel: usb 1-9: USB disconnect, device number 24
Feb 26 12:50:39 tmosrv ool www[31791]: /usr/local/emhttp/plugins/nut/scripts/start
Feb 26 12:50:39 tmosrv kernel: usb 1-9: new low-speed USB device number 25 using xhci_hcd
Feb 26 12:50:40 tmosrv kernel: hid-generic 0003:0764:0501.03EB: hiddev96,hidraw0: USB HID v1.10 Device [CPS VP1000ELCD] on usb-0000:00:14.0-9/input0
Feb 26 12:50:40 tmosrv root: Writing NUT configuration...
Feb 26 12:50:41 tmosrv root: Updating permissions for NUT...
Feb 26 12:50:41 tmosrv root: Checking if the NUT Runtime Statistics Module should be enabled...
Feb 26 12:50:41 tmosrv root: Disabling the NUT Runtime Statistics Module...
Feb 26 12:50:42 tmosrv root: Network UPS Tools - Generic HID driver 0.52 (2.8.1)
Feb 26 12:50:42 tmosrv root: USB communication driver (libusb 1.0) 0.46
Feb 26 12:50:42 tmosrv root: libusb1: Could not open any HID devices: insufficient permissions on everything
Feb 26 12:50:42 tmosrv root: No matching HID UPS found
Feb 26 12:50:42 tmosrv root: Driver failed to start (exit status=1)
Feb 26 12:50:42 tmosrv root: Network UPS Tools - UPS driver controller 2.8.1
Feb 26 12:50:47 tmosrv kernel: usb 1-9: USB disconnect, device number 25
Feb 26 12:50:50 tmosrv kernel: usb 1-9: new low-speed USB device number 26 using xhci_hcd
Feb 26 12:50:51 tmosrv kernel: hid-generic 0003:0764:0501.03EC: hiddev96,hidraw0: USB HID v1.10 Device [CPS VP1000ELCD] on usb-0000:00:14.0-9/input0
Feb 26 12:50:58 tmosrv kernel: usb 1-9: USB disconnect, device number 26
Feb 26 12:51:01 tmosrv kernel: usb 1-9: new low-speed USB device number 27 using xhci_hcd
Feb 26 12:51:02 tmosrv kernel: hid-generic 0003:0764:0501.03ED: hiddev96,hidraw0: USB HID v1.10 Device [CPS VP1000ELCD] on usb-0000:00:14.0-9/input0
Feb 26 12:51:04 tmosrv flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update
Feb 26 12:51:09 tmosrv kernel: usb 1-9: USB disconnect, device number 27
Feb 26 12:51:12 tmosrv kernel: usb 1-9: new low-speed USB device number 28 using xhci_hcd
Feb 26 12:51:13 tmosrv kernel: hid-generic 0003:0764:0501.03EE: hiddev96,hidraw0: USB HID v1.10 Device [CPS VP1000ELCD] on usb-0000:00:14.0-9/input0
Feb 26 12:51:20 tmosrv kernel: usb 1-9: USB disconnect, device number 28
Feb 26 12:51:23 tmosrv kernel: usb 1-9: new low-speed USB device number 29 using xhci_hcd
Feb 26 12:51:24 tmosrv kernel: hid-generic 0003:0764:0501.03EF: hiddev96,hidraw0: USB HID v1.10 Device [CPS VP1000ELCD] on usb-0000:00:14.0-9/input0
Feb 26 12:51:31 tmosrv kernel: usb 1-9: USB disconnect, device number 29
Feb 26 12:51:34 tmosrv kernel: usb 1-9: new low-speed USB device number 30 using xhci_hcd

 

Any ideas? is this caused by a bad cable?

 

Update: Idk what changed but it resolved itself. I can now see the ups. We will see how long it lasts

Thanks for your help

 

Update 2: I guess i found the culprit
my powertop might disconnect the ups

grafik.png

Edited by tmodev
Link to comment
Rysz Enthusiast

Rysz

Posted
Posted (edited)
20 hours ago, tmodev said:

 

Thanks. Ill try to get a replacement and try again :/

 

 

Update: I tried now additonal cables and got the same result. In the syslog i always see that it was found but then disconnected?

  

b 26 12:49:55 tmosrv kernel: usb 1-9: new low-speed USB device number 21 using xhci_hcd
Feb 26 12:49:55 tmosrv kernel: hid-generic 0003:0764:0501.03E7: hiddev96,hidraw0: USB HID v1.10 Device [CPS VP1000ELCD] on usb-0000:00:14.0-9/input0
Feb 26 12:50:03 tmosrv kernel: usb 1-9: USB disconnect, device number 21
Feb 26 12:50:03 tmosrv flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update
Feb 26 12:50:06 tmosrv kernel: usb 1-9: new low-speed USB device number 22 using xhci_hcd
Feb 26 12:50:06 tmosrv kernel: hid-generic 0003:0764:0501.03E8: hiddev96,hidraw0: USB HID v1.10 Device [CPS VP1000ELCD] on usb-0000:00:14.0-9/input0
Feb 26 12:50:14 tmosrv kernel: usb 1-9: USB disconnect, device number 22
Feb 26 12:50:17 tmosrv kernel: usb 1-9: new low-speed USB device number 23 using xhci_hcd
Feb 26 12:50:17 tmosrv kernel: hid-generic 0003:0764:0501.03E9: hiddev96,hidraw0: USB HID v1.10 Device [CPS VP1000ELCD] on usb-0000:00:14.0-9/input0
Feb 26 12:50:23 tmosrv emhttpd: cmd: /usr/local/emhttp/plugins/nut/scripts/nutscan
Feb 26 12:50:25 tmosrv kernel: usb 1-9: USB disconnect, device number 23
Feb 26 12:50:28 tmosrv kernel: usb 1-9: new low-speed USB device number 24 using xhci_hcd
Feb 26 12:50:28 tmosrv kernel: hid-generic 0003:0764:0501.03EA: hiddev96,hidraw0: USB HID v1.10 Device [CPS VP1000ELCD] on usb-0000:00:14.0-9/input0
Feb 26 12:50:36 tmosrv kernel: usb 1-9: USB disconnect, device number 24
Feb 26 12:50:39 tmosrv ool www[31791]: /usr/local/emhttp/plugins/nut/scripts/start
Feb 26 12:50:39 tmosrv kernel: usb 1-9: new low-speed USB device number 25 using xhci_hcd
Feb 26 12:50:40 tmosrv kernel: hid-generic 0003:0764:0501.03EB: hiddev96,hidraw0: USB HID v1.10 Device [CPS VP1000ELCD] on usb-0000:00:14.0-9/input0
Feb 26 12:50:40 tmosrv root: Writing NUT configuration...
Feb 26 12:50:41 tmosrv root: Updating permissions for NUT...
Feb 26 12:50:41 tmosrv root: Checking if the NUT Runtime Statistics Module should be enabled...
Feb 26 12:50:41 tmosrv root: Disabling the NUT Runtime Statistics Module...
Feb 26 12:50:42 tmosrv root: Network UPS Tools - Generic HID driver 0.52 (2.8.1)
Feb 26 12:50:42 tmosrv root: USB communication driver (libusb 1.0) 0.46
Feb 26 12:50:42 tmosrv root: libusb1: Could not open any HID devices: insufficient permissions on everything
Feb 26 12:50:42 tmosrv root: No matching HID UPS found
Feb 26 12:50:42 tmosrv root: Driver failed to start (exit status=1)
Feb 26 12:50:42 tmosrv root: Network UPS Tools - UPS driver controller 2.8.1
Feb 26 12:50:47 tmosrv kernel: usb 1-9: USB disconnect, device number 25
Feb 26 12:50:50 tmosrv kernel: usb 1-9: new low-speed USB device number 26 using xhci_hcd
Feb 26 12:50:51 tmosrv kernel: hid-generic 0003:0764:0501.03EC: hiddev96,hidraw0: USB HID v1.10 Device [CPS VP1000ELCD] on usb-0000:00:14.0-9/input0
Feb 26 12:50:58 tmosrv kernel: usb 1-9: USB disconnect, device number 26
Feb 26 12:51:01 tmosrv kernel: usb 1-9: new low-speed USB device number 27 using xhci_hcd
Feb 26 12:51:02 tmosrv kernel: hid-generic 0003:0764:0501.03ED: hiddev96,hidraw0: USB HID v1.10 Device [CPS VP1000ELCD] on usb-0000:00:14.0-9/input0
Feb 26 12:51:04 tmosrv flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update
Feb 26 12:51:09 tmosrv kernel: usb 1-9: USB disconnect, device number 27
Feb 26 12:51:12 tmosrv kernel: usb 1-9: new low-speed USB device number 28 using xhci_hcd
Feb 26 12:51:13 tmosrv kernel: hid-generic 0003:0764:0501.03EE: hiddev96,hidraw0: USB HID v1.10 Device [CPS VP1000ELCD] on usb-0000:00:14.0-9/input0
Feb 26 12:51:20 tmosrv kernel: usb 1-9: USB disconnect, device number 28
Feb 26 12:51:23 tmosrv kernel: usb 1-9: new low-speed USB device number 29 using xhci_hcd
Feb 26 12:51:24 tmosrv kernel: hid-generic 0003:0764:0501.03EF: hiddev96,hidraw0: USB HID v1.10 Device [CPS VP1000ELCD] on usb-0000:00:14.0-9/input0
Feb 26 12:51:31 tmosrv kernel: usb 1-9: USB disconnect, device number 29
Feb 26 12:51:34 tmosrv kernel: usb 1-9: new low-speed USB device number 30 using xhci_hcd

 

Any ideas? is this caused by a bad cable?

 

Update: Idk what changed but it resolved itself. I can now see the ups. We will see how long it lasts

Thanks for your help

 

Update 2: I guess i found the culprit
my powertop might disconnect the ups

grafik.png

 

I was about to write a reply that you should check your powertop settings because I just saw you post about it in another topic. I'm glad to see that you have got it narrowed down to that and working for now in the meantime.

 

But I'm not entirely sure if your disabling of the auto-suspend for that USB device will survive a reboot of your system. So if it happens again, you know what to do and the culprit.

 

Edited by Rysz
  • Thanks 1
Link to comment
fezster Noob

fezster

Posted
Posted

I noticed I randomly started getting this error yesterday:

  

Mar  1 12:05:43 SM1 usbhid-ups[15531]: nut_libusb_get_report: Input/Output Error
Mar  1 12:05:57 SM1 usbhid-ups[15531]: libusb1: Could not open any HID devices: insufficient permissions on everything
Mar  1 12:05:57 SM1 upsd[15590]: Data for UPS [ups] is stale - check driver
Mar  1 12:06:00 SM1 upsmon[15594]: Poll UPS [[email protected]] failed - Data stale
Mar  1 12:06:00 SM1 upsmon[15594]: Communications with UPS [email protected] lost

 

It just repeats itself all the way to today. Only noticed because the dashbaord was not showing the UPS status anymore (no alert or error in Unraid).

 

Tried to restart NUT server and got this:

  

Mar  2 12:17:08 SM1 root: Stopping the NUT services...
Mar  2 12:17:08 SM1 upsmon[15594]: Signal 15: exiting
Mar  2 12:17:08 SM1 root: Network UPS Tools upsmon 2.8.1
Mar  2 12:17:08 SM1 upsd[15590]: User [email protected] logged out from UPS [ups]
Mar  2 12:17:08 SM1 upsmon[15593]: upsmon parent: read
Mar  2 12:17:08 SM1 upsd[15590]: mainloop: Interrupted system call
Mar  2 12:17:08 SM1 upsd[15590]: Signal 15: exiting
Mar  2 12:17:08 SM1 root: Network UPS Tools upsd 2.8.1
Mar  2 12:17:10 SM1 usbhid-ups[15531]: Signal 15: exiting
Mar  2 12:17:10 SM1 usbhid-ups[15531]: WARNING: send_to_all: write 38 bytes to socket 16 failed (ret=-1), disconnecting: Broken pipe
Mar  2 12:17:11 SM1 root: Network UPS Tools - UPS driver controller 2.8.1
Mar  2 12:17:15 SM1 root: Writing NUT configuration...
Mar  2 12:17:17 SM1 root: Updating permissions for NUT...
Mar  2 12:17:17 SM1 root: Checking if the NUT Runtime Statistics Module should be enabled...
Mar  2 12:17:17 SM1 root: Disabling the NUT Runtime Statistics Module...
Mar  2 12:17:18 SM1 root: Network UPS Tools - Generic HID driver 0.52 (2.8.1)
Mar  2 12:17:18 SM1 root: USB communication driver (libusb 1.0) 0.46
Mar  2 12:17:18 SM1 root: libusb1: Could not open any HID devices: insufficient permissions on everything
Mar  2 12:17:18 SM1 root: No matching HID UPS found
Mar  2 12:17:18 SM1 root: Driver failed to start (exit status=1)
Mar  2 12:17:18 SM1 root: Network UPS Tools - UPS driver controller 2.8.1

 

 

Running nutscanner, it does find the UPS:

  

root@SM1:~# nut-scanner -U
Cannot load XML library (libneon.so) : file not found. XML search disabled.
Cannot load IPMI library (libfreeipmi.so) : file not found. IPMI search disabled.
Scanning USB bus.
[nutdev1]
        driver = "usbhid-ups"
        port = "auto"
        vendorid = "0764"
        productid = "0501"
        bus = "002"
        device = "028"
        busport = "001"
        ###NOTMATCHED-YET###bcdDevice = "0001"
root@SM1:~#

 

 

 

As does lsusb:

  

root@SM1:~# lsusb
Bus 001 Device 002: ID 0930:6545 Toshiba Corp. Kingston DataTraveler 102/2.0 / HEMA Flash Drive 2 GB / PNY Attache 4GB Stick
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 028: ID 0764:0501 Cyber Power System, Inc. CP1500 AVR UPS
Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

 

 

Will try a restart in a bit. Other posts on this topic suggest a dying USB port or cable - but I'm not sure, as it has been working fine.

Link to comment
fezster Noob

fezster

Posted
Posted (edited)

Unplugging the USB and reconnecting has resolved it. Not ideal, though (esp as it lost communication silently). Any ideas?

 

EDIT - I should also add, it was running perfectly fine for 8 days prior to that, before throwing that error in the log yesterday.

Edited by fezster
Link to comment
LSL1337 Apprentice

LSL1337

Posted
Posted

Hello.

What is the value, which triggers the battery replacement warning message?

I have an APC BX 750 ups, and it regularly throws this message with a new original battery. The standard unraid ups service had the same issue, and i have found similiar issues with other people reporting the same thing with the BX series.

I don't see anything in the reported status.

ups.test.result Done and passed.

On the first week, i got the notification daily or once in 2-3 days. Now it's been a few days... very weird

 

Thanks.

Link to comment
Rysz Enthusiast

Rysz

Posted
Posted (edited)
1 hour ago, LSL1337 said:

Hello.

What is the value, which triggers the battery replacement warning message?

I have an APC BX 750 ups, and it regularly throws this message with a new original battery. The standard unraid ups service had the same issue, and i have found similiar issues with other people reporting the same thing with the BX series.

I don't see anything in the reported status.

ups.test.result Done and passed.

On the first week, i got the notification daily or once in 2-3 days. Now it's been a few days... very weird

 

Thanks.

 

It is reported either by the UPS or the UPS driver, you can disable the notification itself in the NUT Settings ("Battery Replacement Notification" to "No"), but you'll always see it in the UPS Status (in GUI) if that's what your UPS or UPS driver reports. At least disabling the notification you won't be bothered with e-mail or push notifications from NUT about your battery needing a replacement anymore - so hope that helps a bit!

 

If possible can you also post the NUT Debug Package here (can be found in NUT Settings) so I can take a look at what else might be causing the UPS status to be reported this way? Thanks in advance!

 

Edited by Rysz
Link to comment
msalad Noob

msalad

Posted
Posted

Hey, I'm running version 2024.03.04b on unraid 6.11.5 and I just started getting the below error message in my unraid's log:

 

nginx: 2024/03/05 00:14:31 [error] 78533#78533: *9345199 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: 192.168.1.22, server: , request: "GET /plugins/nut/include/nut_status.php?all=false HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "192.168.1.235", referrer: "http://192.168.1.235/Dashboard"

 

where I'm accessing my unraid dashboard from 192.168.1.22 and my unraid server is located at 192.168.1.235. Any ideas on what this means?

Link to comment
Rysz Enthusiast

Rysz

Posted
Posted (edited)
3 hours ago, msalad said:

Hey, I'm running version 2024.03.04b on unraid 6.11.5 and I just started getting the below error message in my unraid's log:

 

nginx: 2024/03/05 00:14:31 [error] 78533#78533: *9345199 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: 192.168.1.22, server: , request: "GET /plugins/nut/include/nut_status.php?all=false HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "192.168.1.235", referrer: "http://192.168.1.235/Dashboard"

 

where I'm accessing my unraid dashboard from 192.168.1.22 and my unraid server is located at 192.168.1.235. Any ideas on what this means?

 

This should happen only directly after updating until you refresh the page, it's because the script location was changed between the updates and the page is still looking for the old script at the old location until you refresh the browser. After you refreshed the page there shouldn't be any more of these messages. Can you confirm there are no more new messages like that after closing your browser page and opening it again?

 

Edited by Rysz
Link to comment
msalad Noob

msalad

Posted
Posted
1 hour ago, Rysz said:

 

This should happen only directly after updating until you refresh the page, it's because the script location was changed between the updates and the page is still looking for the old script until you refresh it. After you refreshed the page there shouldn't be any more of these messages. Can you confirm there are no more new messages like that after closing your browser page and opening it again?

 

 

Thanks for the quick reply. The messages have stopped after I closed the tab and opened a new one. I'll keep an eye on my logs to see if it pops up again

Link to comment
Masterwishx Collaborator

Masterwishx

Posted
Posted

@Rysz

if i set 'Disable UPS Power after Shutdown=yes' all working fine , my ups goes to 'Standby' after power loss , and then power up when power return to normal.

but is anyway i can turn OFF completely the UPS ? or it will not power on then if it possible at all?

using Eaton 9E2000i (Online UPS)

Link to comment
Rysz Enthusiast

Rysz

Posted
Posted (edited)
2 hours ago, Masterwishx said:

@Rysz

if i set 'Disable UPS Power after Shutdown=yes' all working fine , my ups goes to 'Standby' after power loss , and then power up when power return to normal.

but is anyway i can turn OFF completely the UPS ? or it will not power on then if it possible at all?

using Eaton 9E2000i (Online UPS)

 

NUT has no more control over this behavior except for telling the UPS to turn off the power. How the UPS handles that depends on the implementation on the UPS itself, maybe there's a setting directly on the UPS. Maybe - I'm guessing here - because you have an online UPS (where the power to the devices is never coming entirely from the mains power) it's never going to fully turn off but will just kill the power to the outlets and remain in standby until it it sees that the AC is back online.

 

I'd check out the user manual and perhaps contact Eaton over this, they are very supportive of the NUT project so I'm sure they'd be able to tell you more about this. For instance my line-interactive Eaton 5P850 turns completely off after shutdown, but that's a line-interactive and not online one.

 

Is the LCD going dark when it "shuts down" or how do you notice it's actually "shutting down" (or going to standby mode as you described)? Does it cut the power to the outlets?

 

Edited by Rysz
  • Like 1
Link to comment
Masterwishx Collaborator

Masterwishx

Posted
Posted (edited)
30 minutes ago, Rysz said:

Is the LCD going dark when it "shuts down" or how do you notice it's actually "shutting down" (or going to standby mode as you described)? Does it cut the power to the outlets?

 

it has two sates (off): 

1. stand by   (no power supplied to outlets) but LCD working and fans in ups working in low noise .

2. power off ( complete shut down nothing working at all )

 

from user guide: 

 

image.thumb.png.4c09b77f422ef39f54fa727037654991.png

 

 

 

Edited by Masterwishx
Link to comment
Rysz Enthusiast

Rysz

Posted
Posted
2 minutes ago, Masterwishx said:

Also checked after nut send FSD OB and power down , it has :  01 - Standby Mode   

 

image.thumb.png.4b6d2cdf387e8b6921a55e719a5df35e.png

 

Did you check upscmd for your UPS if there's anything else?

upscmd -l <upsname> should show a list of available commands.

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
Go to topic listing
×
×
  • Create New...