search for: onbatt

Hi Roger, I get: Apr 27 20:50:05 unifi upsmon[1022]: UPS ups on batteryApr 27 20:50:05 unifi upssched[2688]: Timer daemon startedApr 27 20:50:06 unifi upssched[2688]: New timer: onbatt (20 seconds)Apr 27 20:50:26 unifi upssched[2688]: Event: onbattApr 27 20:50:26 unifi upssched[2688]: exec_cmd(/sbin/upssched-cmd.sh onbatt) returned 126Apr 27 20:50:41 unifi upssched[2688]: Timer queue empty, exiting /etc/nut/upssched.conf CMDSCRIPT /sbin/upssched-cmd.shPIPEFN /etc/nut/upssched/up...

...lugged : > > May 9 11:39:34 serveur upsmon[6411]: UPS ellipse@localhost on battery > May 9 11:39:34 serveur upssched[6823]: Timer daemon started > May 9 11:39:34 serveur upssched[6823]: New timer: phone_alert (15 > seconds) > May 9 11:39:34 serveur upssched[6823]: New timer: onbatt (900 seconds) > May 9 11:39:49 serveur upssched[6823]: Event: phone_alert > May 9 11:39:49 serveur upssched[6823]: Execute command failure: > /root/scripts/upsalert phone_alert: No such file or directory > May 9 11:40:19 serveur upsmon[6411]: UPS ellipse@localhost on line power >...

...Battery" instantly, instead of after 20s. Power returned after 55 seconds. Could I be missing some dependency, external application, which upsmon uses as a timer? (A side issue is that it's not using the correct variable when passing to upssched-cmd, but uses the notify text itself, "ONBATT", this can be seen in the last line from, messages, $1 is "UPS ups0 at localhost on line power", but this is not important for me, but may be used to explain why the timer is not working) ONBATT Dec 2 18:48:56 storage01 upsmon[3603]: ONBATT Dec 2 18:48:56 storage01 wall[4371]: wa...

.... I checked my configuration more than two times and I don't find the failure. Maybe someone can help me and tell me where the failure could be. --- syslog --- May 13 21:50:34 s-monitor1 upsmon[1674]: UPS usv3 at localhost on battery May 13 21:50:34 s-monitor1 upssched[855]: Executing command: ONBATT May 13 21:50:34 s-monitor1 upssched[855]: exec_cmd(/etc/nut/upssched-cmd ONBATT) returned 126 May 13 21:51:04 s-monitor1 upsmon[1674]: UPS usv1 at localhost on battery May 13 21:51:04 s-monitor1 upsmon[1674]: UPS usv2 at localhost on battery May 13 21:51:04 s-monitor1 upssched[1173]: Executing comm...

...driver = usbhid-ups port = auto ignorelb override.battery.charge.low = 90 /usr/etc/upsmon.conf MONITOR ups_genric at 127.0.0.1 1 ups_user pass admin master SHUTDOWNCMD "/sbin/shutdown -h +0" POWERDOWNFLAG /etc/nut/killpower NOTIFYFLAG ONBATT SYSLOG+WALL+EXEC NOTIFYFLAG ONLINE SYSLOG+WALL+EXEC NOTIFYCMD "/usr/sbin/upssched" /usr/etc/upssched.conf CMDSCRIPT /usr/etc/ups_cmd_file PIPEFN /usr/etc/upssched.pipe LOCKFN /usr/etc/upssched.lock AT ONBATT * START-TIMER onbatt 120 AT...

Now that upsstats.cgi works, I've noticed that dummy-ups changes state every 5 minutes between OL and OB (probably when the 300 second timer expires). The UPS state stays online. Also "online" and "onbatt" are broadcast to the console probably via WALL. (The state changes don't seem to be form the ups as upsshed-cmd doesn't run). Upssched-cmd does run when the UPS is actually unplugged and plugged back in. It happens on two different installation. See attached screenshot and configur...

Hi, my UPS (APC SMC1000C) goes to ONBATT every day for a few seconds. This event is emitted because of the short daily UPS self-test, which cannot be disabled. Depending on the poll interval upsmon/NUT sometimes picks this event up and a power failure is logged, even if this is not a real power outage. I would like to prevent that. Now...

