[Nut-upsuser] two MGE Ellipse 1500 ups via usb

Thomas Gutzler thomas.gutzler at gmail.com
Thu Nov 19 02:56:40 UTC 2009

Arjen de Korte wrote:
> Citeren Thomas Gutzler <thomas.gutzler at gmail.com>:
>> My master, which is also nfs server now reads:
>> MONITOR ups1 at localhost 1 monmaster blah master
>> MONITOR ups2 at localhost 1 monmaster blah master
> You'll want to increase the FINALDELAY here to give the NFS clients some
> time to save their data. Because all systems now have the same
> FINALDELAY value, they will all start shutting down at the same time
> (including the NFS server). Something like 60-120 seconds is usually
> plenty. Since the load on the UPS will rapidly decrease (with systems
> powering down), usually the UPS will be able to keep the output powered.

So when the batteries are critical, the master
- sends out FSD to all slaves and touches POWERDOWNFLAG
- waits for slaves to disconnect or max HOSTSYNC seconds to pass
- waits another FINALDELAY seconds
- executes its SHUTDOWNCMD, which
  - stops upsd, the drivers and the master upsmon (K50nut)
  - stops the nfs server (K80nfs-kernel-server)
  - runs upsdrvctl shutdown (S90halt) to shut down the UPSes

When a slave detects a FSD, it
- processes NOTIFY_SHUTDOWN (send an email in my case)
- waits for FINALDELAY seconds
- executes its SHUTDOWNCMD instantly, which
  - unmounts all nfs drives (S31umountnfs.sh)
  - causes upsmon to disconnect and stop (K50nut) and
  - shortly after powers off the system (as long as it takes to execute
the remaining few shutdown scripts)

If that's correct, isn't it better to set FINALDELAY to 0 and increase
HOSTSYNC for all slaves rather than increasing FINALDELAY for the
master? Shouldn't HOSTSYNC be the time the slowest slave needs to get to
the nut shutdown script after receiving a shutdown, which can be delayed
by up to POLLFREQALERT seconds?

> *Verify* that it works by running 'upsmon -c fsd' on the NFS server.

Yes, I was going to do that on a quiet night.


More information about the Nut-upsuser mailing list