search for: finaldelay

...cs/user-manual.chunked/ Configuration_notes.html#UPS_shutdown, and also reading upsmon.c, when a UPS goes OB LB (assuming we have a single UPS connected to a primary and supplying power to the primary and some number of secondaries), the primary notifies the secondaries, the secondaries wait for FINALDELAY and then execute SHUTDOWNCMD immediately followed by exiting, thereby disconnecting from the primary, and the primary, after seeing all secondaries disconnect, proceed with its shutdown (only waiting for FINALDELAY), which ends with telling the UPS to cut the power (without delay too, right?)....

...figuration_notes.html#UPS_shutdown, and also reading upsmon.c, when a > UPS > goes OB LB (assuming we have a single UPS connected to a primary and > supplying > power to the primary and some number of secondaries), the primary notifies > the > secondaries, the secondaries wait for FINALDELAY and then execute > SHUTDOWNCMD > immediately followed by exiting, thereby disconnecting from the primary, > and > the primary, after seeing all secondaries disconnect, proceed with its > shutdown (only waiting for FINALDELAY), which ends with telling the UPS to > cut > the powe...

Hi, I have simple configuration: one master with one UPS connected via serial port, and five slaves. When battery is low and master set FSD on UPS, then after few seconds it get from all slaves: "disconnected (read failure)" and start shutdown and power off before slave shutdown complete, that need about 90 seconds. I don't understand, why slaves disconnected before shutdown go near

...bug : my ups run out of battery before the end of > the shutdown process (a full shutdown take less than 2 minutes). > > Is there a way to "start the shutdown process earlier", or to change the > battery.charge.low or battery.runtime.low variables? > > I try to set a FinalDelay to 0, but it doesn't help. > > Do you have any idea to help me? > > Thank you.

...down, and also reading upsmon.c, when a > > UPS > > goes OB LB (assuming we have a single UPS connected to a primary and > > supplying > > power to the primary and some number of secondaries), the primary notifies > > the > > secondaries, the secondaries wait for FINALDELAY and then execute > > SHUTDOWNCMD > > immediately followed by exiting, thereby disconnecting from the primary, > > and > > the primary, after seeing all secondaries disconnect, proceed with its > > shutdown (only waiting for FINALDELAY), which ends with telling the UPS...

...Connection to pi closed. ################ I ran this command under two sets of conditions: - UPS plugged in to the mains - UPS unplugged from the mains, then plugging it back in approximately 60 seconds after it turned off In both cases, the Pi shut down cleanly after approximately 5 seconds (FINALDELAY?), and the UPS turned off after approximately 25 seconds (FINALDELAY + the default offdelay?) However, the UPS never came back up. Second Experiment ################# $ sudo upsdrvctl shutdown Network UPS Tools - UPS driver controller 2.7.4 Network UPS Tools - Generic HID driver 0.41 (2.7.4) USB c...

