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

Hi Jon, Stuart and the list

2017-04-04 1:09 GMT+02:00 Stuart Gathman <stuart at gathman.org>:
> 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.
>
It's true that upsmon doesn't deal with ALARM, and that's definitely
something missing.

What about adding a <notify type> "ALARM" to upsmon (and its
.conf), and
have it processing like other notifications?
That would mean to you can have WALL / SYSLOG notifications, along with
EXEC reaction if NOTIFYCMD is set.

cheers,
Arno
-- 
Eaton Data Center Automation Solutions - Opensource Leader -
http://42ity.org
NUT (Network UPS Tools) Project Leader - http://www.networkupstools.org
Debian Developer - http://www.debian.org
Free Software Developer - http://arnaud.quette.fr
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20170404/9c3ceb15/attachment.html>

On Tue, 4 Apr 2017, Arnaud Quette wrote:
> Hi Jon, Stuart and the list
> 
> 2017-04-04 1:09 GMT+02:00 Stuart Gathman <stuart at gathman.org>:
>       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.
> 
> It's true that upsmon doesn't deal with ALARM, and that's
definitely something missing.
> 
> What about adding a <notify type> "ALARM" to upsmon (and
its .conf), and have it processing like other notifications?
> That would mean to you can have WALL / SYSLOG notifications, along with
EXEC reaction if NOTIFYCMD is set.
Hi Arnaud, It seems to me that, looking out into the future, there are 
three things upsmon needs:

1. A fall-through <notify type> of "UNKNOWN" so that all status
changes,
no matter how wierd, can be caught.  Such a catch-all <notify type> would 
also have caught the "ALARM" from the old battery.

2. A UPS specific option in the NOTIFYFLAG and NOTIFYMSG declarations as 
already provided by the AT declaration in upssched.conf.  This would make 
it possible to have messages and action specific to a UPS, in a multi-UPS 
configuration.

I would like to be able to specify

    NOTIFYMSG myups at localhost      ONBATT "%s: local UPS on
battery"
    NOTIFYMSG bigups at server        ONBATT "%s: Server room alert: UPS on
battery"

    NOTIFYFLAG myups at localhost     ONBATT SYSLOG+EXEC+WALL
    NOTIFYFLAG heartbeat at localhost ONBATT SYSLOG+EXEC

3. A <notify type> "ALARM" as you propose.

Best Regards, Roger