demonrik

Confirming all is good for me with this update Both UnRAID servers able to select any of the UPS devices thanks @Rysz for the very fast turnaround.

look forward to the update. appreciate you looking

I had it the same first - then changed it to something else just in case. Changed it back and no success in updating the GUI I spun up the disks and get a new details cp: cannot create regular file '/tmp/nut-debug/unraid-version.txt': No such file or directory cp: cannot create regular file '/tmp/nut-debug/PLUGIN/nut-dw.plg.txt': No such file or directoryAnd no - is not a UniFi - is an APC UPS Running the command line looks good # upsc [email protected]:34493 battery.charge: 100 battery.charge.low: 66 battery.mfr.date: 1980/01/01 battery.runtime: 1105 battery.runtime.low: 120 battery.type: PbAc battery.voltage: 27.7 battery.voltage.nominal: 24.0 device.mfr: American Power Conversion device.model: Back-UPS BGM2200B-GR device.serial: 9B2428A19235 device.type: ups driver.name: usbhid-ups driver.parameter.pollfreq: 30 driver.parameter.pollinterval: 2 driver.parameter.port: auto driver.parameter.synchronous: auto driver.version: 2.8.0 driver.version.data: APC HID 0.98 driver.version.internal: 0.47 driver.version.usb: libusb-1.0.24 (API: 0x1000108) input.sensitivity: medium input.transfer.high: 298 input.transfer.low: 176 input.transfer.reason: input voltage out of range input.voltage: 236.0 input.voltage.nominal: 230 ups.beeper.status: enabled ups.delay.shutdown: 20 ups.firmware: 481600G5-481700G2 ups.load: 21 ups.mfr: American Power Conversion ups.mfr.date: 2024/07/16 ups.model: Back-UPS BGM2200B-GR ups.productid: 0002 ups.realpower.nominal: 1320 ups.serial: 9B2428A19235 ups.status: OL DISCHRG ups.test.result: Done and passed ups.timer.reboot: 0 ups.timer.shutdown: -1 ups.vendorid: 051d

