search for: replbatt

On 04/01/2017 03:14 PM, Dan Craciun wrote: > On my Nagios monitoring system I use check_nut_plus (that in turn > calls upsc) to monitor the status (ups.status), load (ups.load), > battery charge (battery.charge) and runtime (battery.runtime). > > If these return "unknown", it means upsd is no longer monitoring the > UPS. As long as you get data, upsd is working. >

...e heart beats, there is no news, but if it stops, upssched-cmd sends out an e-mail or other warning. In ups.conf, add [heartbeat] driver = dummy-ups port = heartbeat.dev desc = "Dummy ups sends heart beat to upssched-cmd" In heartbeat.dev, write ups.status: REPLBATT TIMER 300 In upsmon.conf, write NOTIFYFLAG REPLBATT SYSLOG+EXEC In upssched.conf, add # Heatbeat from dummy ups every 5 minutes, re-start 6 minute timer AT REPLBATT heartbeat CANCEL-TIMER heatbeat-timer AT REPLBATT heartbeat START-TIMER heatbeat-timer 360 In upssched-cmd, if heatbeat-timer co...

...upssched-cmd sends out an e-mail or other warning. > > In ups.conf, add > > [heartbeat] > driver = dummy-ups > port = heartbeat.dev > desc = "Dummy ups sends heart beat to upssched-cmd" > > In heartbeat.dev, write > > ups.status: REPLBATT > TIMER 300 > > In upsmon.conf, write > > NOTIFYFLAG REPLBATT SYSLOG+EXEC > > In upssched.conf, add > > # Heatbeat from dummy ups every 5 minutes, re-start 6 minute timer > AT REPLBATT heartbeat CANCEL-TIMER heatbeat-timer > AT REPLBATT heartbeat START-TIMER heatbe...

On Jun 26, 2017, at 7:03 AM, Andrea de Lutti <adelutti at gmail.com> wrote: > > Are there no warnings for battery test? not sure if you saw my reply on 2016-06-17: Do you mean a notification that a test is in progress, or something for the results? There is the REPLBATT message in upsmon when the battery test fails, but I don't think the generic Qx protocol supports the RB status flag. You could possibly trigger on the OB status and look for the CAL flag in ups.status as well, but I haven't tried to automate that. ^^^ If you run "upsc $UPSNAME ups.s...

hello, i've got a problem with the notifycmd here is a part of my upsmon.conf : NOTIFYCMD /usr/local/ups/bin/nut_notify NOTIFYMSG ONLINE "UPS %s is getting line power" NOTIFYMSG ONBATT "UPS %s is on battery" NOTIFYMSG REPLBATT "The UPS %s battery is bad and needs to be replaced" NOTIFYMSG LOWBATT "UPS %s is being shutdown by the master" NOTIFYMSG FSD "Someone pulled the plug on %s" NOTIFYMSG COMMOK "Communications established with the UPS on %s" NOTIFYMSG COMMBAD "Communicatio...

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

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

...t; NOTIFYMSG FSD "UPS %s: forced shutdown in progress" NOTIFYMSG COMMOK "Communications with UPS %s established" NOTIFYMSG COMMBAD "Communications with UPS %s lost" NOTIFYMSG SHUTDOWN "Auto logout and shutdown proceeding" NOTIFYMSG REPLBATT "UPS %s battery needs to be replaced" NOTIFYMSG NOCOMM "UPS %s is unavailable" NOTIFYMSG NOPARENT "upsmon parent process died - shutdown impossible" NOTIFYFLAG ONLINE SYSLOG+WALL+EXEC NOTIFYFLAG ONBATT SYSLOG+WALL+EXEC NOTIFYFLAG LOWBATT...

...with upssched.conf: upsmon.conf MONITOR ups at localhost:3493 1 upsmon [REDACTED] MASTER NOTIFYCMD "/usr/local/sbin/upssched" NOTIFYFLAG ONBATT SYSLOG+EXEC NOTIFYFLAG LOWBATT SYSLOG+EXEC NOTIFYFLAG ONLINE SYSLOG+EXEC NOTIFYFLAG COMMBAD SYSLOG+EXEC NOTIFYFLAG COMMOK SYSLOG+EXEC NOTIFYFLAG REPLBATT SYSLOG+EXEC NOTIFYFLAG NOCOMM SYSLOG+EXEC NOTIFYFLAG REPLBATT SYSLOG+EXEC NOTIFYFLAG NOCOMM SYSLOG+EXEC NOTIFYFLAG FSD SYSLOG+EXEC NOTIFYFLAG SHUTDOWN SYSLOG+EXEC SHUTDOWNCMD "/sbin/shutdown -p now" POWERDOWNFLAG /etc/killpower HOSTSYNC 15 upssched.conf CMDSCRIPT "/usr/local/bin/s...

...00 AT ONLINE usv1 CANCEL-TIMER VERZ5 AT ONBATT usv1 START-TIMER VERZ8 480 AT ONLINE usv1 CANCEL-TIMER VERZ8 AT ONBATT * EXECUTE ONBATT AT ONLINE * EXECUTE ONLINE AT COMMOK * EXECUTE COMMOK AT COMMBAD * EXECUTE COMMBAD AT FSD * EXECUTE FSD AT LOWBATT * EXECUTE LOWBATT AT NOCOMM * EXECUTE NOCOMM AT REPLBATT * EXECUTE REPLBATT AT SHUTDOWN * EXECUTE SHUTDOWN Here are the 3 timers which should be started (VERZ2, VERZ5, VERZ8). --- upssched-cmd --- [...] case $1 in COMMBAD) notify $PAGER $1 "UPS communications lost" ;; COMMOK) notify $PAGER $1 "UPS communications established"...

