search for: killpower

Hi to all, i install nut and it's work perfectly 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 i...

On Jan 31, 2015, at 3:09 PM, Melvin Call <melvincall979 at gmail.com> wrote: > One last question if you don't mind. I noticed the "default" POWERDOWNFLAG is > set to /etc/killpower, but I changed that to /tmp and modified my umountroot > script to mount it read only too, because I know it gets wiped on reboot. Is > there anything that removes /etc/killpower on reboot, or a more compelling > reason to put killpower in /etc, other than it is usually not on a separate &...

...ld have helped, but it is a clue for anyone else that comes across this thread. I am up and talking to the UPS, so it should just be a matter of getting my shutdown stuff working at this point. One last question if you don't mind. I noticed the "default" POWERDOWNFLAG is set to /etc/killpower, but I changed that to /tmp and modified my umountroot script to mount it read only too, because I know it gets wiped on reboot. Is there anything that removes /etc/killpower on reboot, or a more compelling reason to put killpower in /etc, other than it is usually not on a separate partition? Than...

On 1/31/15, Charles Lepple <clepple at gmail.com> wrote: > On Jan 31, 2015, at 3:09 PM, Melvin Call <melvincall979 at gmail.com> wrote: > >> One last question if you don't mind. I noticed the "default" POWERDOWNFLAG) >> is >> set to /etc/killpower, but I changed that to /tmp and modified my >> umountroot >> script to mount it read only too, because I know it gets wiped on reboot. >> Is >> there anything that removes /etc/killpower on reboot, or a more >> compelling >> reason to put killpower in /etc, other...

...is not powered by it. When running "upsmon -c fsd", upsmon says "Auto logout and shutdown proceeding". This is all well and good, but I never see the machine waiting for the UPS to cut the power. Instead it shuts down. It's my understanding that upsmon should create /etc/killpower, report this found in the syslog, and then wait for the power to be cut. Maybe I have misunderstood something? Thanks, Tobias

...about dead at this point, the computer starts to boot up only till the UPS completely dies since its batteries are depleted. This is what is happening: - Low Battery setpoint reached --> issue computer shutdown - Shutdown commands sent --> computer starts shutting down - At some point, /etc/killpower is sent before computer fully shuts down - Computer shuts down - A few seconds later, I hear a clunk in the UPS (UPS powers off... I used a multimeter to verify no AC voltage on the UPS output outlets) - Another few seconds later, I hear another clunk in the UPS --> computer starts to power on -...

Hello mailing list I read in the snmp-ups manpage that this driver does not provide a shutdown function because there will be no network at the point it is called. So I studied the Ubuntu initscripts, and in fact the network is killed in /etc/rc0.d/S35networking while the driver would be called at /etc/rc0.d/S90halt so this is correct... however! ...disabling the S35networking seems a simple

...ust the first part of the example from Price, I see : [CODE]# /etc/ups/upsmon.conf?MONITOR Eaton-66781 at localhost 1 upsmaster sekret master?MINSUPPLIES 1?SHUTDOWNCMD "/sbin/shutdown -h +0"?NOTIFYCMD /usr/sbin/upssched?POLLFREQ 5?POLLFREQALERT 5?HOSTSYNC 15?DEADTIME 15?POWERDOWNFLAG /etc/killpower[CODE] I have modified the MONITOR line as appropriate for my system but wonder about a coupleof entries. ?The referenced binary '/usr/sbin/upssched' appears to be in '/sbin' not '/usr/sbin' .Is that the '/sbin/upssched' the correct file to use ? ?Also, the '/etc/...

...d the UPS to run with the PowerMust driver. My problem however is when I test the powerdown function by issuing the command: 'upsmon -c fsd' The UPS is cutting the power before the shutdown procedure of FreeBSD is done. I have added the following to /etc/rc.shutdown: if (test -f /etc/killpower) then echo "Killing the power, bye!" /usr/local/libexec/nut/upsdrvctl shutdown fi I dropped the sleep command, as it doesn't have the desired effect on FreeBSD. After looking in the mailing list archives I found out that you can add a delay on the powerdown...

On Feb 1, 2015, at 7:04 AM, Melvin Call <melvincall979 at gmail.com> wrote: > Thank you Charles, for the assistance and the information. Everything is > completely functional here now. Not sure if the APC BackUPS ES550 is on the > list of compatible devices, but it works just fine with the usbhid-ups driver, > and supports several basic commands. You're welcome! We do have

...ER nut MONITOR pulsar at localhost 1 admin1 lahdnets master MINSUPPLIES 1 FINALDELAY 5 HOSTSYNC 15 NOTIFYCMD /home/nut/alert_ups.sh # NOTIFYCMD /sbin/upssched SHUTDOWNCMD "/sbin/shutdown -h +0" POLLFREQ 5 POLLFREQALERT 5 DEADTIME 15 NOCOMMWARNTIME 300 RBWARNTIME 43200 # POWERDOWNFLAG /etc/killpower NOTIFYMSG ONLINE "UPS %s on line power" NOTIFYMSG ONBATT "UPS %s on battery" NOTIFYFLAG ONBATT SYSLOG+WALL+EXEC NOTIFYFLAG ONLINE SYSLOG+WALL+EXEC when the server stops, the log is not generated and Same with upssched ... where can I seach ? Thank you for your help -- Sa...

