[Nut-upsuser] Spurious messages on start

Pedro Côrte-Real pedro at pedrocr.net
Tue Nov 14 15:56:49 CET 2006

On 11/14/06, Arjen de Korte <nut+users at de-korte.org> wrote:
> Did you also try adding a 5 second sleep between starting upsdrvctl and
> upsd? I think the problem lies there, upsd is trying to connect to the
> driver that is still in the process of starting up. Since upsd will
> periodically retry connecting to the driver if it failed, it will try to
> reconnect after 15 seconds (if memory serves). A 20 second delay for
> starting upsmon would blank reporting this problem.

Yes, this was what I tried first and it made no difference. upsdrvctl
seems to wait until the driver is fully initialized and only then goes
into the background.

> > I added a 30 second sleep to my init file just to be on the safe side.
> > Seems to work fine now but it seems like a bug in the way upsd and
> > upsmon interact on startup.
> Note that upon startup upsd will poll all configured UPSes to prevent
> upsmon reporting stale data. However, if it can't connect to a driver
> (because the driver has not finished starting up), this mechanism doesn't
> work and it will rightfully tell you so that it can't connect to the
> driver.

As far as I can tell the driver has started up as it reports the UPS model.


More information about the Nut-upsuser mailing list