UPS - NUT Error when trying to apply changes (Default settings)

MultiUser · 7. Juli 2023

I get a "500 Internal Server Error" when I try to apply a NUT/UPS config to enable UPS monitoring.

I have used the default settings and simply changed it to enabled.

Then when i try to apply the settings it gives me this error.

The log is huge BTW. This is just the clip from the first couple of lines:

Code

500 - INTERNAL SERVER ERROR
Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; export LANGUAGE=; omv-salt deploy run --no-color nut 2>&1' with exit code '1': debian:

I have used it in its default config with this UPS before. On OMV5 it worked just fine. Also on TrueNAS scale it worked just fine. I dont understand why I would be getting an error now.

I do have a raid rebuilding in the background. would that be an issue?

chente · 7. Juli 2023

Zitat von MultiUser

The log is huge BTW. This is just the clip from the first couple of lines:

With those two error lines it is not enough to see the problem, post something else. If it doesn't fit you can do it in two consecutive publications.

Zitat von MultiUser

I do have a raid rebuilding in the background. would that be an issue?

That shouldn't be a problem.

MultiUser · 7. Juli 2023

Zitat von chente

With those two error lines it is not enough to see the problem, post something else. If it doesn't fit you can do it in two consecutive publications.

ok here goes nothing.

Soma · 7. Juli 2023

It would be easier to paste it in a text file and attach it here, 😉

MultiUser · 7. Juli 2023

OK Thanks

Damn, should have done this from the beginning.

chente · 7. Juli 2023

Zitat von MultiUser

Code

----------
          ID: start_nut_driver_service
    Function: service.running
        Name: nut-driver
      Result: False
     Comment: Job for nut-driver.service failed because the control process exited with error code.
              See "systemctl status nut-driver.service" and "journalctl -xe" for details.
     Started: 12:48:40.010332
    Duration: 132.631 ms
     Changes:
----------

Alles anzeigen

Here it is. The next time you get a long error similar to this, it may be enough to look for the part where it says

Result: False

Now you need to run the two commands that that error is asking for and post them:

Code

systemctl status nut-driver.service
journalctl -xe

run them consecutively

MultiUser · 7. Juli 2023

Zitat von Soma

It would be easier to paste it in a text file and attach it here, 😉

HAHAHA, Im such a newb. lol .txt is the obvious choice here.

chente · 7. Juli 2023

Zitat von MultiUser

Damn, should have done this from the beginning.

Yeah, I didn't think it would be that long. nut files have a bible inside

MultiUser · 7. Juli 2023

Zitat von chente

Now you need to run the two commands that that error is asking for and post them:

do I do that from the cli in putty or similar?

chente · 7. Juli 2023

Zitat von MultiUser

do I do that from the cli in putty or similar?

Yes

MultiUser · 7. Juli 2023

Here are the results.

MultiUser · 7. Juli 2023

I should mention that the cable is unplugged from the UPS at this point. Not sure if that matters since it wont even enable itself. I have tried with and without the cable attached to the UPS.

chente · 7. Juli 2023

Zitat

Failed to start Network UPS Tools - power device driver controller.

Did you check the driver that works for your UPS?

Did you read this? [How-to] Use the openmediavault-nut plugin

MultiUser · 7. Juli 2023

i have used this plugin before with zero issues on two different nas OSes.... including OMV5

Im not sure what else to do or where to go from here...

chente · 7. Juli 2023

Zitat von MultiUser

Im not sure what else to do or where to go from here...

Zitat von chente

Before using this plug-in you should check the compatibility of your UPS with NUT. You can check your model here

You have to make sure which is the driver that works with your UPS model. What is the manufacturer and model?

Network UPS Tools - Hardware compatibility list

lukas.horor · 1. November 2023

I had similar problem yesterday when trying to Apply changes after upgrade to the new OMV.

My UPS works well (nutdrv_qx, ID 0665:5161) before and after upgrade, communication still works. But there is an error in journal the nut-driver.service failed.

It because of this service is missing!

The service has different name based on UPS identifier in OMV settings: nut-driver@my-ups.service

And there is a nut-driver.target (after typo "systemctl status nut-" and pressed tab in shell).

Zitat von https://wiki.archlinux.org/title/Network_UPS_Tools#Driver_configuration

At this point you should be able to start/enable nut-driver-enumerator.service which will automatically create nut-driver@<ups name> systemd service instance and start it.)

So, I searched in omv code and found "nut-driver" in /srv/salt/omv/deploy/nut/default.sls and changed it to "nut-driver@my-ups". And then Apply changes in OMV finally works! But it is temporary solution.

chente · 1. November 2023

Zitat von lukas.horor

So, I searched in omv code and found "nut-driver" in /srv/salt/omv/deploy/nut/default.sls and changed it to "nut-driver@my-ups". And then Apply changes in OMV finally works!

Thanks for posting. I think this may interest votdev

votdev · 1. November 2023

Zitat von lukas.horor

I had similar problem yesterday when trying to Apply changes after upgrade to the new OMV.
My UPS works well (nutdrv_qx, ID 0665:5161) before and after upgrade, communication still works. But there is an error in journal the nut-driver.service failed.

It because of this service is missing!
The service has different name based on UPS identifier in OMV settings: nut-driver@my-ups.service
And there is a nut-driver.target (after typo "systemctl status nut-" and pressed tab in shell).
So, I searched in omv code and found "nut-driver" in /srv/salt/omv/deploy/nut/default.sls and changed it to "nut-driver@my-ups". And then Apply changes in OMV finally works! But it is temporary solution.

Alles anzeigen

This only applies to the nut package that is shipped with Debian 12. In Debian 11, which OMV6 is strictly tied to, there is only one unit file called nut-driver.service.

It looks like you have installed a backported package which is not supported by OMV because of exactly the problem you are facing now; backports introduce incompatibilities.

But thx for the hint, i've fixed the issue in the upcoming OMV7.

UPS - NUT Error when trying to apply changes (Default settings)

Jetzt mitmachen!

Tags