3 hours ago, Joly0 said:

Hey guys, maybe some can help me. So i have purchased a green cell 2000va ups on german amazon.

I installed the nut plugin and let it detect the driver. It suggested the "nutdrv_qx" driver, so i tried that first, but i noticed in the dashboard, that "Battery Charge" and "Runtime Left" were missing. So i switched to the second recommendation "blazer_usb". Now "Batter Charge" is shown aswell, but the "Runtime Left" is still missing.
The detect function suggests a third driver "nutdrv_atcl_usb" but that is not to be seen anywhere on the selection. Should i try that driver and if so, how can i do so? Or is there another reason, why the runtime left is not showing up?

 

It works with this configuration. If that driver doesn't provide more information, which I don't think it will, I would recommend to use "blazer_usb" as all important NUT functions will still work without "Runtime Left" - except the "Runtime Left" shutdown mode (which I don't recommend personally anyway) - so I'd just use "Time on Battery" or "Battery Level" instead. 🙂 

 

I just want to add a data point regarding the "NUT Connected Slaves" count. I have my pfsense firewall connected as a NUT slave (using NUT slave credentials) and the emergency shutdown function, along with all NUT data reporting has always functioned properly on the pfsense side. That said, I show "No Active Connections" in the unraid NUT server plugin. Any thoughts on what may be the issue?

I'm getting this when trying to update the plugin: plugin: run failed: '/bin/bash' returned 1. Not sure why as all other updates have worked before.

22 hours ago, cinsun42 said:

I just want to add a data point regarding the "NUT Connected Slaves" count. I have my pfsense firewall connected as a NUT slave (using NUT slave credentials) and the emergency shutdown function, along with all NUT data reporting has always functioned properly on the pfsense side. That said, I show "No Active Connections" in the unraid NUT server plugin. Any thoughts on what may be the issue?

 

I'm not sure how/if pfSense handles client registration, but this is (if anything) an issue on the client side (e.g. wrong credentials, used "NUT Monitor Username" instead of "NUT Slave Username").

 

Note: For an Unraid-type setup it won't make a huge difference (unless something fails), this is mostly relevant on NUT setups which don't have scripted shutdown thresholds (as on Unraid) and rely on default NUT behaviour of shutting down when the UPS says so (and not primarily the server). Such setups would first wait HOSTSYNC (configurable) seconds for a logged in slave to disconnect, before shutting down themselves. If - however - the slave is not logged in, the master server would not wait and potentially kill the outlet power before the slave has finished shutting down (hence this "registration"). I implemented this because there is an option to disable all shutdown thresholds and rely on this default NUT behaviour on Unraid too (so this would be needed for verification in such cases), and it also has some additional minor benefits regarding communication and logging to be fully "logged in". In any case, it's not mandatory, and NUT slaves can still act on the information from the NUT server without slave registration and/or authorization (so it's just an additional safeguard).

 

29 minutes ago, Snowman said:

I'm getting this when trying to update the plugin: plugin: run failed: '/bin/bash' returned 1. Not sure why as all other updates have worked before.

 

Please try uninstalling and installing the plugin again (instead of updating).

If that also fails, uninstall the plugin => reboot the server => install the plugin again. 🙂 

Hi there. Wondering if I could get some guidance about the issue I'm seeing. Recently I had to replace cpu/motherboard and previously functioning NUT stopped working.

 

NUT plugin was nuked and reinstalled.

 

Here's what I'm seeing with nut-scanner (so it can see UPS connected):

 

[nutdev-usb1]
driver = "usbhid-ups"
port = "auto"
vendorid = "0764"
productid = "0601"
product = "CP1500PFCRM2U"
serial = "XXXXXXXXX" # edited
# bus = "001"
# device = "002"
# busport = "006"

 

Starting it results with this error:

 

