When the UPS starts to run on Battery, upsmon notifies upssched, and
upssched runs an "onbatt script", which sends out an alert every 15
seconds via wall.
When the UPS is put back on line, upsmon acknowledges this change (via
WALL). However, upssched does not get notified properly, so the onbatt
script continues to send alerts. About 45 seconds later, upssched
acknowledges the UPS change, and disengages the onbatt script.
I checked syslog, and I found these upssched error messages during that
45 second delay:
Jul 21 10:23:55 simnet-alic upsmon[3917]: UPS APC@localhost on battery
Jul 21 10:23:55 simnet-alic upssched[3925]: Timer daemon started
Jul 21 10:23:55 simnet-alic upssched[3925]: New timer: onbatt (5
seconds)
Jul 21 10:24:00 simnet-alic upssched[3925]: Event: onbatt
Jul 21 10:24:50 simnet-alic upsmon[3917]: UPS APC@localhost on line
power
Jul 21 10:24:52 simnet-alic upssched[3948]: read confirmation failed,
trying again
Jul 21 10:25:22 simnet-alic last message repeated 15 times
Jul 21 10:25:22 simnet-alic upssched[3948]: Executing command: onpower
Does anyone know why I'm running into this problem?
-Rob
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20050721/7d4f9348/attachment.htm
