Jon Bendtsen
2017-Apr-03 15:41 UTC
[Nut-upsuser] battery not installed, but battery still 100% and NUT 2.7.2-4 does not catch this and report a error
On 03/04/17 17.24, Roger Price wrote:> On Mon, 3 Apr 2017, Jon Bendtsen wrote: > >> On 03/04/17 17.10, Roger Price wrote: >>> On Mon, 3 Apr 2017, Jon Bendtsen wrote: >>> >>>> Power seem to be lost immediately. >>>> But my APC Smart-UPS 1500 always reported everything OK. >>>> battery.charge : 100 >>> ... >>>> battery.mfr.date : 2005/08/26 >>> >>> Hi, Could you confirm that the battery is nearly 12 years old? Roger >> >> yeah, it most likely is that old > > That's probably the cause of the immediate power loss. A new battery should fix > the problem. Rogeryeah a new battery will most likely make it go away. However, that is not why I wrote the email. I wrote the email because I want NUT to tell me much more clearly that something is wrong, and NUT currently does not do that. JonB
Tim Dawson
2017-Apr-03 16:05 UTC
[Nut-upsuser] battery not installed, but battery still 100% and NUT 2.7.2-4 does not catch this and report a error
NUT can only report what the UPS tells it. IE, if no battery/load test is runs on the UPS, it has no way to know the battery croaked . . . it just sees normal voltage, and says "100% charge" . . . . - Tim On April 3, 2017 10:41:56 AM CDT, Jon Bendtsen <jon.bendtsen at jonix.dk> wrote:>On 03/04/17 17.24, Roger Price wrote: >> On Mon, 3 Apr 2017, Jon Bendtsen wrote: >> >>> On 03/04/17 17.10, Roger Price wrote: >>>> On Mon, 3 Apr 2017, Jon Bendtsen wrote: >>>> >>>>> Power seem to be lost immediately. >>>>> But my APC Smart-UPS 1500 always reported everything OK. >>>>> battery.charge : 100 >>>> ... >>>>> battery.mfr.date : 2005/08/26 >>>> >>>> Hi, Could you confirm that the battery is nearly 12 years old? >Roger >>> >>> yeah, it most likely is that old >> >> That's probably the cause of the immediate power loss. A new battery >should fix >> the problem. Roger > >yeah a new battery will most likely make it go away. However, that is >not why I >wrote the email. I wrote the email because I want NUT to tell me much >more >clearly that something is wrong, and NUT currently does not do that. > > > >JonB > > >_______________________________________________ >Nut-upsuser mailing list >Nut-upsuser at lists.alioth.debian.org >http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser-- Sent from my Android device with K-9 Mail. Please excuse my brevity. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20170403/95c869ca/attachment.html>
Jon Bendtsen
2017-Apr-03 16:29 UTC
[Nut-upsuser] battery not installed, but battery still 100% and NUT 2.7.2-4 does not catch this and report a error
On 03/04/17 18.05, Tim Dawson wrote:> NUT can only report what the UPS tells it. IE, if no battery/load test is runs > on the UPS, it has no way to know the battery croaked . . . it just sees normal > voltage, and says "100% charge" . . . .yeah, but the UPS does also tell NUT: root at dkfitlet:/etc/nut# upslog -s apc1500 -l - Network UPS Tools upslog 2.7.2 logging status of apc1500 to - (30s intervals) Init SSL without certificate database 20170403 154055 100 230.4 21.4 [ALARM OL] NA NA 20170403 154125 100 230.4 20.8 [ALARM OL] NA NA 20170403 154155 100 230.4 21.4 [ALARM OL] NA NA root at dkfitlet:/etc/nut# upsmon -DDD Network UPS Tools upsmon 2.7.2 kill: No such process 0.000000 UPS: apc1500 at localhost (monitoring only) 0.000214 UPS: Smart-UPS_3000 at localhost (monitoring only) 0.000328 UPS: R3000XR at localhost (monitoring only) 0.001278 Using power down flag file /etc/killpower 0.002126 debug level is '3' 0.005831 Init SSL without certificate database 0.011754 Trying to connect to UPS [apc1500 at localhost] 0.013150 Can not connect to localhost in SSL, continue uncrypted 0.013909 Logged into UPS apc1500 at localhost 0.014384 pollups: apc1500 at localhost 0.014501 get_var: apc1500 at localhost / status 0.014889 parse_status: [ALARM OL] 0.015012 parsing: [ALARM] 0.015100 parsing: [OL] 0.015181 ups_on_line: apc1500 at localhost (first time) however, I have to go into debug level 2 to see that. root at dkfitlet:/home/jonbendtsen# upsmon -DD Network UPS Tools upsmon 2.7.2 kill: No such process 0.000000 UPS: apc1500 at localhost (monitoring only) 0.000166 UPS: Smart-UPS_3000 at localhost (monitoring only) 0.000257 UPS: R3000XR at localhost (monitoring only) 0.000884 Using power down flag file /etc/killpower 0.001629 debug level is '2' 0.005681 Init SSL without certificate database 0.011154 Trying to connect to UPS [apc1500 at localhost] 0.013431 Logged into UPS apc1500 at localhost 0.013955 pollups: apc1500 at localhost 0.014318 parse_status: [ALARM OL] level 1 is not enough to see the ALARM in the output
Gene Heskett
2017-Apr-03 17:33 UTC
[Nut-upsuser] battery not installed, but battery still 100% and NUT 2.7.2-4 does not catch this and report a error
On Monday 03 April 2017 11:41:56 Jon Bendtsen wrote:> On 03/04/17 17.24, Roger Price wrote: > > On Mon, 3 Apr 2017, Jon Bendtsen wrote: > >> On 03/04/17 17.10, Roger Price wrote: > >>> On Mon, 3 Apr 2017, Jon Bendtsen wrote: > >>>> Power seem to be lost immediately. > >>>> But my APC Smart-UPS 1500 always reported everything OK. > >>>> battery.charge : 100 > >>> > >>> ... > >>> > >>>> battery.mfr.date : 2005/08/26 > >>> > >>> Hi, Could you confirm that the battery is nearly 12 years old? > >>> Roger > >> > >> yeah, it most likely is that old > > > > That's probably the cause of the immediate power loss. A new > > battery should fix the problem. Roger > > yeah a new battery will most likely make it go away. However, that is > not why I wrote the email. I wrote the email because I want NUT to > tell me much more clearly that something is wrong, and NUT currently > does not do that. > > > > JonB >Nut, IIRC, can do a periodic battery test by putting it offline, using the battery, for a predetermined length of time, weekly, monthly etc, and IIRC recording the battery voltage just as it switches back to line power. The comparative voltage level at the switchback point is a pretty good indication of the battery condition, and I think that could be used to trigger an "I need a new battery" email message well ahead of an unexpected total fail shutdown. I have a 20kw nat gas fired standby generator thats typically live in 5 seconds since the Mrs. has COPD, so I have never set that up here, but I believe you can find that in the Nut docs. Unless its been elided in the last 15 years. :( Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) Genes Web page <http://geneslinuxbox.net:6309/gene>
Stuart D. Gathman
2017-Apr-03 18:13 UTC
[Nut-upsuser] battery not installed, but battery still 100% and NUT 2.7.2-4 does not catch this and report a error
On Mon, 3 Apr 2017, Gene Heskett wrote:>> > Nut, IIRC, can do a periodic battery test by putting it offline, using > the battery, for a predetermined length of time, weekly, monthly etc,We definitely don't want that in this instance either! (Unless it is a dual PS server.) We want the ALARM that the nut driver is generating, and upsd is passing on - to be acted on in some way by upsmon. Which NOTIFYCMD is run when there is an ALARM? -- Stuart D. Gathman <stuart at gathman.org> "Confutatis maledictis, flamis acribus addictis" - background song for a Microsoft sponsored "Where do you want to go from here?" commercial.
Maybe Matching Threads
- battery not installed, but battery still 100% and NUT 2.7.2-4 does not catch this and report a error
- battery not installed, but battery still 100% and NUT 2.7.2-4 does not catch this and report a error
- battery not installed, but battery still 100% and NUT 2.7.2-4 does not catch this and report a error
- battery not installed, but battery still 100% and NUT 2.7.2-4 does not catch this and report a error
- battery not installed, but battery still 100% and NUT 2.7.2-4 does not catch this and report a error