search for: upscli_err_drvnotconn

...hat chatter. These messages originate in pollups() in clients/upsmon.c. It looks to me like pollups() sees the utype_t->status flag ST_CONNECTED set, yet the UPSCONN_t->fd is -1, which means there is no valid connection (upscli_sendline() in clients/upsclient.c sets UPSCONN_t->upserror = UPSCLI_ERR_DRVNOTCONN). If ST_CONNECTED was clear, the connection would be retried. It appears to me that because ST_CONNECTED is set, pollups() thinks it should have a good connection and is surprised to find out it does not. Thus, it always writes the "Driver not connected" message to /var/log/messages....