NUT Question
-
Hi all,
I have an APC UPS connected to pfSense via USB and OpenMediaVault (OMV) setup to run as Netclient/Slave. OMV is set to shutdown after 15 mins on battery and this works just fine.
If the UPS is still on battery and pfSense has not shutdown yet, but OMV has been shutdown and power is restored OMV will not power back ON. I have to physically turn it back ON. I have the OMV BIOS set to turn ON after a power failure but as there was never no power on OMV so it fails to turn ON.
Can anything be done in the pfSense config to make OMV automatically turn ON in this situation?
The 2 ups.conf are below.
TIA
# This file is auto-generated by openmediavault (https://www.openmediavault.org) # WARNING: Do not edit this file, your changes will get lost. [apcups] driver = usbhid-ups port = auto desc = No Comment
user = root [apcups] ignorelb override.battery.charge.low = 40 [apcups] driver=usbhid-ups port=auto
-
If it's already off I don't think NUT can do anything. I don't believe it can power cycle the outlet for example. You might be able to do something with WoL. Does it have a BIOS option to power on on a schedule?
It might be better to prevent the OMV shutting down until it really has to. Though I imagine that might shorten the battery run time. And risk data etc.Steve
-
@gregeeh said in NUT Question:
I have an APC UPS connected to pfSense via USB and OpenMediaVault (OMV) setup to run as Netclient/Slave. OMV is set to shutdown after 15 mins on battery and this works just fine.
Is the OMV a NUT client of the pfSense NUT server?
When using NUT you do not want to clients to make independent decisions about when to shut down. This should always be initiated by the NUT server. Otherwise you can get into the situation of power being restored after the client decides to shut down but before the server decides to shut down. When this happens, the mains will never be cut, resulting in clients never rebooting. Which sounds like what you are experiencing.
-
@stephenw10 said in NUT Question:
It might be better to prevent the OMV shutting down until it really has to.
This sounds like the best solution. Rather then shutdown the OMV (NUT Client) in 15 minutes set it to low battery, like the NUT Server, then both will shutdown together and hopefully both come back on when power is restored.