...rom source on Xenserver 5.6 SP2 (Linux xen-home 2.6.32.12-0.7.1.xs5.6.100.323.170596xen #1 SMP Fri Apr 8 07:25:07 EDT 2011 i686 athlon i386 GNU/Linux), my UPS is Powercom WOW--500U FW3.A4. All works almost fine but here are some troubles: when I pull the plug then upsd immediately starts (after FINALDELAY delaying) the procedure of shutdown as if UPS have low battery. What I see after pulling the plug: ./upsc xen-home battery.charge 72 ./upsc xen-home ups.status OB DISCHRG OB status is correct but why is there DISCHRG status?! This flag, as I think, cause immediately begin of shutdown although...

...OWS\\system32\\shutdown.exe -s -t 0" NOTIFYCMD /sbin/upssched POLLFREQ 5 POLLFREQALERT 5 HOSTSYNC 15 DEADTIME 15 POWERDOWNFLAG "C:\\killpower" NOTIFYFLAG ONLINE SYSLOG+WALL+EXEC NOTIFYFLAG ONBATT SYSLOG+WALL+EXEC NOTIFYFLAG LOWBATT SYSLOG+WALL+EXEC RBWARNTIME 43200 NOCOMMWARNTIME 300 FINALDELAY 5 upssched.conf: * * CMDSCRIPT /bin/upssched-cmd AT ONBATT * START-TIMER onbattwarn 10 AT ONLINE * CANCEL-TIMER onbattwarn AT LOWBATT * EXECUTE lowbattwarn AT ONBATT * START-TIMER timeshutdown 100 AT ONLINE * CANCEL-TIMER timeshutdown After start I can see couple neutral events: ups...

Hi! Trying to set up NUT on Centos 5 to monitor a CyberPower 1500AVR UPS. There seem to be many documents, all of which seem to be not fully consistent with each other, and most of them aren't up to date. I'm guessing I should be using udev rather than hal, but I'm somewhat stumped on how to figure out what device it should be monitoring. there are a bunch of udev rules installed

...SYNC set to 15 Level INFO 10/26/2016 10:46:17 Config Load: DEADTIME set to 15 Level INFO 10/26/2016 10:46:17 Config Load: RBWARNTIME set to 43200 Level INFO 10/26/2016 10:46:17 Config Load: NOCOMMWARNTIME set to 300 Level INFO 10/26/2016 10:46:17 Config Load: FINALDELAY set to 5 Level CRITICAL 10/26/2016 10:46:17 Fatal error: insufficient power configured! Level CRITICAL 10/26/2016 10:46:17 Sum of power values........: 0 Level CRITICAL 10/26/2016 10:46:17 Minimum value (MINSUPPLIES): 1 Level CRITICAL 10/26/2016 10:46:17 Edit your upsmon.conf a...

Yes both UPS units are on different power supplies. MINSUPPLIES is set to 1. Afaik NUT waits for OB and LB before shutting down the system. Is there a way to change this behavior to only wait for OB? Then I would use FINALDELAY in case the power outage doesn't last long. I already tried to change the battery.runtime.low setting over the webinterface of the CS121 (snmp is readonly) but with our AEG UPS, this didn't work as expected(seems like a firmware bug) and I need to work around this problem. I'm already...

...fectly but when i start upsmon i recive the message: POWERDOWNFLAG (/etc/killpower) does not contain the upsmon magic string My upmon.conf contain: MONITOR myups@theseo 1 orion91 carlos81 master SHUTDOWNCMD "/sbin/shutdown -h +0" HOSTSYNC 15 POWERDOWNFLAG /etc/killpower FINALDELAY 5 My killpower scrit in /etc/killpower contain: #!/bin/bash if (test -f /etc/killpower) then echo "Killing the power, bye!" /sbin/upsdrvctl shutdown sleep 120 # uh oh... the UPS poweroff failed! # you probably should reboot h...

...ssword = **** actions = SET instcmds = ALL [upsmon] password = **** upsmon master /etc/nut/upsmon.conf : RUN_AS_USER nut MINSUPPLIES 1 SHUTDOWNCMD "/sbin/shutdown -h +0" POLLFREQ 5 POLLFREQALERT 5 HOSTSYNC 15 DEADTIME 15 POWERDOWNFLAG /etc/killpower RBWARNTIME 43200 FINALDELAY 5 MONITOR dell at localhost 1 upsmon **** master /etc/nut/upssched.conf : CMDSCRIPT /etc/nut/sched/upssched.sh (this script exists but seems never to be executed...) PIPEFN /etc/nut/sched/upssched.pipe LOCKFN /etc/nut/sched/upssched.lock # the timers, here 30 sec after the ONBATT (ups on battery...

...here other variables that are affected? (I don't think the IDG400 is covered in the protocol documentation that the NUT project received a while back.) > > For the point number 2, as we know NUT perfomrs the shutdown after battery low signal with a delay of 5 seconds as specified in the FINALDELAY. > Is this correct? Right, NUT tells the computer to shut down, but it also typically sends a shutdown signal to the UPS. Does the IDG400 also respond to the same shutdown command as others?

...ONLINE NOTIFYMSG ONBATT ONBATT NOTIFYMSG LOWBATT LOWBATT NOTIFYMSG FSD FSD NOTIFYFLAG ONLINE SYSLOG+WALL+EXEC NOTIFYFLAG ONBATT SYSLOG+WALL+EXEC NOTIFYFLAG LOWBATT SYSLOG+WALL+EXEC NOTIFYFLAG FSD SYSLOG+WALL+EXEC RBWARNTIME 43200 NOCOMMWARNTIME 300 FINALDELAY 5 I also tried NOTIFYCMD C:\\NUT\\shutdown.bat NOTIFYCMD "\"C:\\NUT\\shutdown.bat"" with no success. NUT 2.6.1-1 with replaced upsmon.exe from here: http://fbohe.free.fr/upsmon.exe. Windows 2003 R2 x64 Rusian. Master server is Debian Squeeze. Regards, Dmitry

...PLIES 1 SHUTDOWNCMD "/sbin/shutdown -h +0" NOTIFYCMD /sbin/upssched POLLFREQ 5 POLLFREQALERT 5 HOSTSYNC 15 DEADTIME 15 POWERDOWNFLAG /etc/killpower NOTIFYFLAG ONLINE SYSLOG+WALL+EXEC NOTIFYFLAG ONBATT SYSLOG+WALL+EXEC NOTIFYFLAG LOWBATT SYSLOG+WALL+EXEC RBWARNTIME 43200 NOCOMMWARNTIME 300 FINALDELAY 5 *upssched.conf:* CMDSCRIPT /bin/upssched-cmd AT ONBATT * START-TIMER onbattwarn 10 AT ONLINE * CANCEL-TIMER onbattwarn AT LOWBATT * EXECUTE lowbattwarn AT ONBATT * START-TIMER timeshutdown 100 AT ONLINE * CANCEL-TIMER timeshutdown There are huge count of windows events such as &quo...

...*** master MINSUPPLIES 1 SHUTDOWNCMD "/sbin/shutdown -h +0" NOTIFYCMD /home/android/nutShutdown.sh POLLFREQ 5 POLLFREQALERT 5 HOSTSYNC 15 DEADTIME 15 POWERDOWNFLAG /etc/killpower NOTIFYMSG ONBATT "UPS %s on battery" NOTIFYFLAG ONBATT WALL+EXEC RBWARNTIME 43200 NOCOMMWARNTIME 300 FINALDELAY 5 ########### /etc/nut/upssched.conf ########### CMDSCRIPT /bin/upssched-cmd ########### <scriptname> ########### Cannot access <scriptname> ########### /etc/hosts.allow ########### ########### ps aux ########### nut 2333 0.0 0.0 3336 696...

...YSLOG+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 RBWARNTIME 43200 NOCOMMWARNTIME 300 FINALDELAY 5 What am I missing? Thanks! -- David Benfell, LCP benfell@parts-unknown.org --- Resume available at http://www.parts-unknown.org/

Hi, I've got two MGE Ellipse 1500 UPS connected via usb to an ubuntu jaunty system with nut and libupsclient1 2.4.1-2ubuntu4. As soon as I start the driver for the second one, they start fighting each other and I get no data. I found an older post to this list that said: If you want to monitor multiple UPSes through usbhid-ups, you *must* make sure that each one can be uniquely identified

OS name and version, MASTER SYSTEM has three APC smart UPS 3000 UPS connected via USB debian 8 "jessie" Linux pdxvhtst01 3.16.0-4-amd64 #1 SMP Debian 3.16.43-2+deb8u5 (2017-09-19) x86_64 GNU/Linux SLAVE SYSTEMS monitoring MASTER via IP debian 8 "jessie" Linux geaaetst01