...upssched-cmd:: 2024-02-23_09.42.31 upssched-cmd running Feb 23 09:42:31 windows10production upssched-cmd:: nocomm-timer-expired -------------- next part -------------- CMDSCRIPT /etc/nut/upssched-cmd PIPEFN /var/state/ups/upssched/upssched.pipe LOCKFN /var/state/ups/upssched/upssched.lock AT ONBATT ups at localhost EXECUTE onbatt AT ONBATT ups at localhost START-TIMER onbatt-timer 10 AT ONBATT ups at localhost CANCEL-TIMER lowbatt-timer AT ONBATT ups at localhost CANCEL-TIMER shutdown-timer AT ONBATT ups at localhost START-TIMER beeperoff 60 AT ONBATT ups at localhost EXECUT...

...****m**** primery MONITOR heartbeat at localhost 0 heartbeat ****m**** MINSUPPLIES 1 SHUTDOWNCMD "/sbin/shutdown -h +2" NOTIFYCMD /etc/nut/upssched-cmd POLLFREQ 10 POLLFREQALERT 5 HOSTSYNC 15 DEADTIME 30 POWERDOWNFLAG /etc/killpower NOTIFYMSG ONLINE "online" NOTIFYMSG ONBATT "onbatt" NOTIFYMSG LOWBATT "lowbatt" NOTIFYMSG FSD "fsd" NOTIFYMSG COMMOK "commok" NOTIFYMSG COMMBAD "commbad" NOTIFYMSG SHUTDOWN "shutdown" NOTIFYMSG REPLBATT "replacebatt" NOTIFYMSG...

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

...0 upsmaster xxx primary MINSUPPLIES 1 NOTIFYCMD /sbin/upssched SHUTDOWNCMD "/sbin/shutdown -h +0" POLLFREQ 5 POLLFREQALERT 5 HOSTSYNC 15 DEADTIME 15 POWERDOWNFLAG /etc/killpower RBWARNTIME 43200 NOCOMMWARNTIME 300 FINALDELAY 5 NOTIFYMSG ONLINE "UPS %s: On line power." NOTIFYMSG ONBATT "UPS %s: On battery." NOTIFYMSG LOWBATT "UPS %s: Battery is low." NOTIFYMSG REPLBATT "UPS %s: Battery needs to be replaced." NOTIFYMSG FSD "UPS %s: Forced shutdown in progress." NOTIFYMSG SHUTDOWN "Auto logout and shutdown proceeding." NOTIFYMSG COM...

...you have SELinux enabled? Regards, Neil. On 27/04/15 20:55, James Hammond wrote: > Hi Roger, > > I get: > > Apr 27 20:50:05 unifi upsmon[1022]: UPS ups on battery > Apr 27 20:50:05 unifi upssched[2688]: Timer daemon started > Apr 27 20:50:06 unifi upssched[2688]: New timer: onbatt (20 seconds) > Apr 27 20:50:26 unifi upssched[2688]: Event: onbatt > Apr 27 20:50:26 unifi upssched[2688]: exec_cmd(/sbin/upssched-cmd.sh > onbatt) returned 126 > Apr 27 20:50:41 unifi upssched[2688]: Timer queue empty, exiting > > > /etc/nut/upssched.conf > > CMDSCRIPT /...

...tdown and logging configuration is set right? I had hoped I set it up right to at least log when it goes and off battery but I guess I missed something. /etc/nut# grep upssched /var/log/syslog Apr 3 12:31:06 gw upssched[12732]: Timer daemon started Apr 3 12:31:06 gw upssched[12732]: New timer: onbatt (30 seconds) Apr 3 12:31:36 gw upssched[12732]: Event: onbatt Apr 3 12:31:36 gw upssched-cmd: Unrecognized command: onbatt Apr 3 12:31:51 gw upssched[12732]: Timer queue empty, exiting Apr 3 16:03:55 gw upssched-cmd: Unrecognized command:

