On 2019-12-16 05:34, Roger Price wrote:> On Sun, 15 Dec 2019, Phil Stracchino wrote: > >> I switched a while back to a Cyberpower PR3000LCDRTXL2U UPS with an >> external battery chassis. We've lost power twice since I installed it, >> and both times, the UPS has killed power to everything while still >> indicating 80% capacity before NUT has even initiated shutdown on anything. >> >> I don't think I ever got all the way through NUT configuration on it. >> What am I most likely doing wrong, or what might I have missed, or what >> setting am I misunderstanding, that the UPS itself is shutting off the >> power so absurdly early? > > It would be interesting to see your NUT configuration. If it would help you > there is a shell script at http://rogerprice.org/NUT/nut-report which will > prepare a configuration report. (It removes passwords.)Thanks! Report attached. One observation: "WARNING: I am unable to call script nut-journal to read the NUT activity records in the systemd journal. Either the nut-journal script is not available or you do not have access to the journal for system commands such as those of NUT. Ask your system administrator to add your account to the systemd-journal group. When this is done, log out and then log in and try again." .... OR, you're not running systemd. (Out, out, vile daemon. You shall not pass.)> Meanwhile, how old is your battery? Very old batteries can produce exactly the > effect you describe: crashing rapidly while still indicating high charge.It's a brand new UPS installed earlier this year. -- Phil Stracchino Babylon Communications phils at caerllewys.net phil at co.ordinate.org Landline: +1.603.293.8485 Mobile: +1.603.998.6958 -------------- next part -------------- A non-text attachment was scrubbed... Name: NUT.report.gz Type: application/x-gzip-compressed Size: 1158 bytes Desc: not available URL: <http://alioth-lists.debian.net/pipermail/nut-upsuser/attachments/20191216/3ff68add/attachment.bin>
On December 16, 2019 9:14:01 PM GMT+02:00, Phil Stracchino <phils at caerllewys.net> wrote:>On 2019-12-16 05:34, Roger Price wrote: >> On Sun, 15 Dec 2019, Phil Stracchino wrote: >> >>> I switched a while back to a Cyberpower PR3000LCDRTXL2U UPS with an >>> external battery chassis. We've lost power twice since I installed >it, >>> and both times, the UPS has killed power to everything while still >>> indicating 80% capacity before NUT has even initiated shutdown on >anything. >>> >>> I don't think I ever got all the way through NUT configuration on >it. >>> What am I most likely doing wrong, or what might I have missed, or >what >>> setting am I misunderstanding, that the UPS itself is shutting off >the >>> power so absurdly early? >> >> It would be interesting to see your NUT configuration. If it would >help you >> there is a shell script at http://rogerprice.org/NUT/nut-report which >will >> prepare a configuration report. (It removes passwords.) > >Thanks! Report attached. > >One observation: > >"WARNING: I am unable to call script nut-journal to >read the NUT activity records in the systemd journal. >Either the nut-journal script is not available >or you do not have access to the journal >for system commands such as those of NUT. >Ask your system administrator to add your >account to the systemd-journal group. >When this is done, log out and then log in >and try again." > > >.... OR, you're not running systemd. (Out, out, vile daemon. You >shall >not pass.) > > >> Meanwhile, how old is your battery? Very old batteries can produce >exactly the >> effect you describe: crashing rapidly while still indicating high >charge. > > >It's a brand new UPS installed earlier this year.There are documented cases of UPSes that were stored so long on a shelf prior to being sold that the batteries were completely dry at the time of sale. If your UPS is not sealed, I'd open it and test the batteries separately. Or at least do a full self check.
On Mon, 16 Dec 2019, Phil Stracchino wrote:> One observation: > > "WARNING: I am unable to call script nut-journal to > read the NUT activity records in the systemd journal. > > .... OR, you're not running systemd. (Out, out, vile daemon. You shall not > pass.)I definitely need to check that the vile daemon is present and running. In upsmon.conf there are no NOTIFYFLAG declarations, especially for events ONBATT and LOWBATT. When ONBATT and LOWBATT occur nothing will happen. There are no NOTIFYMSG declarations and in particular no messages for the ONBATT and LOWBATT events. If you add NOTIFYFLAG and NOTIFYMSG declarations to upsmon.conf, you should get a better idea of what is happening. Additionally, in upsmon.conf there is no NOTIFYCMD declaration which would call upssched.conf. So the only system shutdown criterion will be on LB status. Roger
On 2019-12-17 06:18, Roger Price wrote:> > I definitely need to check that the vile daemon is present and running. > > In upsmon.conf there are no NOTIFYFLAG declarations, especially for events > ONBATT and LOWBATT. When ONBATT and LOWBATT occur nothing will happen. There > are no NOTIFYMSG declarations and in particular no messages for the ONBATT and > LOWBATT events. > > If you add NOTIFYFLAG and NOTIFYMSG declarations to upsmon.conf, you should get > a better idea of what is happening. > > Additionally, in upsmon.conf there is no NOTIFYCMD declaration which would call > upssched.conf. So the only system shutdown criterion will be on LB status.OK, so I definitely missed configuration steps and, apparently, forgot that I'd never finished. I will have to look over everything again. Also, looking at my own monitoring graphs of what happened around the outage, it looks as though runtime on my UPS is strangely non-linear with respect to load — i.e, dropping to my critical-systems-only load which is about 40% of my normal total load (which is to say, slightly less than 20% of UPS capacity vs. about 45%) does not appear to have extended runtime nearly as much as expected. It more than doubled the UPS's PROJECTED runtime according to the UPS, but not the *actual* runtime. Also, it looks from my graphs as though the UPS was claiming 10% capacity when it shut off, but 80% when the power came back on. There are some very odd things going on here that I need to get to the bottom of. -- Phil Stracchino Babylon Communications phils at caerllewys.net phil at co.ordinate.org Landline: +1.603.293.8485 Mobile: +1.603.998.6958