Oct 23 14:38:41 FileBox ool www[15619]: /usr/local/emhttp/plugins/nut-dw/scripts/start
Oct 23 14:38:42 FileBox rc.nut: Writing NUT configuration...
Oct 23 14:38:43 FileBox rc.nut: Updating permissions for NUT...
Oct 23 14:38:43 FileBox rc.nut: Checking if the NUT Runtime Statistics Module should be enabled...
Oct 23 14:38:43 FileBox rc.nut: Disabling the NUT Runtime Statistics Module...
Oct 23 14:38:45 FileBox kernel: usb 1-7.3: new low-speed USB device number 62 using xhci_hcd
Oct 23 14:38:45 FileBox kernel: usb 1-7.3: device descriptor read/64, error -32
Oct 23 14:38:45 FileBox kernel: usb 1-7.3: device descriptor read/64, error -32
Oct 23 14:38:45 FileBox kernel: usb 1-7.3: new low-speed USB device number 63 using xhci_hcd
Oct 23 14:38:45 FileBox kernel: usb 1-7.3: device descriptor read/64, error -32
Oct 23 14:38:45 FileBox kernel: usb 1-7.3: device descriptor read/64, error -32
Oct 23 14:38:45 FileBox kernel: usb 1-7-port3: attempt power cycle
Oct 23 14:38:46 FileBox kernel: usb 1-7.3: new low-speed USB device number 64 using xhci_hcd
Oct 23 14:38:46 FileBox kernel: usb 1-7.3: Device not responding to setup address.
Oct 23 14:38:46 FileBox kernel: usb 1-7.3: Device not responding to setup address.
Oct 23 14:38:46 FileBox kernel: usb 1-7.3: device not accepting address 64, error -71
Oct 23 14:38:46 FileBox kernel: usb 1-7.3: new low-speed USB device number 65 using xhci_hcd
Oct 23 14:38:46 FileBox kernel: usb 1-7.3: Device not responding to setup address.
Oct 23 14:38:47 FileBox kernel: usb 1-7.3: Device not responding to setup address.
Oct 23 14:38:47 FileBox kernel: usb 1-7.3: device not accepting address 65, error -71
Oct 23 14:38:47 FileBox kernel: usb 1-7-port3: unable to enumerate USB device
Oct 23 14:38:47 FileBox rc.nut: Using subdriver: CyberPower HID 0.80
Oct 23 14:38:47 FileBox rc.nut: Network UPS Tools - Generic HID driver 0.53 (2.8.2)
Oct 23 14:38:47 FileBox rc.nut: USB communication driver (libusb 1.0) 0.47
Oct 23 14:38:47 FileBox rc.nut: nut_libusb_get_string: Input/Output Error
Oct 23 14:38:47 FileBox rc.nut: nut_libusb_get_report: Input/Output Error
Oct 23 14:38:47 FileBox rc.nut: Can't initialize data from HID UPS
Oct 23 14:38:47 FileBox rc.nut: Driver failed to start (exit status=1)
Oct 23 14:38:47 FileBox rc.nut: Network UPS Tools - UPS driver controller 2.8.2

 

What exactly am I seeing here? I tried all the different USB ports (that seem to work just fine otherwise... in bios at least and in terminal after unraid boots). Googling about it didn't help.

 

Upgraded from Intel 10400 to 13400 and motherboard from Asus B560 to Gigabyte B760... everything else is the same.

 

Unraid is on the latest stable 6.12.13 version.

Edited October 23, 20241 yr by Grocery
more clarity

5 hours ago, Grocery said:

Hi there. Wondering if I could get some guidance about the issue I'm seeing. Recently I had to replace cpu/motherboard and previously functioning NUT stopped working.

 

NUT plugin was nuked and reinstalled.

 

Here's what I'm seeing with nut-scanner (so it can see UPS connected):

 

[nutdev-usb1]
driver = "usbhid-ups"
port = "auto"
vendorid = "0764"
productid = "0601"
product = "CP1500PFCRM2U"
serial = "XXXXXXXXX" # edited
# bus = "001"
# device = "002"
# busport = "006"

 

Starting it results with this error:

 