On Fri, 9 Jun 2017, Robbie van der Walle wrote: > ... and also still open is the notification on the Mac. If notify-send is available on the Mac, then perhaps this will work: In upsmon.conf on the Mac you need NOTIFYCMD /usr/sbin/upssched (or wherever this goes on a Mac) NOTIFYFLAG ONBATT SYSLOG+EXEC In upssched.conf you need CMDSCRIPT /usr/sbin/upssched-cmd (or wherever this goes on a Mac) AT ONBATT UPS at NAS EXECUTE on-battery In upssched-cmd you need case $1 in (on-battery) MSG="Power failure. Save your work!" notify-send -a nut -u critical...

Hi, I am unable to get upssched working correctly as my UPS calls low battery too late and there is no way to change it. I am running Nut 2.7.3 on Ubuntu 14.04 I have made this script, called /sbin/upssched-cmd.sh #!/bin/sh case $1 in onbatt) /sbin/upsmon -c fsd;; *) echo "shutdown implemented";; esac I am trying to run the script manually to break down my issues. All that happens when I run the script is I get the echo script but no shutdown, effectively the script doesn't seem to run the command /sbin/upsmon -...

...rd slave Webserver2 MONITOR ups-webserver2 at webserver1 1 ups-webserver2-master mypassword master MONITOR ups-webserver1 at localhost 0 ups-webserver1-slave mypassword slave It needs the following upsmon.conf NOTIFYCMD /usr/sbin/upssched NOTIFYFLAG ONLINE SYSLOG+WALL+ NOTIFYFLAG ONBATT SYSLOG+WALL+EXEC Configure 'upssched' by editing upssched.conf upssched.conf webserver1 CMDSCRIPT /bin/upssched-cmd PIPEFN /var/lib/ups/upssched/upssched.pipe LOCKFN /var/lib/ups/upssched/upssched.lock AT ONBATT ups-webserver2 at localhost START-TIMER onbatt-ups-webserver2 600 AT ONLI...

...mes Hammond wrote: > I am unable to get upssched working correctly as my UPS calls low > battery too late and there is no way to change it. I am running Nut > 2.7.3 on Ubuntu 14.04 I have made this script, called > /sbin/upssched-cmd.sh > > #!/bin/sh > case $1 in > onbatt) > /sbin/upsmon -c fsd;; > *) > echo "shutdown implemented";; > esac Hi, Just wondering, do you have a line in upssched.conf which specifies CMDSCRIPT /sbin/upssched-cmd.sh ? Roger _______________________________________________ Nut-upsuser mailing list Nut...

...NAS and connecting it (if possible) to the Mac. After setting to 80 and a power off-on cycle is the value 80 or 10? > 3. Users from the NAS are warned, not yet the Mac user.? Only when > executing automatic power-fail shutdown.? In upsmon.conf on the Mac, what are the values of NOTIFYMSG ONBATT and NOTIFYFLAG ONBATT? Does program wall work on the Mac? It fails on a lot of Linux boxes with graphical interfaces - to get a message to the user, you have to use notify-send, which means setting up upssched. > 7. No they didn?t restart. I know there is a setting on the NAS to > activ...

Hi, I've been getting emails from upsmon saying: Subject: UPS PW5125 at localhost notification: ONBATT UPS PW5125 at localhost on battery But then the machines on the UPS stay on for hours; we haven't got that kind of runtime, more like 10-20 minutes. After a few occurrences, it now happened at a time where I could log in to see in real time what is happening and: $ upsc PW5125 | grep statu...

...r bggjy master MINSUPPLIES 1 SHUTDOWNCMD "/sbin/shutdown -h +0" NOTIFYCMD /sbin/upssched POLLFREQ 5 POLLFREQALERT 5 HOSTSYNC 15 DEADTIME 15 POWERDOWNFLAG /etc/killpower NOTIFYMSG LOWBATT "UPS %s battery is critically low" NOTIFYFLAG ONLINE SYSLOG+WALL+EXEC NOTIFYFLAG ONBATT SYSLOG+WALL+EXEC NOTIFYFLAG FSD SYSLOG+WALL+EXEC RBWARNTIME 43200 NOCOMMWARNTIME 300 FINALDELAY 20 ------------- upssched.conf: CMDSCRIPT /usr/local/bin/upssched-cmd PIPEFN /var/run/nut/upssched/upssched.pipe LOCKFN /var/run/nut/upssched/upssched.lock AT ONBATT * EXECUTE onbatt AT ON...