killpower

[Grimeton]

Hi,

it's not exactly a bug, more a mixture of feature request and bug.

I have the following setup:

FreeNAS as storage backend for iSCSI and other stuff, an iMac as the iSCSI frontend, a switch and a firewall all connected to the ups.

I run NUT on all of the devices, to monitor the ups which is directly connected to the FreeNAS box.

If a power failure occurs, everything is working as expected, but the UPS is not powered down after FreeNAS shut itself down. FreeNAS needs to honor the existence of the killpower file in /etc/killpower or /var/etc/killpower and then tell the UPS to shut down. In the NUT config there is no config option set that would create the file.

It's like the explanation of the "POWERDOWNFLAG" of NUT says. The systems become stuck in the power down state even if the power comes back.

Code:

POWERDOWNFLAG filename
upsmon creates this file when running in master mode when the UPS needs to be powered off. You should check for this file in your shutdown scripts and call upsdrvctl shutdown if it exists.
This is done to forcibly reset the slaves, so they don’t get stuck at the "halted" stage even if the power returns during the shutdown process. This usually does not work well on contact-closure UPSes that use the genericups driver.

So what is missing is the "POWERDOWNFLAG" in the config file (there is no way to add extra options to upsmon.conf) and an entry in the shutdown scripts that call upsdrvctl to power down the UPS in the end.

KR,

Grimeton

 

[catuso]

Please can any budy help with this NUT command?

POWERDOWNFLAG /etc/killpower


I really cant make this work. Help!

 

[Grimeton]

Yeah still a problem... Funny that the USV host can't power down itself after all other clients have successfully powered down...

 

[dlavigne]

Please create a ticket of type enhancement at support.freenas.org to add this feature to the UPS screen.