Rysz

There's lots of USB disconnects in your logs and it seems something is hibernating your UPS periodically - causing the data staleness. I also see you have powertop installed, which is known to cause such issues. Would be best to remove anything powertop related, reboot the system and watch if the problems come back.

Just updated it, should be fixed with the new update. 🙂

No, the first message actually seems to come from the LLDP plugin which tries to send LLDP beacons from virtual interfaces (which doesn't work). That's actually useful information because that needs fixing (will push an update ASAP), so that it only does it from physical interfaces. The second message is normal after uninstallation and will only occur until the page is reloaded because after uninstallation the client side JS footer code is still there and looking for a no longer existing script until you reload the browser page at which point the code will be completely gone.

Sorry to have spawned such a discussion about this, glad that there's such diligent security mechanisms in place so thanks to everyone involved with that and for the hard work of all our contributing developers as well (including of this plugin). Glad to be a part of the Unraid community exactly for those reasons and many more. 🙂

Thanks for getting back to me so quick, makes absolute sense from your perspective and you're right about other plugins, of course, it probably boils down to moderation discretion and where it makes sense and doesn't (which it seems to do in your case). Please also don't get me wrong for pointing this out. I just think it's good to talk about such things especially at this point in time where people are on high alert with everything. I'm probably also a bit more paranoid after the whole XZ situation and one too many security meetings at work.

Is there any reason the program is closed source now? It seems there's been no update to it for a long time, now suddenly there's a new release with a changed PLG location and all the source code was removed from the GitHub repository. The newly released package contains a compiled binary but no source code to go with it. It's one thing to not include source code with binaries where the source code is publicly available (e.g. rclone), but with a self-coded project I'm pretty sure this is against Community Applications rules and in light of recent developments with the XZ Utils backdoor it really makes me nervous (probably unwarranted). I'm sure there's a solid reason and I don't want to throw around accusations at all, but better to get out in front of this. 🙂 It's just seems a bit weird that there was source code before and now it's suddenly removed before a new release is put out after a longer hiatus, the PLG location suddenly changing too... I mean why go to such lengths, inconveniencing the users with a PLG location change, to remove source code? https://github.com/jbrodriguez/controlr https://github.com/jbrodriguez/controlr/pull/36 https://github.com/jbrodriguez/controlr/commit/154360d41dac9591d8064656f8dffc97337fda1e @SpencerJ @Squid

blazer_ser only works with UPS connected via serial cable (that's why it wants a port = physical location of the device). Sorry then we're really out of luck, 2.7.4. was my last idea for this UPS basically 😕

Actually can you try something else - change NUT Backend to "legacy (2.7.4 stable)" in NUT Settings and reboot the system or reinstall NUT. Then try again with same driver (nutdrv_qx) - sometimes the old backend works better with some UPS.

I'm afraid your UPS doesn't seem to be supported at all, it cannot find or communicate with the device. NUT's hardware compatibility list also doesn't list that specific UPS as supported, so unfortunately it seems we're unlucky in this case. You can try with Unraid's "UPS Settings" (which use a different program: APCUPSD) if maybe the device will be detected there - but I'm not very hopeful. 😞

Is this on UNRAID? You have a weird mount setup for that - how do you mount these /netapp/ mounts? Also, are you sure your appdata is at /mnt/appdata ? It's usually on /mnt/user/appdata, /mnt/disk[number]/appdata?! Please check your paths again and possibly put 2>&1 behind your mergerFS commands so you'll also see any errors from stderr.

Please post the NUT Debug Package found in NUT Settings.

Hello, you need to click into this field to pick the configuration file to edit first:

Dynamix System Temperature Probably low priority but a bunch of PHP8 warnings if one of the temperatures is not used: [12-Apr-2024 14:19:41 Europe/Berlin] PHP Warning: Undefined array key 1 in /usr/local/emhttp/plugins/dynamix.system.temp/nchan/system_temp on line 78 [12-Apr-2024 14:19:57 Europe/Berlin] PHP Warning: Undefined array key 1 in /usr/local/emhttp/plugins/dynamix.system.temp/nchan/system_temp on line 78 [12-Apr-2024 14:19:57 Europe/Berlin] PHP Warning: Undefined array key 1 in /usr/local/emhttp/plugins/dynamix.system.temp/include/SystemTemp.php on line 42 [12-Apr-2024 14:20:02 Europe/Berlin] PHP Warning: Undefined array key 1 in /usr/local/emhttp/plugins/dynamix.system.temp/nchan/system_temp on line 78 [12-Apr-2024 14:20:07 Europe/Berlin] PHP Warning: Undefined array key 1 in /usr/local/emhttp/plugins/dynamix.system.temp/nchan/system_temp on line 78 [12-Apr-2024 14:20:12 Europe/Berlin] PHP Warning: Undefined array key 1 in /usr/local/emhttp/plugins/dynamix.system.temp/nchan/system_temp on line 78 [12-Apr-2024 14:20:17 Europe/Berlin] PHP Warning: Undefined array key 1 in /usr/local/emhttp/plugins/dynamix.system.temp/nchan/system_temp on line 78 [12-Apr-2024 14:20:22 Europe/Berlin] PHP Warning: Undefined array key 1 in /usr/local/emhttp/plugins/dynamix.system.temp/nchan/system_temp on line 78

Some UPS do behave better on USB 2.0 ports, so I usually always connect mine on USB 2.0 where possible. Another affected user reported the BX problems stopped for him all of a sudden and without changing anything around. I still haven't gotten my hands on a BX series device to investigate more, at this point I'm really clueless what the UPS is actually doing when it reports these states.

There is nothing in the logs regarding the previous shutdown, please make sure to enable this: And then post the NUT Debug Package again next time you get a shutdown, directly on the first boot after the shutdown. The BX series is known to be bugged (we spoke on GitHub about this) but it shouldn't cause any shutdowns, at least it didn't for any of the other affected people so far. NUT should in general never cause unclean shutdowns (and parity checks) unless something on your server was taking extremely long to stop - resulting in a forced shutdown (but this would also happen without NUT if you press "Shutdown" and something gets stuck). So even if your UPS reported a false power event the shutdown should always have been a clean shutdown. In any case we would need the logs from before the shutdown to really diagnose the problem that led to the unclean shutdown so this is guesswork on my part at best. Regarding the other problems now having stopped on another USB port, I'm guessing the USB port you were previously connecting your UPS to is maybe faulty or the USB cable between the PC and the UPS is in the process of dying. There's a lot of USB related events in the logs, so I'd monitor the situation and if it happens again on the new USB port I'd consider exchanging the cable (can be found on Amazon for around 10$). Sorry I can't really help more at this point, but do report back with new logs in case it happens again.