Nut upsuser - Apr 2017 - 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!
>
> Why not? If the battery has a holdup time of 5 minutes when its fresh,
Because in this instance it crashes your system, corrupts filesystems,
etc, etc.
>> 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?
>
> I've not read the docs in ages, but if there isn't something
mentioned in
> a man upsmon, I would be unpleasantly surprised.
>
> According to my copy, it does a -wall (warn all) by default, and it looks
> like REPLBATT is one such message, and the default time for a repeat is
> 12 hours.  The -wall type message shows on every open terminal on the
> system's network, so someone should see it.  From the upsmon.conf file:
That would be great if "we" (the original poster) were getting a
REPLBATT...
> NOTIFYCMD command
... long winded reiteration of man pages....

I think what we have here is a bug/oversight in upsmon, which we might be able
to create a nice test case for using the dummy-ups driver.  It is not 
clear if it can generate the composite status "ALARM OL", but I will
try
in a bit.  If it can't, maybe a patch for dummy-ups is in order.

-- 
 	      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.

Which gets back to the original point I was trying to make. Iy the UPS does a
load test (and I'm pretty certain My SmartUPS can, if enabled), you know the
battery is failing *before* something face-plants, thus *reducing* risk! I test
on all mine, and have never in 15+ years of doing so, had anything go down
unintentionally . . . The fact that you have not tested is why you find yourself
with such a bad battery . . .

- Tim

On April 3, 2017 3:39:30 PM CDT, "Stuart D. Gathman" <stuart at
gathman.org> wrote:
>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!
>>
>> Why not? If the battery has a holdup time of 5 minutes when its
>fresh,
>
>Because in this instance it crashes your system, corrupts filesystems,
>etc, etc.
>
>>> 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?
>>
>> I've not read the docs in ages, but if there isn't something
>mentioned in
>> a man upsmon, I would be unpleasantly surprised.
>>
>> According to my copy, it does a -wall (warn all) by default, and it
>looks
>> like REPLBATT is one such message, and the default time for a repeat
>is
>> 12 hours.  The -wall type message shows on every open terminal on the
>> system's network, so someone should see it.  From the upsmon.conf
>file:
>
>That would be great if "we" (the original poster) were getting a
>REPLBATT...
>
>> NOTIFYCMD command
>... long winded reiteration of man pages....
>
>I think what we have here is a bug/oversight in upsmon, which we might
>be able
>to create a nice test case for using the dummy-ups driver.  It is not 
>clear if it can generate the composite status "ALARM OL", but I
will
>try
>in a bit.  If it can't, maybe a patch for dummy-ups is in order.
>
>-- 
> 	      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.
>
>_______________________________________________
>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/6e93be3c/attachment.html>

On Monday 03 April 2017 16:39:30 Stuart D. Gathman wrote:
> 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!
> >
> > Why not? If the battery has a holdup time of 5 minutes when its
> > fresh,
>
> Because in this instance it crashes your system, corrupts filesystems,
> etc, etc.
>
But it does that because you have tried to get 12  years out of a gell 
cell battery that is doing really really well if you get 4 years out of 
it. I am not saying you should do that _now_, without first replacing 
that thoroughly boiled dry battery, but as something you should set it 
up to do once you have a serviceable battery set installed in it.  That 
way, you would be getting warnings before this replacement battery is 
deep into its failure.  THIS is how you best prevent these surprise 
failures that are probably causing recovery nightmares and lost profit 
opportunities because of the downtime.

A good manager isn't the one who spends less money, thinking it improves 
the P&L report.  He is the one who spends the money wisely to maintain 
as close to 100% uptime as he can.  Do that, and the P&L report will 
take care of itself.
> >> 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?
Have you specified that in your upsmon.conf?  And have you verified that 
the resources it needs to send that warning message are available on 
your systems? See man wall and test the default. You will have to 
compose a one line file, and name that file in order to send the 
contents of that file to users.

Create that file:
echo "I need a fresh battery" >rplbat.

Then do wall rplbat
and get this on every screen on the system:
gene at coyote:~$ sudo wall rplbat
                                                                               
Broadcast Message from gene at coyo
        (/dev/pts/2) at 18:56 ...                                              
                                                                               
I need a fresh battery                                                         

Which can be embellished by naming the ups that needs the battery I 
believe.

Now, I'll bow out and let the nut maintainers advise from here. I am just 
a happy nut user trying to help.

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>

On 04/03/2017 07:03 PM, Gene Heskett wrote:
>
> But it does that because you have tried to get 12  years out of a gell 
> cell battery that is doing really really well if you get 4 years out of 
> it. I am not saying you should do that _now_, without first replacing 
> that thoroughly boiled dry battery, but as something you should set it 
> up to do once you have a serviceable battery set installed in it.  That 
Absolutely.  But as you say, that is NOT recommended for the original
poster *now* until he replaces said dead battery
(I actually recommended replacing the entire UPS to get an AVR
model).
>>>> 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?
Have you specified that in your upsmon.conf?

And that is the question of the hour.  How do you specify that?  Note
that this is not the REPLBATT status we are talking about.