Oct 23 14:38:41 FileBox ool www[15619]: /usr/local/emhttp/plugins/nut-dw/scripts/start
Oct 23 14:38:42 FileBox rc.nut: Writing NUT configuration...
Oct 23 14:38:43 FileBox rc.nut: Updating permissions for NUT...
Oct 23 14:38:43 FileBox rc.nut: Checking if the NUT Runtime Statistics Module should be enabled...
Oct 23 14:38:43 FileBox rc.nut: Disabling the NUT Runtime Statistics Module...
Oct 23 14:38:45 FileBox kernel: usb 1-7.3: new low-speed USB device number 62 using xhci_hcd
Oct 23 14:38:45 FileBox kernel: usb 1-7.3: device descriptor read/64, error -32
Oct 23 14:38:45 FileBox kernel: usb 1-7.3: device descriptor read/64, error -32
Oct 23 14:38:45 FileBox kernel: usb 1-7.3: new low-speed USB device number 63 using xhci_hcd
Oct 23 14:38:45 FileBox kernel: usb 1-7.3: device descriptor read/64, error -32
Oct 23 14:38:45 FileBox kernel: usb 1-7.3: device descriptor read/64, error -32
Oct 23 14:38:45 FileBox kernel: usb 1-7-port3: attempt power cycle
Oct 23 14:38:46 FileBox kernel: usb 1-7.3: new low-speed USB device number 64 using xhci_hcd
Oct 23 14:38:46 FileBox kernel: usb 1-7.3: Device not responding to setup address.
Oct 23 14:38:46 FileBox kernel: usb 1-7.3: Device not responding to setup address.
Oct 23 14:38:46 FileBox kernel: usb 1-7.3: device not accepting address 64, error -71
Oct 23 14:38:46 FileBox kernel: usb 1-7.3: new low-speed USB device number 65 using xhci_hcd
Oct 23 14:38:46 FileBox kernel: usb 1-7.3: Device not responding to setup address.
Oct 23 14:38:47 FileBox kernel: usb 1-7.3: Device not responding to setup address.
Oct 23 14:38:47 FileBox kernel: usb 1-7.3: device not accepting address 65, error -71
Oct 23 14:38:47 FileBox kernel: usb 1-7-port3: unable to enumerate USB device
Oct 23 14:38:47 FileBox rc.nut: Using subdriver: CyberPower HID 0.80
Oct 23 14:38:47 FileBox rc.nut: Network UPS Tools - Generic HID driver 0.53 (2.8.2)
Oct 23 14:38:47 FileBox rc.nut: USB communication driver (libusb 1.0) 0.47
Oct 23 14:38:47 FileBox rc.nut: nut_libusb_get_string: Input/Output Error
Oct 23 14:38:47 FileBox rc.nut: nut_libusb_get_report: Input/Output Error
Oct 23 14:38:47 FileBox rc.nut: Can't initialize data from HID UPS
Oct 23 14:38:47 FileBox rc.nut: Driver failed to start (exit status=1)
Oct 23 14:38:47 FileBox rc.nut: Network UPS Tools - UPS driver controller 2.8.2

 

What exactly am I seeing here? I tried all the different USB ports (that seem to work just fine otherwise... in bios at least and in terminal after unraid boots). Googling about it didn't help.

 

Upgraded from Intel 10400 to 13400 and motherboard from Asus B560 to Gigabyte B760... everything else is the same.

 

Unraid is on the latest stable 6.12.13 version.

 

This mostly looks like a broken cable to me, do you have another one to test it with?

15 hours ago, Rysz said:

 

This mostly looks like a broken cable to me, do you have another one to test it with?

 

I'll dig through my bags of cables, maybe there's another one... But does it make sense to see these errors when `lsusb` shows UPS as connected:

Bus 002 Device 002: ID 0781:5583 SanDisk Corp. Ultra Fit
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 05e3:0608 Genesys Logic, Inc. Hub
Bus 001 Device 002: ID 0764:0601 Cyber Power System, Inc. PR1500LCDRT2U UPS
Bus 001 Device 004: ID 048d:5702 Integrated Technology Express, Inc. ITE Device
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

 

... and `nut-scanner` returns correct stuff?

 

UPDATE: Changed the cable... even disabled "Secure Boot" option in BIOS just in case... same

device descriptor read/64, error -32

Internet says it might have something to do with "specifically indicates a permission issue"

Edited October 24, 20241 yr by Grocery

Interesting what voltage users have on battery.voltage ?

after calc for one battery 13.8v or 14v ?

13.8 here, but it would depend on the UPS...

2 hours ago, Kilrah said:

