fezster

I created an issue and PR to fix this: https://github.com/stephondoestech/unraid-config-guardian/issues/40 You can use my fork to build locally until the PR is approved and merged

I tried downgrading the plugin to version 4.27.2, which did not work. However, I had another server running an even older version of the plugin and installing this version has fixed it for now (until they fix the latest version): plugin remove dynamix.unraid.net.plg plugin install https://github.com/unraid/api/releases/download/v4.25.2/dynamix.unraid.net.plg

Unraid Connect version 2025.12.15.2141 doesn't seem to be working on Unraid 6.12.15. The status just says as "launching". Diagnostics attached. unraid-api status unraid-api logs sm1-diagnostics-20251216-1152.zip

Any advice on how to diagnose this? Are there any logs for dockerman's update check?

I'm running the cuda image of immich: ghcr.io/imagegenius/immich:cuda Despite the digest being different to the latest version, the Docker tab never shows an update. I have to "force update". Any way I can diagnose this? # docker images --digests|grep immich ghcr.io/imagegenius/immich cuda sha256:5ed251756b296282409c5518fce3589fa469b29ad1648d0fe290952311b462de Latest digest for cuda: https://github.com/imagegenius/docker-immich/pkgs/container/immich/514095499?tag=cuda cuda Latestsha256:62d8c9e4428c09464a40485b87def1b9c9df25210b9ecd58facb00f93ea82b3b

@Rysz Different question here to above. I had NUT restarting every hour, as I said in my post a few days ago, to see if that would resolve the staleness/disconnects. This restart has been working fine for the past few days. However - this morning, I realised my UPS had reported on battery and the server had shutdown. I did not have any power outage. Looking at the previous syslog (which is helpfully saved on the flash), it looks like after NUT restarted, the UPS reported on battery for some reason. Have you ever come across this? Jun 9 08:47:01 SM1 root: Stopping the NUT services... Jun 9 08:47:01 SM1 upsmon[2921]: Signal 15: exiting Jun 9 08:47:01 SM1 root: Network UPS Tools upsmon 2.8.2 Jun 9 08:47:01 SM1 upsd[2918]: User [email protected] logged out from UPS [ups] Jun 9 08:47:02 SM1 upsd[2918]: mainloop: Interrupted system call Jun 9 08:47:02 SM1 upsd[2918]: Signal 15: exiting Jun 9 08:47:02 SM1 root: Network UPS Tools upsd 2.8.2 Jun 9 08:47:04 SM1 usbhid-ups[2912]: Signal 15: exiting Jun 9 08:47:04 SM1 usbhid-ups[2912]: WARNING: send_to_all: write 38 bytes to socket 13 failed (ret=-1), disconnecting: Broken pipe Jun 9 08:47:05 SM1 root: fopen /var/run/nut/usbhid-ups-ups.pid: No such file or directory Jun 9 08:47:05 SM1 root: Network UPS Tools - UPS driver controller 2.8.2 Jun 9 08:47:08 SM1 root: WARNING: NUT was user-configured to disable power management for all USB devices. Jun 9 08:47:08 SM1 root: WARNING: NUT is now forcing all USB devices to permanent [on] power state as requested... Jun 9 08:47:09 SM1 root: Writing NUT configuration... Jun 9 08:47:11 SM1 root: Updating permissions for NUT... Jun 9 08:47:11 SM1 root: Checking if the NUT Runtime Statistics Module should be enabled... Jun 9 08:47:11 SM1 root: Disabling the NUT Runtime Statistics Module... Jun 9 08:47:12 SM1 root: Using subdriver: CyberPower HID 0.80 Jun 9 08:47:12 SM1 root: Network UPS Tools - Generic HID driver 0.53 (2.8.2) Jun 9 08:47:12 SM1 root: USB communication driver (libusb 1.0) 0.47 Jun 9 08:47:14 SM1 root: using 'battery.charge' to set battery low state Jun 9 08:47:14 SM1 usbhid-ups[19996]: using 'battery.charge' to set battery low state Jun 9 08:47:14 SM1 usbhid-ups[19996]: using 'battery.runtime' to set battery low state Jun 9 08:47:14 SM1 root: using 'battery.runtime' to set battery low state Jun 9 08:47:14 SM1 usbhid-ups[20002]: Startup successful Jun 9 08:47:14 SM1 root: Network UPS Tools - UPS driver controller 2.8.2 Jun 9 08:47:15 SM1 root: fopen /var/run/nut/upsd.pid: No such file or directory Jun 9 08:47:15 SM1 root: Could not find PID file '/var/run/nut/upsd.pid' to see if previous upsd instance is already running! Jun 9 08:47:15 SM1 root: listening on 0.0.0.0 port 3493 Jun 9 08:47:15 SM1 upsd[20007]: listening on 0.0.0.0 port 3493 Jun 9 08:47:15 SM1 upsd[20007]: Connected to UPS [ups]: usbhid-ups-ups Jun 9 08:47:15 SM1 root: Connected to UPS [ups]: usbhid-ups-ups Jun 9 08:47:15 SM1 usbhid-ups[20002]: sock_connect: enabling asynchronous mode (auto) Jun 9 08:47:15 SM1 upsd[20007]: Found 1 UPS defined in ups.conf Jun 9 08:47:15 SM1 root: Found 1 UPS defined in ups.conf Jun 9 08:47:15 SM1 upsd[20008]: Startup successful Jun 9 08:47:15 SM1 root: fopen /var/run/nut/upsmon.pid: No such file or directory Jun 9 08:47:15 SM1 root: Could not find PID file to see if previous upsmon instance is already running! Jun 9 08:47:15 SM1 root: UPS: [email protected] (primary) (power value 1) Jun 9 08:47:15 SM1 root: Using power down flag file /etc/nut/killpower Jun 9 08:47:15 SM1 upsmon[20011]: Startup successful Jun 9 08:47:15 SM1 upsmon[20011]: Warning: running as one big root process by request (upsmon -p) Jun 9 08:47:15 SM1 upsd[20008]: User [email protected] logged into UPS [ups] Jun 9 08:47:15 SM1 upsmon[20011]: UPS [email protected] on battery Jun 9 08:47:15 SM1 nut-notify: [ups] UPS is on battery. The system will shutdown in 180 seconds.

