Ong, Kevin
2018-Sep-03 23:49 UTC
[Nut-upsuser] NUT messes up UPS after mains power is restored
Hi Charles, Ok. I'm testing NUT now with only pfsense running as the master and no slaves. I'm noticing a very strange behavior that totally doesn't make sense to me. So here's what I did (in chronological order): 1. Set override.battery.charge.warning to 55 and override.battery.charge.low to 50. 2. I started with a full charge battery and unplugged the UPS from the mains. 3. The UPS status in the pfsense picked up the change and says Online, discharging. 4. As soon as the battery charge hits 50, the state changed to FSD which is what is expected. So far so good. 5. Since no slaves are present, the pfsense box turned off itself pretty quick. 6. The UPS waited for a few more seconds before it finally cut off the load power to the rest of its ports. All good. 7. Now I plug the mains back into the UPS. As soon as I do this, the UPS turns on BUT stays at battery mode (so discharging). 8. It supplies power back to all ports and pfsense and the other devices started booting. 9. Then the UPS itself detects that the battery charge is still below 50% (of course, because it needs time to charge and it is even at a discharging state now) and then a few seconds later the unit turns off again. It seems that the killpower command given to it by the pfsense is still being enforced even though the mains is already connected and providing power. 10. Then it turns on by itself again. And this vicious cycle continues over and over until I disconnected the USB serial connection in the back of the UPS. What have I done wrong here? Why doesn't the UPS detect that the mains power is already back when the USB serial connection is plugged in. It seems to me that the command given by the pfsense NUT package is messing the behavior of the UPS. Here's my post on the pfsense forum about it: https://forum.netgate.com/topic/102959/nut-package/389 Thank you. Regards, Kevin This email may contain material that is confidential, and proprietary to Ingram Micro, for the sole use of the intended recipient. Any review, reliance or distribution by others or forwarding without express permission is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies. [Ingram_2818e5de] -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://alioth-lists.debian.net/pipermail/nut-upsuser/attachments/20180903/688a9399/attachment.html>
Ong, Kevin
2018-Sep-04 16:36 UTC
[Nut-upsuser] NUT messes up UPS after mains power is restored
UPDATE: I think I know what I did wrong. In step 7, I plugged the mains too early causing a power race condition as described by point #51 here<https://networkupstools.org/docs/FAQ.html> . I thought that when APC BR1500GI's display went black (even with the fans still running) it is already in a shutdown state. This was not the case, it waited for a few more seconds until it totally went silent. At that time, I plugged the mains back and everything was working as expected :) Thank you. Regards, Kevin Mychal M. Ong Sr Infrastructure Engineer, Microsoft Technology Services - Messaging Global Infrastructure Operations Ingram Micro Inc. 4F Three World Square, 22 Upper McKinley Hill, Fort Bonifacio Taguig City, Philippines 1634 Direct +1-716-633-3600 ext. 33996 Mobile +63-917-511-0251 *: kevin.ong at ingrammicro.com<mailto:kevin.ong at ingrammicro.com> [Ingram_Micro_Logo_ Small_Image] From: Ong, Kevin <Kevin.Ong at ingrammicro.com> Sent: Tuesday, September 4, 2018 7:49 AM To: nut-upsuser at alioth-lists.debian.net Cc: kevindd992002 at yahoo.com; Denny Page <denny at cococafe.com> Subject: NUT messes up UPS after mains power is restored Hi Charles, Ok. I'm testing NUT now with only pfsense running as the master and no slaves. I'm noticing a very strange behavior that totally doesn't make sense to me. So here's what I did (in chronological order): 1. Set override.battery.charge.warning to 55 and override.battery.charge.low to 50. 2. I started with a full charge battery and unplugged the UPS from the mains. 3. The UPS status in the pfsense picked up the change and says Online, discharging. 4. As soon as the battery charge hits 50, the state changed to FSD which is what is expected. So far so good. 5. Since no slaves are present, the pfsense box turned off itself pretty quick. 6. The UPS waited for a few more seconds before it finally cut off the load power to the rest of its ports. All good. 7. Now I plug the mains back into the UPS. As soon as I do this, the UPS turns on BUT stays at battery mode (so discharging). 8. It supplies power back to all ports and pfsense and the other devices started booting. 9. Then the UPS itself detects that the battery charge is still below 50% (of course, because it needs time to charge and it is even at a discharging state now) and then a few seconds later the unit turns off again. It seems that the killpower command given to it by the pfsense is still being enforced even though the mains is already connected and providing power. 10. Then it turns on by itself again. And this vicious cycle continues over and over until I disconnected the USB serial connection in the back of the UPS. What have I done wrong here? Why doesn't the UPS detect that the mains power is already back when the USB serial connection is plugged in. It seems to me that the command given by the pfsense NUT package is messing the behavior of the UPS. Here's my post on the pfsense forum about it: https://forum.netgate.com/topic/102959/nut-package/389 Thank you. Regards, Kevin This email may contain material that is confidential, and proprietary to Ingram Micro, for the sole use of the intended recipient. Any review, reliance or distribution by others or forwarding without express permission is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies. [Ingram_2818e5de] -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://alioth-lists.debian.net/pipermail/nut-upsuser/attachments/20180904/76f93a5f/attachment-0001.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 7752 bytes Desc: image001.png URL: <http://alioth-lists.debian.net/pipermail/nut-upsuser/attachments/20180904/76f93a5f/attachment-0001.png>
Stuart Gathman
2018-Sep-04 17:12 UTC
[Nut-upsuser] NUT messes up UPS after mains power is restored
On 09/04/2018 12:36 PM, Ong, Kevin wrote:> > I think I know what I did wrong. In step 7, I plugged the mains too > early causing a power race condition as described by point #51 here > <https://networkupstools.org/docs/FAQ.html> . I thought that when APC > BR1500GI's display went black (even with the fans still running) it is > already in a shutdown state. This was not the case, it waited for a > few more seconds until it totally went silent. At that time, I plugged > the mains back and everything was working as expected :) >Unfortunately, electric utilities are not always so polite. They have a habit of restoring power at the most inopportune times. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://alioth-lists.debian.net/pipermail/nut-upsuser/attachments/20180904/25cebb1a/attachment.html>