<div dir="auto">Hello. Battery, battery, battery. I am only thinking at worn batteries. I recently had the same symptoms with an hp/eaton g3 1500va. One of the 3 batteries was reading a healthy 12.8v, but when put under load it would quickly drain. I would measure each battery and test them under load, like with a car headlight bulb switched on both fillaments. </div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, 23 Apr 2020, 16:54 Marc Franquesa, <<a href="mailto:marc.franquesa@gmail.com">marc.franquesa@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hi, recently I observed that during a power outage, my NUT setup doesn't shutdown properly. Indeed it never reaches the LowBattery state to notify and initiate shutdown on clients. Reviewing my setup and logs I think I'm facing multiple problems and I'm unable to point to real root cause.<br><br>First, let me focus on my scenario and current setup:<br><br>In normal status (ONLINE, fully charged) my UPS runtime is about 20minutes, this is some of the relevant info:<br><br>Charge 100%<br>Charge Low 20%<br>Runtime 20m37s<br>Type PbAc<br>Manufacturer EATON<br>Model Ellipse<br>ECO 1200<br>Serial 000000000<br>Power 25VA<br>Frequency Nominal 50Hz<br>Voltage 230.0V<br>Voltage Nominal 230V<br>Delay Shutdown 25s<br>Delay Start 40s<br>Firmware 02<br>Load 23%<br>Power Nominal 1200VA<br>Status OL<br><br>During a power outage it used to last for about 15 minutes and then initiate the shutdown. however reviewing the logs of my systems:<br><br>Apr 19 12:04:23 - OnBattery<br>Apr 19 12:10:21 - Power from UPS cut, all systems got suddenly powered off (no graceful shutdown)<br>Apr 19 12:16:46 - Power restored, UPS feeds power again to the systems and they boot up.<br><br>So this indicated the UPS only lasted about 6 minutes.<br><br>Also I have 2 UPS:<br>- UPSdevice, which is the real UPS<br>- HeartBeat : virtual dummy device to monitor proper NUT communication (see <a href="http://rogerprice.org/NUT/NUT.html#HEARTBEAT" target="_blank" rel="noreferrer">http://rogerprice.org/NUT/NUT.html#HEARTBEAT</a>).<br><br>Looking at the logs when the event starts:<br><br>Apr 19 12:04:23 laney upsmon[756]: UPS <a href="mailto:UPSdevice@power.srv.l3jane.net" target="_blank" rel="noreferrer">UPSdevice@power.srv.l3jane.net</a>: On battery.<br>Apr 19 12:04:23 laney upssched[797]: New timer: onbattwarn (30 seconds)<br>Apr 19 12:04:53 laney upssched[797]: Event: onbattwarn<br>Apr 19 12:08:24 laney upsmon[756]: UPS <a href="mailto:HeartBeat@power.srv.l3jane.net" target="_blank" rel="noreferrer">HeartBeat@power.srv.l3jane.net</a>: On battery.<br>Apr 19 12:08:24 laney upssched[797]: Cancelling timer: heartbeat-failure<br><br>UPSdevice uses timer "onbattwarn", while HeartBeat is using a separated timer "heartbeat-failure". So I supose that when heartbeat cancels the 'heartbeat-failure' the onbattwarn timer is still running.<br><br>The second concern is quickly spotted:<br><br>Apr 19 12:09:19 laney usbhid-ups[703]: libusb_get_interrupt: error submitting URB: No such device<br>Apr 19 12:09:24 laney upsd[753]: Data for UPS [UPSdevice] is stale - check driver<br>Apr 19 12:09:26 laney upsd[753]: UPS [UPSdevice] data is no longer stale<br><br>Seems that during the 'onbattwarn' event, NUT lost communcaiton with the UPS for about 6 secs? this is really quick to trigger any 'COMM_BAD' evebt so no notifcation regarding this is sent, just the logs.<br><br>However as stated above on the logs, just 1 min later (12:10:21) power is totally lost even from UPS, no trace of LowBattery events, comm errors or so. A part from a email message that upssched sent me (although no logs of the event appears), this email reports:<br><br>Power ups UPSdevice battery-low notification<br>UPS: <a href="mailto:UPSdevice@power.srv.l3jane.net" target="_blank" rel="noreferrer">UPSdevice@power.srv.l3jane.net</a><br>Notice type: LOWBATT<br>Message: battery-low<br>Sun, 19 Apr 2020 12:10:27 +0200<br><br>Charge 73%<br>Charge Low 20%<br>Runtime 15m52s<br>Type PbAc<br>Manufacturer EATON<br>Model Ellipse<br>ECO 1200<br>Serial 000000000<br>Type Ups<br>Power 25VA<br>Frequency Nominal 50Hz<br>Voltage 230.0V<br>Voltage Nominal 230V<br>Delay Shutdown 20s<br>Delay Start 30s<br>Firmware 02<br>Load 21%<br>Power Nominal 1200VA<br>Status FSD<br>ALARM OB LB<br><br>So, indeed was in LowBattery and FSD shutdown, however note that the current charge was 73% >> 20% low battery, so why it set LB when there were enough battery to run? Is this a comm problem, device issue, driver ?<br><br>So mainly my concerns questions are:<br>A) Can upsched introduce some race-conditions making a timer cancel cancel other timers not related ?<br>B) May my UPS be faulting or just some USB driver issue?<br><br>Any other hint, information or idea is welcomed.<br><br>Regards</div>
_______________________________________________<br>
Nut-upsuser mailing list<br>
<a href="mailto:Nut-upsuser@alioth-lists.debian.net" target="_blank" rel="noreferrer">Nut-upsuser@alioth-lists.debian.net</a><br>
<a href="https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser" rel="noreferrer noreferrer" target="_blank">https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser</a></blockquote></div>