13.8 here, but it would depend on the UPS...

i had last half year 13.8v*6 =83v but from 4 days ago its 14v*6=84v mostly :   can it be maybe because weather temperature goes down from hot to cold also in house?

 

Hi there.

 

I have a custom battery backup with a huge battery that provides multi-day uptime.  I noticed that this plugin seems to truncate anything over a day of runtime and just reports the remaining time as 'HH:MM:SS', which is a bit misleading.  Would it be possible to change the display format to report as 'DD HH:MM:SS' (or maybe just 'DD.X days') if the runtime is more than a day?

 

 

Edited October 25, 20241 yr by sjerisman

I could use some help figuring out how to completely eliminate or at least suppress some constant connection errors that are filling up my system logs. The specific errors are shown below:

 

Quote

Oct 27 19:48:35 unRAID usbhid-ups[6814]: nut_libusb_get_string: Pipe error
Oct 27 19:48:45 unRAID usbhid-ups[6814]: nut_libusb_get_report: Input/Output Error
Oct 27 19:48:47 unRAID usbhid-ups[6814]: nut_libusb_get_string: Input/Output Error
Oct 27 19:49:57 unRAID usbhid-ups[6814]: nut_libusb_get_report: Input/Output Error
Oct 27 19:50:13 unRAID usbhid-ups[6814]: nut_libusb_get_report: Input/Output Error
Oct 27 19:50:47 unRAID usbhid-ups[6814]: nut_libusb_get_report: Input/Output Error
Oct 27 19:50:49 unRAID usbhid-ups[6814]: nut_libusb_get_report: Input/Output Error
Oct 27 19:51:37 unRAID usbhid-ups[6814]: nut_libusb_get_report: Input/Output Error
Oct 27 19:51:39 unRAID usbhid-ups[6814]: nut_libusb_get_string: Input/Output Error
Oct 27 19:51:55 unRAID usbhid-ups[6814]: nut_libusb_get_string: Input/Output Error
Oct 27 19:51:55 unRAID usbhid-ups[6814]: nut_libusb_get_string: Input/Output Error
Oct 27 19:52:53 unRAID usbhid-ups[6814]: nut_libusb_get_report: Input/Output Error
Oct 27 19:53:43 unRAID usbhid-ups[6814]: nut_libusb_get_report: Input/Output Error
Oct 27 19:53:46 unRAID usbhid-ups[6814]: nut_libusb_get_string: Input/Output Error
Oct 27 19:54:35 unRAID usbhid-ups[6814]: nut_libusb_get_string: Input/Output Error
Oct 27 19:54:55 unRAID usbhid-ups[6814]: nut_libusb_get_report: Input/Output Error
Oct 27 19:54:58 unRAID usbhid-ups[6814]: nut_libusb_get_report: Input/Output Error
Oct 27 19:55:31 unRAID usbhid-ups[6814]: nut_libusb_get_report: Input/Output Error
Oct 27 19:55:49 unRAID usbhid-ups[6814]: nut_libusb_get_report: Input/Output Error
Oct 27 19:56:11 unRAID usbhid-ups[6814]: nut_libusb_get_report: Input/Output Error
Oct 27 19:56:45 unRAID usbhid-ups[6814]: nut_libusb_get_string: Pipe error

These go on and on and on....

That said, the nut plugin reporting in unraid seems to be functioning properly.

 

I've tried enabling the "Enable Rule-Based Syslog Filters" option, but I must be writing the commands into xnut-nospam.conf improperly because I can't seem to suppress any of the above messages. Any help getting these messages resolved would be much appreciated, thank you!

3 hours ago, cinsun42 said:

I could use some help figuring out how to completely eliminate or at least suppress some constant connection errors that are filling up my system logs. The specific errors are shown below:

 

These go on and on and on....

That said, the nut plugin reporting in unraid seems to be functioning properly.

 

I've tried enabling the "Enable Rule-Based Syslog Filters" option, but I must be writing the commands into xnut-nospam.conf improperly because I can't seem to suppress any of the above messages. Any help getting these messages resolved would be much appreciated, thank you!

 

Sure, add these lines to your xnut-nospam.conf using the GUI configuration editor:

