[Nut-upsuser] Understanding the shutdown sequence of steps for a master and slave configuration

Paul Freeman paul.freeman at emlair.com.au
Wed Apr 25 21:35:30 UTC 2012


Gabriele,
Thank you for your reply.  I will try your solution.

Regards

Paul

> -----Original Message-----
> From: nut-upsuser-
> bounces+paul.freeman=emlair.com.au at lists.alioth.debian.org [mailto:nut-
> upsuser-bounces+paul.freeman=emlair.com.au at lists.alioth.debian.org] On
> Behalf Of Gabriele
> Sent: Friday, 20 April 2012 5:55 PM
> To: nut-upsuser at lists.alioth.debian.org
> Subject: Re: [Nut-upsuser] Understanding the shutdown sequence of steps
> for a master and slave configuration
> 
> Hy,
> I have the same situation.
> In brief: the trick is to put FINALDELAY 600 on the master node.
> 
> My shutdown sequence is:
> 
> * power outage occurs
> * master not waits 300 seconds (timer of upssched)
> * after 300 seconds, the master node sends shutdown signal to all slaves
> * masternode waits 600 seconds (FINALDELAY) doing nothing
> * all slaves initiates shutdown. I calculated that I have enough time.
> * when the 600 seconds FINALDELAY expires on master, it starts shutdown
> * My UPS is configured to wait 340 seconds before cutting power
> * after 340 seconds, power is disconnected
> * when power returns, my ups will wait for 90 seconds AND at le
> ast 15% of battery power to restore power
> 
> My 2c,
> --
> Gabriele
> 
> _______________________________________________
> Nut-upsuser mailing list
> Nut-upsuser at lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser



More information about the Nut-upsuser mailing list