...shutdown seems kill off all those processes prior to excuting my upsdrvctl shutdown command, thereby preventing any ups communications and yup, the power don't get killed. rc.shutdown snippet: ... [code to run all rc.d stop script here] ... # Insert other shutdown procedures here if [ -f /etc/killpower ]; then echo "Killing the power, bye!" /usr/local/ups/bin/upsdrvctl shutdown <<< oops, upsd is already dead sleep 120 reboot fi ... rc.local snippet, for what it's worth: ... /usr/local/ups/bin/upsdrvctl start /usr/local/ups/sbin/upsd /usr/l...

APC Smart-UPS X 1500 Restart Issue. Hi All, I have installed nut-2.4.3. I have manually modified the files apc-hid.c and udev-rules to support 5G APC UPS. I took sample code from the 2.5 development tree. Shutdown process is working very well -- upsmon creates the file /etc/killpower - shutdown script checks for the file and issues /sbin/upsdrvctl shutdown - UPS cuts the power off. All is well. I am facing an issue when power is reapplied to the UPS. Following is the behavior I see: 1. Power comes back to the outlet. 2. System powers up. 3. When system reaches "Sta...

APC Smart-UPS X 1500 Restart Issue. Hi All, I have installed nut-2.4.3. I have manually modified the files apc-hid.c and udev-rules to support 5G APC UPS. I took sample code from the 2.5 development tree. Shutdown process is working very well -- upsmon creates the file /etc/killpower - shutdown script checks for the file and issues /sbin/upsdrvctl shutdown - UPS cuts the power off. All is well. I am facing an issue when power is reapplied to the UPS. Following is the behavior I see: 1. Power comes back to the outlet. 2. System powers up. 3. When system reaches "Sta...

...l on printing that is NOT set, because that's normal. I think it would be good to stat the dir containing POWERDOWNFLAG and print a warning if it is not there. All the notable things that lead to shutdown (UPS going on battery, lowbatt, decision to shutdown, setting FSD flag, setting killpower, calling shutdown) are fair game for syslog. syslog should mostly survive for post-mortem analysis console output is ephemeral anyway, usually extra info is harmful because it makes everything harder to read; a bigger haystack to find a needle (which may be not about nut) Specifical...

...l on printing that is NOT set, because that's normal. I think it would be good to stat the dir containing POWERDOWNFLAG and print a warning if it is not there. All the notable things that lead to shutdown (UPS going on battery, lowbatt, decision to shutdown, setting FSD flag, setting killpower, calling shutdown) are fair game for syslog. syslog should mostly survive for post-mortem analysis console output is ephemeral anyway, usually extra info is harmful because it makes everything harder to read; a bigger haystack to find a needle (which may be not about nut) Specifical...

Thanks again, Great to see confirmations of more and more things working! > I wonder what's the fastest method to test the function (previously I setup the ups and unplug the utility from the ups for testing). > is "upsrw driver.flag.allow_killpower=1" then "upscmd driver.killpower" the correct testing procedure? At least by intent of this new feature -- yes. Normally the drivers are not allowed to pass these dangerous commands unless started specifically for killpower handling late in the system shutdown. Since NUT v2.8.1 howe...

Thanks again, Great to see confirmations of more and more things working! > I wonder what's the fastest method to test the function (previously I setup the ups and unplug the utility from the ups for testing). > is "upsrw driver.flag.allow_killpower=1" then "upscmd driver.killpower" the correct testing procedure? At least by intent of this new feature -- yes. Normally the drivers are not allowed to pass these dangerous commands unless started specifically for killpower handling late in the system shutdown. Since NUT v2.8.1 howe...

...s for both UPS(outlet.group.count: 2). but SMT2200RM2U has only one outlet group. since the new driver can not shutdown the ups, I wonder what's the fastest method to test the function (previously I setup the ups and unplug the utility from the ups for testing). is "upsrw driver.flag.allow_killpower=1" then "upscmd driver.killpower" the correct testing procedure? 5. the default/actual shutdown delay for both ups is 90 seconds(when real testing under apcupsd). the "upsrw -l myups" has value "90" for the attribute "outlet.group.1.delay.shutdown". but...

...s for both UPS(outlet.group.count: 2). but SMT2200RM2U has only one outlet group. since the new driver can not shutdown the ups, I wonder what's the fastest method to test the function (previously I setup the ups and unplug the utility from the ups for testing). is "upsrw driver.flag.allow_killpower=1" then "upscmd driver.killpower" the correct testing procedure? 5. the default/actual shutdown delay for both ups is 90 seconds(when real testing under apcupsd). the "upsrw -l myups" has value "90" for the attribute "outlet.group.1.delay.shutdown". but...