yonesmit

Same problem here. In tests all works ok, windows sync, ios sync, all was ok. When I write 5GB to windows synced folder started correctly but after some time it stops and Unraid became unresponsive. I had to reboot from command line and forced to do a parity check. It's a shame because I liked due to simplicity. Any chance this get fixed? Seems a unraid problem because I don't see reports of this problem in other platforms. Best Regards

I know it's not related to NUT plugin, even not related to NUT. The problem is with the kernel unraid is using, but I was suggesting that may be you could add to plugin some retries when loading the driver fails.... more people can have this issue and will not find a solution. Meanwhile, on my side, I fixed with a script that retries it..... Best Regards, nut-autofix.sh syslog.log

Hi, I have a problem with my UPS and unraid since I updated to version 7. The issue appear when I have a power outage or when I start the server from power off state, when I restart the server all runs fine. When this happen I have the following log: Oct 27 09:43:48 hpnas rc.nut: Writing NUT configuration... Oct 27 09:43:49 hpnas rc.nut: Updating permissions for NUT... Oct 27 09:43:49 hpnas rc.nut: Adding UDEV lines to rc.6 for NUT... Oct 27 09:43:49 hpnas rc.nut: Adding UPS shutdown lines to rc.6 for NUT... Oct 27 09:43:50 hpnas rc.nut: Checking if the NUT Runtime Statistics Module should be enabled... Oct 27 09:43:50 hpnas rc.nut: Disabling the NUT Runtime Statistics Module... Oct 27 09:43:51 hpnas rc.nut: Network UPS Tools upsdrvctl - UPS driver controller 2.8.4 release Oct 27 09:43:51 hpnas rc.nut: Network UPS Tools 2.8.4 release - Generic HID driver 0.67 Oct 27 09:43:51 hpnas rc.nut: USB communication driver (libusb 1.0) 0.50 Oct 27 09:43:51 hpnas rc.nut: No matching HID UPS found Oct 27 09:43:51 hpnas rc.nut: Driver failed to start (exit status=1 The config is correct but UPS is not foud. I look in syslog and find this log: Oct 27 09:42:36 hpnas kernel: usb 3-1.6: new low-speed USB device number 4 using ehci-pci Oct 27 09:42:36 hpnas kernel: hid-generic 0003:06DA:FFFF.0001: hiddev96,hidraw0: USB HID v1.00 Device [PPC Offline UPS] on usb-0000:00:1a.0-1.6/input0 Oct 27 09:42:36 hpnas kernel: usb 3-1.6: USB disconnect, device number 4 Oct 27 09:42:36 hpnas kernel: usb 3-1.6: new low-speed USB device number 5 using ehci-pci Oct 27 09:42:36 hpnas kernel: hid-generic 0003:06DA:FFFF.0002: hiddev96,hidraw0: USB HID v1.00 Device [PPC Offline UPS] on usb-0000:00:1a.0-1.6/input0 Oct 27 09:42:36 hpnas kernel: usb 3-1.6: USB disconnect, device number 5 Oct 27 09:42:40 hpnas kernel: usb 3-1.6: new low-speed USB device number 6 using ehci-pci Oct 27 09:42:40 hpnas kernel: hid-generic 0003:06DA:FFFF.0003: hiddev96,hidraw0: USB HID v1.00 Device [PPC Offline UPS] on usb-0000:00:1a.0-1.6/input0 Oct 27 09:42:54 hpnas kernel: usb 3-1.6: USB disconnect, device number 6 UPS is constantly connecting and disconnecting!! I think this happens since I updated to Unraid 7.0. Now If I manually start the plugin when UPS is connected it runs as expected Oct 27 09:52:33 hpnas rc.nut: Writing NUT configuration... Oct 27 09:52:35 hpnas rc.nut: Updating permissions for NUT... Oct 27 09:52:35 hpnas rc.nut: Checking if the NUT Runtime Statistics Module should be enabled... Oct 27 09:52:35 hpnas rc.nut: Disabling the NUT Runtime Statistics Module... Oct 27 09:52:36 hpnas rc.nut: Network UPS Tools upsdrvctl - UPS driver controller 2.8.4 release Oct 27 09:52:36 hpnas rc.nut: Network UPS Tools 2.8.4 release - Generic HID driver 0.67 Oct 27 09:52:36 hpnas rc.nut: USB communication driver (libusb 1.0) 0.50 Oct 27 09:52:36 hpnas rc.nut: Using subdriver: Phoenixtec/Liebert HID 0.41 Oct 27 09:52:37 hpnas rc.nut: Listening on socket /var/run/nut/usbhid-ups-salicru Oct 27 09:52:38 hpnas rc.nut: Network UPS Tools upsd 2.8.4 release Oct 27 09:52:38 hpnas rc.nut: listening on 0.0.0.0 port 3493 Oct 27 09:52:38 hpnas rc.nut: Connected to UPS [salicru]: usbhid-ups-salicru Oct 27 09:52:38 hpnas rc.nut: Found 1 UPS defined in ups.conf Oct 27 09:52:38 hpnas rc.nut: Network UPS Tools upsmon 2.8.4 release Oct 27 09:52:38 hpnas rc.nut: UPS: [email protected] (primary) (power value 1) Oct 27 09:52:38 hpnas rc.nut: Using power down flag file /etc/nut/killpower Would be possible to implement some sort of retry drive loading? or waiting until UPS is connected before drive loading? Thanks in advance Best Regards

Hi! thanks to @VladoPortos for making the plugin working again. I have the same issue with compose dockers reported in previous message by @Messias, please @VladoPortos help us adding the changes suggested by him when you have some spare time, and thanks again for your work. As others said I think this plugin should be part of Unraid product!! It has been widely promoted by SpaceInvader in his videos, now it's not working and in the Apps it's a broken version!!! Please @Squid help us to get this working, at last the current fixed version. Thanks in advance Best Regards

I had same problem

I never said it was a bug, it's simply a cosmetic option I would like to have: not have the icon loading all the time. The problem is not from plugin, it comes from NUT, the own usbhid driver use this code: if ((ups_status & STATUS(CHRG)) && !(ups_status & STATUS(FULLYCHARGED))) { status_set("CHRG"); /* charging */ } The problem is that FULLYCHARGED status is only supported by some subdrivers, the others will display always as CHRG. Note that usbhid driver is using FULLYCHARGED to stop displaying "CHRG" even the ups status is CHRG. The same i was requesting. No problem I can live with it. So, the real fact is that the info provided by NUT is only as real as the driver used is supported. Some drivers are not fully developed or simply can't support all features. And also NUT is doing some assumptions: for example that UPS stop charging when status is FULLYCHARGED although the status is also CHRG. May be I should request it to NUT developers. Thanks for your work.

He explained it here: I need to use it because the is the only 2.80 version that works correctly with my UPS.

Hi, I have a suggestion to enhance your plugin, at last for me... My UPS when it's connected to power always display status as: ups.status: OL CHRG So the footer icon always is displayed as battery charging even if battery charge is 100%. I think that if value of battery.charge is 100 you should display icon as battery-full and not battery-charging. This can be easily done when you select the icon to display adding a check. Also in this way I get a chance to get the replacement battery icon, now it will never be displayed in my UPS. Thanks for your work Best Regards,

Hi I installed your version, unfortunately the 2.8.0 version included fails with my UPS. This is the output of the shutdown command: root@hpnas:~# sudo /usr/sbin/upsdrvctl -u root shutdown Network UPS Tools - UPS driver controller 2.8.0-signed Network UPS Tools - Generic HID driver 0.47 (2.8.0-signed) USB communication driver (libusb 1.0) 0.43 Using subdriver: Phoenixtec/Liebert HID 0.41 Initiating UPS shutdown Shutdown failed! Driver failed to start (exit status=1) Rysz plugin contains a newer 2.8.0.1 version that correctly shutdown my UPS: root@hpnas:~# sudo /usr/sbin/upsdrvctl -u root shutdown Network UPS Tools - UPS driver controller 2.8.0.1 Network UPS Tools - Generic HID driver 0.50 (2.8.0.1) USB communication driver (libusb 1.0) 0.45 Can't open /var/run/nut/usbhid-ups-salicru: No such file or directory Using subdriver: Phoenixtec/Liebert HID 0.41 Initiating UPS shutdown The old 2.7.4 version also correctly shutdown my UPS, but it detects it as another subdriver. Seems that there are many changes from 2.7.4 to 2.8.0 (2.7.4 is very old) and they includes this. The shutdown command support in new subdriver has been added in late revisions. Please, use the new 2.8.0.1 version or newer in new plugin. Thanks

The versions that works ok for me are: - any plugin using 2.7.4 networkupstools - Rysz plugin running 2.8.0 (latest version) found in this post: The problem is 2.7.4 is quite old and 2.8.0 is being developed since a lot of time so you can find many different versions. The first ones (like the ones used in your 2.8.0 version) don't work correctly with my UPS. That's why i say that would be good to update the package frequently, not only the plugin. Thanks for your work. Best Regards

Although I didn't reported it I also had problems with previous 2.8.0 plugin. It detect my UPS as another subdriver and the shutdown command fails. I tested with other more recent versions of 2.8.0 and it works. And also works OK with your new version!!! I think that the 2.8.0 version used in previous plugin was very old. Please use this version of Network UPS Tools with 2.8.0 plugin and would be great if there is some way to update it when new versions appear, or to the latest git version... Thanks for your work Best Regards

Hi, I confirm that 6.12.4-rc18 fixes the problem with NUT plugin and system shutdown. Thanks!

Thanks a lot for testing and also for reporting it as a bug. I also think this is a bug, /usr and /lib should not be unmounted! Remounting it imply to reinstall the plugins!! Temporarily I use this script to shutdown my UPS: #!/bin/bash FILE_TO_PATCH="/etc/rc.d/rc.nut" CMD_TO_COMMENT="/usr/sbin/upsdrvctl shutdown" CMD_TO_ADD="/root/usbhid-ups -u root -s ups -x port=auto -x offdelay=20 -x ondelay=30 -k" cp /usr/libexec/nut/usbhid-ups /root/usbhid-ups chmod 755 /root/usbhid-ups if grep -q "$CMD_TO_ADD" $FILE_TO_PATCH; then echo "file $FILE_TO_PATCH already patched" else sed -i "s|\(^.*\)\($CMD_TO_COMMENT\)|\1#\2\n\1$CMD_TO_ADD|" $FILE_TO_PATCH echo "patching $FILE_TO_PATCH done" fi CMD_TO_ADD is for my UPS and need to be correctly setup for others. Also if UPS uses other driver then the correct driver should be used. I hope they "fix" the issue soon. Best Regards

As a temporary solution I will make a script to copy usbhid-ups binary (my ups driver) to /etc/nut and then patch /etc/rc.d/rc.nut to stop calling "upsdrvctl shutdown" and call to this binary directly to shutdown ups. Unfortunately the shutdown command is different for every UPS (depending on driver used and UPS manufacturer) so this should be only a temp solution. It's strange nobody has complained about this... and nobody using 6.12.x confirmed if his rc.6 contains or not the line: /bin/umount -v -a Best Regards,

Are you running unraid 6.12.x ? In both rc.0 and rc.6 i find: # Unmount local file systems: echo "Unmounting local file systems:" /bin/umount -v -a may be this is a new addition in 6.12 (because as I said the UPS power off was working ok with my ups when I tested time ago). And also UPS shutdown when i run from command line: upsdrvctl -u root shutdown I looked my plugins and I don't find anyone adding the "umount -v -a" command so it must be from unraid 6.12 Please, can anyone running unraid 6.12.x confirm if "/bin/umount -v -a" is present in file /etc/rc.d/rc.6 or not? Thnaks in advance