...there is a next Windows release, perhaps the default NOTIFYFLAG's should be adjusted? NOTIFYFLAG ONLINE SYSLOG NOTIFYFLAG ONBATT SYSLOG NOTIFYFLAG LOWBATT SYSLOG NOTIFYFLAG FSD SYSLOG NOTIFYFLAG COMMOK SYSLOG NOTIFYFLAG COMMBAD SYSLOG NOTIFYFLAG SHUTDOWN SYSLOG NOTIFYFLAG REPLBATT SYSLOG NOTIFYFLAG NOCOMM SYSLOG NOTIFYFLAG NOPARENT SYSLOG The 'wall' messages (message.exe) don't pop-up and worst case, I had so many message.exe's running that all memory was consumed. This is because Windows hasn't allowed services to interact with the desktop fo...

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

...t; NOTIFYMSG FSD "UPS %s: forced shutdown in progress" NOTIFYMSG COMMOK "Communications with UPS %s established" NOTIFYMSG COMMBAD "Communications with UPS %s lost" NOTIFYMSG SHUTDOWN "Auto logout and shutdown proceeding" NOTIFYMSG REPLBATT "UPS %s battery needs to be replaced" NOTIFYMSG NOCOMM "UPS %s is unavailable" NOTIFYMSG NOPARENT "upsmon parent process died - shutdown impossible" NOTIFYFLAG ONLINE SYSLOG NOTIFYFLAG ONBATT SYSLOG NOTIFYFLAG LOWBATT SYSLOG NOTIFYFLAG...

...ADTIME 15 POWERDOWNFLAG /var/etc/killpower NOTIFYFLAG ONLINE SYSLOG+WALL+EXEC NOTIFYFLAG ONBATT SYSLOG+WALL+EXEC NOTIFYFLAG LOWBATT SYSLOG+WALL+EXEC NOTIFYFLAG FSD SYSLOG+WALL+EXEC NOTIFYFLAG COMMOK SYSLOG+WALL+EXEC NOTIFYFLAG COMMBAD SYSLOG+WALL+EXEC NOTIFYFLAG SHUTDOWN SYSLOG+WALL+EXEC NOTIFYFLAG REPLBATT SYSLOG+WALL+EXEC NOTIFYFLAG NOCOMM SYSLOG+WALL+EXEC NOTIFYFLAG NOPARENT SYSLOG+WALL+EXEC RBWARNTIME 43200 NOCOMMWARNTIME 300 FINALDELAY 5 ----------------------------------------------------------------------------------------------------------- nas4free: etc# more upssched.conf CMDSCRIPT /usr/loc...

...ONITOR qnapups at 192.168.222.252 3493 admin 123456 slave MINSUPPLIES 1 SHUTDOWNCMD "/sbin/shutdown -h +0" POLLFREQ 5 POLLFREQALERT 5 HOSTSYNC 15 DEADTIME 15 POWERDOWNFLAG /etc/killpower NOTIFYFLAG ONLINE SYSLOG+EXEC NOTIFYFLAG ONBATT SYSLOG+EXEC NOTIFYFLAG LOWBATT SYSLOG+EXEC NOTIFYFLAG REPLBATT SYSLOG+EXEC NOTIFYCMD /usr/sbin/upssched RBWARNTIME 43200 NOCOMMWARNTIME 300 FINALDELAY 5 And in /etc/nut/upssched.conf (changed from 2 min to 4 min) CMDSCRIPT /etc/nut/upssched-execscript.sh PIPEFN /etc/nut/upssched.pipe LOCKFN /etc/nut/upssched.lock AT ONBATT * START-TIMER shutdown_onba...

Thanks mates, as suggested I have added runtimecal = 240,100,720,50 default.battery.voltage.low = 10.4 default.battery.voltage.high = 13.8 (the actual charging voltage) In ups.conf I have also added the startup procedure in rc.local file, everything is fine... I have only to make a deep test. Is there a way to add a NOTIFYMSG value for the battery test? Thank you lots Andrea

On Thu, 8 Jun 2017, Robbie van der Walle wrote: > After the first test and the NAS is restarted I had to change the > setting battery.charge.low again to 80? Does the NAS DSM reset battery.charge.low to 10 or is it internal to the UPS? You will have to experiment by disconnecting the UPS control lead from the NAS and connecting it (if possible) to the Mac. After setting to 80 and a

Hi everybody, i'm trying to use the UPSNAME environment variable within the script launched by upssched, and although it is correctly written and thus read by my script, it doesn't get updated when multiple UPSes are configured. To be more precise i'm monitoring 2 UPSes and using AT *EVENT* * *OPERATION* *handle *to manage events in upssched.conf. Am i wrong somewhere? I'm

...t;UPS %s battery is low" NOTIFYMSG FSD "UPS %s: forced shutdown in progress" NOTIFYMSG COMMOK "Communications with UPS %s established" NOTIFYMSG COMMBAD "Communications with UPS %s lost" NOTIFYMSG SHUTDOWN "Auto logout and shutdown proceeding" NOTIFYMSG REPLBATT "UPS %s battery needs to be replaced" NOTIFYMSG NOCOMM "UPS %s is unavailable" NOTIFYMSG NOPARENT "upsmon parent process died - shutdown impossible" NOTIFYFLAG ONLINE SYSLOG+WALL <== add +EXEC to this line NOTIFYFLAG ONBATT SYSLOG+WALL ... NOTIFYFLAG LOWBATT SYS...