Yes Atreyu, I'm using the full path to shutdown commandQuote:
Are you using the full path to shutdown (i.e., /sbin/shutdown) in your SHUTDOWNCMD?
You are correct I should not use that "POWERDOWNFLAG "/sbin/shutdown -P +0" in the upsmon.conf file.
When I try the upsmon -c fsd with my current confuguration it gave the following output
After commenting the POWERDOWNFLAG "/sbin/shutdown -P +0" line and re-enabling the POWERDOWNFLAG /etc/ups/killpower line and executing upsmon -c fsd command, I was able to shutdown the server:)Code:[root@proxy ~]# upsmon -c fsd
Network UPS Tools upsmon 2.6.5
kill: No such process
but the five minute setting is the one that hard to achive:shock:Code:[root@proxy ups]# upsmon -c fsd
Network UPS Tools upsmon 2.6.5
[root@proxy ups]#
Broadcast message from nut@proxy.server (Wed Nov 14 17:49:52 2012):
UPS 3000@localhost: forced shutdown in progress
Broadcast message from nut@proxy.server (Wed Nov 14 17:50:04 2012):
Executing automatic power-fail shutdown
Broadcast message from nut@proxy.server (Wed Nov 14 17:50:04 2012):
Auto logout and shutdown proceeding
Broadcast message from nut@proxy.server (Wed Nov 14 17:50:08 2012):
Executing automatic power-fail shutdown
Broadcast message from nut@proxy.server (Wed Nov 14 17:50:08 2012):
Auto logout and shutdown proceeding
Broadcast message from root@proxy.server
(unknown) at 17:50 ...
The system is going down for power off NOW!
Broadcast message from root@proxy.server
(unknown) at 17:50 ...
The system is going down for power off NOW!
