thecode

@Rysz I apologize for tagging you, did you have a chance to look at the attached diagnostics? Since 7.3.2 the issue happens on another server (again with an Eaton UPS) and very often, so now I can reproduce the problem on two servers once a day both with 2.8.5 and 2.8.4 It is a little bit problematic to be without a working UPS, especially since one of the servers uses ZFS so it is critical to have a UPS shutting down the server before the UPS battery ends and on the other hand I am afraid to downgrade it since I upgraded the ZFS pool. Thanks.

With 2.8.4 there is no segfault error in the log, but it did stopped working after few days, with ups driver debug level 6, the only thing shown in the log is: Jun 17 22:54:34 Tower rc.nut: Network UPS Tools upsdrvctl - UPS driver controller 2.8.4 release Jun 17 22:54:34 Tower rc.nut: Network UPS Tools 2.8.4 release - Generic HID driver 0.67 Jun 17 22:54:34 Tower rc.nut: USB communication driver (libusb 1.0) 0.50 Jun 17 22:54:35 Tower rc.nut: No matching HID UPS found Jun 17 22:54:35 Tower rc.nut: Driver failed to start (exit status=1) Jun 17 22:54:40 Tower kernel: usb 3-2: USB disconnect, device number 3 Jun 17 22:54:41 Tower kernel: usb 3-2: new full-speed USB device number 4 using xhci_hcd Jun 17 22:54:43 Tower kernel: hid-generic 0003:0463:FFFF.0005: hiddev96,hidraw2: USB HID v1.10 Device [EATON 5E] on usb-0000:2c:00.3-2/input0every time I try to start the driver. In the attached debug package the syslog is showing the error using driver 2.8.4 and the syslog-previous shows the error from 2.8.5 I am pretty sure the problem started when I updated Unraid from 7.2.x to to 7.3.1 and not due to NUT package updates. nut-debug-20260617225812.zip EDIT: I switched back the driver to 2.8.5 without reboot of the system and the driver loads correctly (of course still with 2.8.4), I switched back to reboot the system and let it load again with 2.8.5, but I am wondering what does the switch of the driver from 2.8.4 to 2.8.5 without reboot does to fix the issue. Attached another diagnostics now with the device connected. nut-debug-20260617232218.zip Thanks for helping.

Before I saw this answer I bumped into https://github.com/networkupstools/nut/issues/3422 and downgraded the NUT driver to 2.8.4 to see if the issue is related to 2.8.5, it is running with 2.8.4 without errors for 3 days, but it is really random so I will let it run for another week, than switch to 2.8.5 with debug level and post back, thanks for the fast reply.

In the last few weeks (I think it started since updating to Unraid 7.3.1 from 7.2.4) the connection to the UPS stops working after few days, if I try to stop the NUT service and start it again the following error is shown in the log: Jun 10 11:30:53 Tower ool www[729600]: /usr/local/emhttp/plugins/nut-dw/scripts/start Jun 10 11:30:54 Tower rc.nut: Writing NUT configuration... Jun 10 11:30:56 Tower rc.nut: Updating permissions for NUT... Jun 10 11:30:56 Tower rc.nut: Adding UDEV lines to rc.6 for NUT... Jun 10 11:30:56 Tower rc.nut: Checking if the NUT Runtime Statistics Module should be enabled... Jun 10 11:30:56 Tower rc.nut: Disabling the NUT Runtime Statistics Module... Jun 10 11:30:57 Tower rc.nut: Network UPS Tools upsdrvctl - UPS driver controller 2.8.5 release Jun 10 11:30:57 Tower rc.nut: Network UPS Tools 2.8.5 release - Generic HID driver 0.71 Jun 10 11:30:57 Tower rc.nut: USB communication driver (libusb 1.0) 0.53 Jun 10 11:31:03 Tower rc.nut: Driver exited abnormally Jun 10 11:31:03 Tower kernel: usbhid-ups[736883]: segfault at 7ffc148c9000 ip 0000000000414f3d sp 00007ffc148c4f80 error 4 in usbhid-ups[14f3d,403000+27000] likely on CPU 0 (core 0, socket 0) Jun 10 11:31:03 Tower kernel: Code: 44 24 38 ff d0 85 c0 0f 8f 06 05 00 00 83 7d 00 01 7e 13 48 8d 35 2b 55 02 00 bf 02 00 00 00 31 c0 e8 07 db 00 00 49 83 c5 04 <45> 8b 65 00 8b 45 00 45 85 e4 78 f0 83 f8 01 0f 8e 3b ff ff ff 31 Jun 10 11:31:04 Tower kernel: usb 3-2: USB disconnect, device number 3 Jun 10 11:31:04 Tower kernel: usb 3-2: new full-speed USB device number 4 using xhci_hcd Jun 10 11:31:07 Tower kernel: hid-generic 0003:0463:FFFF.0005: hiddev96,hidraw2: USB HID v1.10 Device [EATON 5E] on usb-0000:2c:00.3-2/input0I never had errors with this UPS after it stops working the only way to fix it is to reboot Unraid, any idea how to debug this issue?

With the 7.0.0 release I can't add origins anymore also.

I am not sure if this is the same problem, upgrading from RC1 to RC2 removes the stored value but I can add it again (which as I understand doesn't work for you)

It is fixed in 7.0.0 betas

Can you show screenshots with the bugs? I have 7.0.0-beta.2 on 3 servers with 3 different themes, I only noticed a different in color near the dockers/VMs on dashboard but didn't really check if it is something can be fixed in the theme

Try to clear cache for this IP, I had something similar due to changes in the docker URLs

You need a larger UPS, I would also check the batteries, when they are at end of life the UPS will not hold it full load capacity. I don't see any other solution that will work as you can't control what is on and what is not. Power failure can happen during parity check which has all the disks running anyhow. Spinning the disks at shutdown is how all OSes works.

This plugin in not maintained anymore and I assume you are using Folder View which doesn't have this feature yet, you can ask on the plugin support thread:

I think it would be better to post it on a new thread.

I don't know if this is just coincidence, but after updating the unraid connect plugin my theme reverted to the normal black theme, moreover even the banner disappeared. Theme engine config files were not changed (comparing to a backup), removing and reinstalling it did nothing. What I noticed is that the display settings changed, I could manually update them (for example reselect the banner), but eventually just restored this file from a backup (config\plugins\dynamix\dynamix.cfg)

I don't see it either, however I am not the owner of that app, you better ask in the relevant support thread. This is about Portainer business edition

Thanks for updating back. I was too busy this week and planed to test it over the weekend.

I think this is related to Samba, it is definitely not the famous macvlan call trace

You should not get any macvlan errors on 6.12.4 as far as I understand, can you post a sample log trace here? or diagnostics?

vhost0 replaces br0. virbr0 is provided by libvirt and is used to created a NAT network for VMs. You should only update the interface in VMs (if it doesn't update automatically) to vhost0 if it was br0. There is no preferred default, it depends if you want the VM to run on your network (non-isolated) or run in a separated isolated network.

This is a great release which makes 6.12 so much better.

I don't really understand what you want to do, you should add dockers via unraid docker system, this is just for monitoring docker containers

You will need to contact Deconz, you can do it on their Github https://github.com/dresden-elektronik/deconz-rest-plugin or Discord: https://discord.gg/ycPBweQf and debug it with them. There is nothing wrong in this Docker according to the log. They will ask you to enable extra logging which can help understand the issue

There are no errors in the log, can you try to pair/add device?