> Does the problem occur frequently? The more details, the better. > > from there, 3 possibilities (need more details to audit): > - if the problem occurred only once, then you've seen a battery test, > - else you have some electrical problems upstream, > - else the UPS has some internal problem. > > A workaround would be to increase upsd.conf -> MAXAGE (ie to 20 - 25) > and upsmon.conf -> DEADTIME (to 20 - 25 too)
I doubt this will work. The driver will broadcast any changes it sees in the status from the UPS, regardless of the value of MAXAGE. The latter is only used by the server to determine when to PING the driver, if the server has heard nothing from the driver lately. But it can't be used to mask out unwanted messages from the driver, this has to be done in the driver. Changing MAXAGE and DEADTIME should no longer be necessary, since they only determine the timeouts for communication between driver/server and server/client respectively. Increasing the value of DEADTIME used to be a solution if you saw lots of packet loss between server and client, but since we use TCP exclusively nowadays, this is not really relevant anymore. Best regards, Arjen -- Eindhoven - The Netherlands Key fingerprint - 66 4E 03 2C 9D B5 CB 9B 7A FE 7E C1 EE 88 BC 57 _______________________________________________ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