:msg, regex, "nut_libusb.*rror" -/var/log/nut-spam
:msg, regex, "nut_libusb.*rror" stop

Enable Rule-Based Syslog Filters: "Yes" => Restart NUT.

9 hours ago, Rysz said:

 

Sure, add these lines to your xnut-nospam.conf using the GUI configuration editor:

:msg, regex, "nut_libusb.*rror" -/var/log/nut-spam
:msg, regex, "nut_libusb.*rror" stop

Enable Rule-Based Syslog Filters: "Yes" => Restart NUT.

 

Unfortunately this doesn't seem to have worked for me, I'm still getting the same errors populating in syslog. This is after adding the lines above and restarting NUT several times with Enable Rule-Based Syslog Filters: "Yes"

 

Some things I've noticed that may or may (or may not) be helpful:

• when I was originally trying to add my own filter rules to "xnut-nospam.conf" I was getting syntax errors upon NUT start-up, presumably because what I was adding was wrong. After adding the lines you suggested above, I no longer receive those errors so that is a good sign
• I've looked for the /var/log/nut-spam file through Krusader and I simply can't find it. I had NUT running overnight with "Enable Rule-Based Syslog Filters" set to Yes, so I would have at least expected the file to have been created. Is it possible there might be some sort of permission issue that's preventing any of these lines from executing?

Attaching my current xnut-nospam.conf for reference. Thanks again for the help!

 

 

EDIT: adding an additional screenshot of "errors". I believe some of these should be captured by the filters in xnut-nospam.conf which seems to indicate that none of the filters are working in my case

Edited October 28, 20241 yr by cinsun42
added screenshot

4 hours ago, cinsun42 said:

 

Unfortunately this doesn't seem to have worked for me, I'm still getting the same errors populating in syslog. This is after adding the lines above and restarting NUT several times with Enable Rule-Based Syslog Filters: "Yes"

 

Some things I've noticed that may or may (or may not) be helpful:

• when I was originally trying to add my own filter rules to "xnut-nospam.conf" I was getting syntax errors upon NUT start-up, presumably because what I was adding was wrong. After adding the lines you suggested above, I no longer receive those errors so that is a good sign
• I've looked for the /var/log/nut-spam file through Krusader and I simply can't find it. I had NUT running overnight with "Enable Rule-Based Syslog Filters" set to Yes, so I would have at least expected the file to have been created. Is it possible there might be some sort of permission issue that's preventing any of these lines from executing?

Attaching my current xnut-nospam.conf for reference. Thanks again for the help!

 

 

EDIT: adding an additional screenshot of "errors". I believe some of these should be captured by the filters in xnut-nospam.conf which seems to indicate that none of the filters are working in my case

Welp, I don't want to waste your time with any of this. I ended up trying a different USB cable on a whim and those errors have stopped it seems. That said, it does seem like the ability to suppress the syslog errors is not working for me, but I guess I won't worry about that until the need arises.

 

Thanks again for your help!

 

EDIT AGAIN: I spoke too soon. I'm now getting a bunch of the data stale messages, but as stated previously it does not seem like the syslog filtering function is working for me. Screenshot attached for ref

Edited October 28, 20241 yr by cinsun42
new error messages attached

12 hours ago, cinsun42 said:

Welp, I don't want to waste your time with any of this. I ended up trying a different USB cable on a whim and those errors have stopped it seems. That said, it does seem like the ability to suppress the syslog errors is not working for me, but I guess I won't worry about that until the need arises.

 

Thanks again for your help!

 

EDIT AGAIN: I spoke too soon. I'm now getting a bunch of the data stale messages, but as stated previously it does not seem like the syslog filtering function is working for me. Screenshot attached for ref

 

Hm, that's really weird, because I tested those lines and they worked for me.

Can you post the NUT Debug Package that's located in "NUT Settings"?

On 10/28/2024 at 11:36 PM, Rysz said:

 

Hm, that's really weird, because I tested those lines and they worked for me.

Can you post the NUT Debug Package that's located in "NUT Settings"?

 

Here you go, thank you!

 

Edited October 30, 20241 yr by cinsun42

13 hours ago, cinsun42 said:

 