@Rysz Given your expertise on this, would like some advice. From my previous posts, you may know I have an unconventional setup - Im running Unraid on Esxi as a VM and I think this may the cause of my USB disconnects. When I had the same data staleness this time, rather than unplug the USB, I simply rebooted the Unraid VM. And the UPS worked correctly after the reboot. This tells me it is not a problem with the cable/connection and (most likely) not a problem with a disconnection on the host machine either. Rather some kind of Virtual Machine oddity. Here's the advice question. I came across these commands to force a USB disconnect/reconnect in UNRAID: echo 2-2.1 > /sys/bus/usb/drivers/usb/unbind echo 2-2.1 > /sys/bus/usb/drivers/usb/bind #restart NUT /etc/rc.d/rc.nut restart 2>&1 | logger I'm going to try this the next time the problem occurs and hopefully automate it, if it works. My question is - do you think this might work (given what I said above)? And/or do you have any other advice on how to force the USB to reconnect (similar to what would happen when Unraid reboots)? Thank you!

Using USB 2.0 port. Have tried a different cable. The challenge is that it's not easily reproducible, so I think it's fixed, but then it randomly happens again. I'm following some advice I found in this thread: https://forum.netgate.com/topic/31120/nut-data-stale/13. It's over 10 years old, but I've set a user script to restart nut every hour (perhaps that might help). #!/bin/bash /etc/rc.d/rc.nut restart 2>&1 | logger

Still struggling with random disconnects of a CYBERPOWER BR700ELCD. I tried adding the pollonly flag, as suggested on the manual page: https://networkupstools.org/docs/man/usbhid-ups.html, but this did not help. I realise this is not an Unraid/NUT issue, but wondering if anyone has any other suggestions? The disconnects are completely random - sometimes it goes weeks, other times only a day. And I have to unplug/replug the USB cable to get it to work again (a restart of NUT does not help). Jun 3 16:14:43 SM1 usbhid-ups[19008]: nut_libusb_get_report: Input/Output Error Jun 3 16:14:43 SM1 kernel: usb 2-2.1: USB disconnect, device number 41 Jun 3 16:14:45 SM1 kernel: usb 2-2.1: new low-speed USB device number 42 using uhci_hcd Jun 3 16:14:46 SM1 kernel: hid-generic 0003:0764:0501.0028: hiddev96,hidraw1: USB HID v1.10 Device [CPS BR700ELCD] on usb-0000:02:00.0-2.1/ input0 Jun 3 16:14:53 SM1 kernel: usb 2-2.1: USB disconnect, device number 42 Jun 3 16:14:56 SM1 usbhid-ups[19008]: libusb1: Could not open any HID devices: insufficient permissions on everything Jun 3 16:14:56 SM1 upsd[19125]: Data for UPS [ups] is stale - check driver Jun 3 16:14:57 SM1 kernel: usb 2-2.1: new low-speed USB device number 43 using uhci_hcd Jun 3 16:14:58 SM1 kernel: hid-generic 0003:0764:0501.0029: hiddev96,hidraw1: USB HID v1.10 Device [CPS BR700ELCD] on usb-0000:02:00.0-2.1/ input0 Jun 3 16:14:59 SM1 upsmon[19129]: Poll UPS [[email protected]] failed - Data stale Jun 3 16:14:59 SM1 upsmon[19129]: Communications with UPS [email protected] lost Jun 3 16:15:04 SM1 upsmon[19129]: Poll UPS [[email protected]] failed - Data stale ups.conf [ups] driver = usbhid-ups port = auto # If not in manual mode, put any additional settings below this line desc = "BR700ELCD" offdelay = 120 ondelay = 0 ignorelb override.battery.charge.low = 20 override.battery.charge.warning = 40 pollinterval = 15 pollfreq = 60

Try enabling "Host access to custom networks" under Settings -> Docker (need to disable Docker first).

Found the new version of the plugin has USB power management override Will see if that may have been the reason for the disconnection and if this setting helps.

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.

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.

Agreed, appreciate the input. On a slightly different topic - I see increased CPU utilization with NUT running. I'm using a Cyberpower BR700ELCD with the usbhid-ups driver. I've changed the pollinterval to 15 which has helped, but I see consistent spikes (which arent there if I shut down NUT). Is this normal? [ups] driver = usbhid-ups port = auto # If not in manual mode, put any additional settings below this line desc = "BR700ELCD" offdelay = 180 ondelay = 0 ignorelb override.battery.charge.low = 20 override.battery.charge.warning = 40 pollinterval = 15

Thank you - I expected as much. I have everything working as required with the GUI settings, so was only looking for an easy way to add an additional script to run as part of the shutdown sequence. It's not easy to modify rc.nut / rc.0 / rc.6 - maybe as a future enhancement a GUI option could be added for an additional script to run just before shutdown? Thanks for this plugin btw!