Vladimir Stavrinov wrote:
> I have simple configuration: one master with one UPS connected
> via serial port, and five slaves. When battery is low and master
> set FSD on UPS, then after few seconds it get from all slaves:
> "disconnected (read failure)" and start shutdown and power off
> before slave shutdown complete, that need about 90 seconds.
See 'man 5 upsmon.conf'. This will explain in detail what goes on if the
master decides the UPS has become critical.
> I
> don't understand, why slaves disconnected before shutdown go
> near it's finish.
When the slaves get the command to shutdown, they close the connection
to the master. The latter will wait for the slaves to disconnect or
until HOSTSYNC seconds have elapsed before starting the FINALDELAY
(whichever comes first). After that, init takes over. If your slaves
take more time than FINALDELAY plus the time it takes init to shutdown
the master, you may need to increase FINALDELAY. But watch the pitfall,
if the battery of the UPS is too low, the UPS may not wait for the
master to shut it down.
> I have checked this: it is not init or init
> script that kill upsmon, but upsmon itself close connection
> right after get "force shutdown" from master.
Indeed. This is by design. If you want to know why, I suggest to start
reading the documents in the docs/ directory.
Best regards, Arjen