Here you go, thank you!

nut-debug-20241029085202.zip 182.09 kB · 0 downloads

 

That's very strange, it all seems correctly set, and it works for me with the exact same configuration file:

But there's a lot of rsyslogd-related networking errors in your SYSLOG, do you use a remote SYSLOG server?
Did you maybe manually edit the rsyslogd configuration and perhaps put the remote line above the filter includes?

 

Apart from the logs situation, I saw you have some power saving features enabled (powertop, also /power/control settings inside /boot/config/go) - these can cause such connection instabilities, so might be worth a try to remove those (temporarily) and see if the situation improves.

 

15 hours ago, Rysz said:

 

That's very strange, it all seems correctly set, and it works for me with the exact same configuration file:

But there's a lot of rsyslogd-related networking errors in your SYSLOG, do you use a remote SYSLOG server?
Did you maybe manually edit the rsyslogd configuration and perhaps put the remote line above the filter includes?

 

Apart from the logs situation, I saw you have some power saving features enabled (powertop, also /power/control settings inside /boot/config/go) - these can cause such connection instabilities, so might be worth a try to remove those (temporarily) and see if the situation improves.

 

I fixed it!

 

To start, yes I do have a remote syslog server running. While that wasn't exactly the culprit, the fact that you mentioned it along with the syslogd configuration had me digging through all my syslog config files. It turns out there was a bug in how rsyslog.conf was written sometime before unraid 6.9.x (issue linked below), which would inadvertently reset the filtering rules after custom rules has been applied.

 

After deleting rsyslog.conf and rsyslog.cfg from flash, the files were recreated properly after accessing the syslog configuration in settings. The filters are now working!

 

Thanks again for the support, there's no way I would have sorted this out through blind troubleshooting.

 

 

Edited October 30, 20241 yr by cinsun42

8 hours ago, cinsun42 said:

I fixed it!

 

To start, yes I do have a remote syslog server running. While that wasn't exactly the culprit, the fact that you mentioned it along with the syslogd configuration had me digging through all my syslog config files. It turns out there was a bug in how rsyslog.conf was written sometime before unraid 6.9.x (issue linked below), which would inadvertently reset the filtering rules after custom rules has been applied.

 

After deleting rsyslog.conf and rsyslog.cfg from flash, the files were recreated properly after accessing the syslog configuration in settings. The filters are now working!

 

Thanks again for the support, there's no way I would have sorted this out through blind troubleshooting.

 

 

 

Thanks a lot for getting back to us with the solution, I never even knew about this.

This'll be very helpful to know in the future, thanks again and glad you got it resolved.

Need your help guys.

Where can i find the option to set the shutdown mode? I wanted to set it to shutdown at 20% battery left but i'm not finding the option.

 

1 hour ago, Jonilive said:

Need your help guys.

Where can i find the option to set the shutdown mode? I wanted to set it to shutdown at 20% battery left but i'm not finding the option.

 

 

These options are not available in manual configuration mode (which is just "bare NUT" without extras). If you are in manual configuration mode because your UPS needs special settings within UPS.CONF, you can switch to "Enable Manual Configuration": "For UPS Driver", where you can keep a custom UPS.CONF, but still have the rest controlled via the GUI (and those options also available).

Thanks! Didn't noticed the manual configuration was on.

Hi all,

Probably been asked a 1000 times so I apologise.

 

New to this.  Have just connected my OptiUPS ES800C via USB to my UNRAID box and installed the NUT plugin but I cannot get the right driver.  When checking the log it suggests I use the "powercom" driver but it doesnt appear in the list of the selectable options and i try the search for powercom and it says it detected nothing.

 

Any help greatly appreciated.

3 minutes ago, Dwarfboysim said:

Hi all,

Probably been asked a 1000 times so I apologise.

 

New to this.  Have just connected my OptiUPS ES800C via USB to my UNRAID box and installed the NUT plugin but I cannot get the right driver.  When checking the log it suggests I use the "powercom" driver but it doesnt appear in the list of the selectable options and i try the search for powercom and it says it detected nothing.

 

Any help greatly appreciated.

 

 

Just choose "custom (not listed)" and write the driver name in the field appearing to the right. 🙂