I have an RPi running docker containers of NUT (upshift/nut-upsd:2.8.0) for each UPS I have in my UPS farm. Each UPS is exposed to an individual port for clients to hook on to and monitor - e.g. NAS, HA, etc. However, I just can't seem to connect my UnRAID NAS (7.1.4) with the 2025.09.07 plugin to any of the NUT instances. my other non UnRAID clients are working and can see battery charge, voltage, etc.. My NUT Settings ( I get an error when trying to create the NUT debug package :( ERROR: The NUT Debug Package Generation Script has failed - no response from the bash backend. ) Network UPS Tools Backend: nut-2.8.4-x86_64-1stable.ssl31 Network UPS Tools Backend Switch: default (2.8.4 stable) Start Network UPS Tools Service: Yes Enable USB Power Management Override: No Enable Rule-Based Syslog Filters: No Redirection for NUT Service Logs: Default (to Syslog) Persist Redirected Logs on Reboot: No Enable Manual Configuration: Yes UPS Name: nutupsAnd the only CONF file I've changed is upsmon.conf to MONITOR [email protected]:34493 1 demonrik nutserver slave SHUTDOWNCMD "/sbin/poweroff" POWERDOWNFLAG "/etc/nut/no_killpower" NOTIFYCMD "/usr/sbin/nut-notify" NOTIFYFLAG ONBATT SYSLOG+EXEC NOTIFYFLAG ONLINE SYSLOG+EXEC NOTIFYFLAG REPLBATT SYSLOG+EXECWith no DEBUG_MIN in the upsmon.conf it looks like it has trouble accessing. Oct 27 08:47:41 INX-NAS4 rc.nut: Network UPS Tools upsdrvctl - UPS driver controller 2.8.4 release Oct 27 08:47:41 INX-NAS4 rc.nut: Can't open /var/run/nut/usbhid-ups-nut-srvr.pid: No such file or directory Oct 27 08:47:41 INX-NAS4 rc.nut: Can't open /var/run/nut/usbhid-ups-auto.pid either: No such file or directory Oct 27 08:56:16 INX-NAS4 ool www[1823930]: /usr/local/emhttp/plugins/nut-dw/scripts/start Oct 27 08:56:17 INX-NAS4 rc.nut: Writing NUT configuration... Oct 27 08:56:18 INX-NAS4 rc.nut: Updating permissions for NUT... Oct 27 08:56:18 INX-NAS4 rc.nut: Checking if the NUT Runtime Statistics Module should be enabled... Oct 27 08:56:18 INX-NAS4 rc.nut: Disabling the NUT Runtime Statistics Module... Oct 27 08:56:19 INX-NAS4 rc.nut: Network UPS Tools upsmon 2.8.4 release Oct 27 08:56:19 INX-NAS4 rc.nut: UPS: [email protected]:34493 (secondary) (power value 1) Oct 27 08:56:19 INX-NAS4 rc.nut: Using power down flag file /etc/nut/no_killpower Oct 27 08:56:19 INX-NAS4 upsmon[1824603]: Startup successful Oct 27 08:56:19 INX-NAS4 upsmon[1824603]: Warning: running as one big root process by request (upsmon -p) Oct 27 08:56:19 INX-NAS4 upsmon[1824603]: Login on UPS [[email protected]:34493] failed - got [ERR ACCESS-DENIED]setting 'DEBUG_MIN 6' it looks like it has same access issue - however it does appear to read some stats Oct 27 08:59:00 INX-NAS4 rc.nut: Network UPS Tools upsdrvctl - UPS driver controller 2.8.4 release Oct 27 08:59:00 INX-NAS4 rc.nut: Can't open /var/run/nut/usbhid-ups-nut-srvr.pid: No such file or directory Oct 27 08:59:00 INX-NAS4 rc.nut: Can't open /var/run/nut/usbhid-ups-auto.pid either: No such file or directory Oct 27 08:59:03 INX-NAS4 rc.nut: Network UPS Tools upsmon 2.8.4 release Oct 27 08:59:03 INX-NAS4 rc.nut: UPS: [email protected]:34493 (secondary) (power value 1) Oct 27 08:59:03 INX-NAS4 rc.nut: Using power down flag file /etc/nut/no_killpower Oct 27 08:59:03 INX-NAS4 rc.nut: 0.000023#011[D1:1830988] debug level is '6' Oct 27 08:59:03 INX-NAS4 rc.nut: 0.000028#011[D1:1830988] will use a shutdown command (SHUTDOWNCMD): '/sbin/poweroff' Oct 27 08:59:03 INX-NAS4 rc.nut: 0.000029#011[D1:1830988] will use custom notification command (NOTIFYCMD): '/usr/sbin/nut-notify' Oct 27 08:59:03 INX-NAS4 upsmon[1830989]: Startup successful Oct 27 08:59:03 INX-NAS4 upsmon[1830989]: Warning: running as one big root process by request (upsmon -p) Oct 27 08:59:03 INX-NAS4 upsmon[1830989]: [D1:1830989] Saving PID 1830989 into /var/run/nut/upsmon.pid Oct 27 08:59:03 INX-NAS4 upsmon[1830989]: [D1:1830989] upsnotify: failed to notify about state NOTIFY_STATE_READY_WITH_PID: no notification tech defined, will not spam more about it Oct 27 08:59:03 INX-NAS4 upsmon[1830989]: [D1:1830989] Trying to connect to UPS [[email protected]:34493] Oct 27 08:59:03 INX-NAS4 upsmon[1830989]: Login on UPS [[email protected]:34493] failed - got [ERR ACCESS-DENIED] Oct 27 08:59:03 INX-NAS4 upsmon[1830989]: [D3:1830989] Current power value: 1 Oct 27 08:59:03 INX-NAS4 upsmon[1830989]: [D3:1830989] Minimum power value: 1 Oct 27 08:59:03 INX-NAS4 upsmon[1830989]: [D4:1830989] Beginning 5-sec delay between main loop cycles Oct 27 08:59:08 INX-NAS4 upsmon[1830989]: [D4:1830989] 5-sec delay between main loop cycles finished, took 5.000160 Oct 27 08:59:08 INX-NAS4 upsmon[1830989]: [D2:1830989] pollups: [email protected]:34493 Oct 27 08:59:08 INX-NAS4 upsmon[1830989]: [D3:1830989] get_var: [email protected]:34493 / status Oct 27 08:59:08 INX-NAS4 upsmon[1830989]: [D3:1830989] get_var: [email protected]:34493 / buzzword Oct 27 08:59:08 INX-NAS4 upsmon[1830989]: [D3:1830989] get_var: [email protected]:34493 / X-buzzword Oct 27 08:59:08 INX-NAS4 upsmon[1830989]: [D2:1830989] parse_status: [OL DISCHRG] Oct 27 08:59:08 INX-NAS4 upsmon[1830989]: [D3:1830989] parsing: [OL] Oct 27 08:59:08 INX-NAS4 upsmon[1830989]: [D3:1830989] ups_on_line: [email protected]:34493 (first time) Oct 27 08:59:08 INX-NAS4 upsmon[1830989]: [D3:1830989] parsing: [DISCHRG] Oct 27 08:59:08 INX-NAS4 upsmon[1830989]: [D4:1830989] Known and ignored status token: [DISCHRG] Oct 27 08:59:08 INX-NAS4 upsmon[1830989]: [D3:1830989] Handled 2 status tokens Oct 27 08:59:08 INX-NAS4 upsmon[1830989]: [D3:1830989] Current power value: 1 Oct 27 08:59:08 INX-NAS4 upsmon[1830989]: [D3:1830989] Minimum power value: 1 Oct 27 08:59:08 INX-NAS4 upsmon[1830989]: [D4:1830989] Beginning 5-sec delay between main loop cyclesi.e. it clearly sees on this UPS (an APC BGM2200B-GR) it's OL and DISCHARGing. But no update of any details anywhere on UnRAID I do see the upsnotify failure and also have that backend issue creating the debug package and wonder if it's some permission setting somewhere gone wrong. I have tried removing and reinstalling the plugin several times on 2 different UnRAID NASes with identical results and am not even sure where to look next. Any help on getting this working greatly appreciated.