[Nut-upsuser] NUT 2.0.4-4 - Debian stable - /etc/killpower not created?

Arjen de Korte nut+users at de-korte.org
Wed Apr 30 09:03:39 UTC 2008

Please keep the mailinglist posted. I won't reply to messages sent to me 
in private, unless a consulting fee is involved.
>>> How can I make sure that a machine was "ready" when the power was 
>>> cut? I
>>> have been getting messages about corrupt databases on return from a
>>> power out.
>> The latter could happen, if the shutdown sequence of a slave takes 
>> longer
>> than that of the master. In that case, the slave may not have finished
>> shutting down at the time the power is cut.
> This happens on the master.
In that case either you're sending the shutdown command to the UPS at 
the wrong time (it should be near the bottom of the halt script, just 
before the system power-off command) or your database doesn't respond to 
a SIGTERM signal in a timely matter (it doesn't have enough time to 
proceed and it receives a SIGKILL before it has finished).
> In my halt script, it looks for /etc/killpower. It should log if this 
> file exists or not. However, I never see anything like this in my 
> logs.  What could the reason be?
It can't. At the time you're looking for this file, the syslogd won't be 
running anymore, so you can't write to the logs anymore. This is normal.

Best regards, Arjen

More information about the Nut-upsuser mailing list