joelones Posted August 24, 2015 Share Posted August 24, 2015 I trying to configure the following UPS CP1500PFCLCD to cleanly shutdown the server after 30 seconds on battery. unRAID recognizes the UPS and prompts me with notifications when I trip the UPS. Please see screens. But unfortunately the server remains on. I keep the UPS unplugged for a couple of minutes to see if it would shutdown the server, alas it does not. I then plugged it back in as you can see. Aug 24 18:58:52 petunia apcupsd[9359]: Power failure. Aug 24 18:58:58 petunia apcupsd[9359]: Running on UPS batteries. Aug 24 18:59:29 petunia apcupsd[9359]: Reached run time limit on batteries. Aug 24 18:59:29 petunia apcupsd[9359]: Initiating system shutdown! Aug 24 18:59:29 petunia apcupsd[9359]: User logins prohibited ... Aug 24 19:01:23 petunia apcupsd[9359]: Communications with UPS restored. Aug 24 19:01:23 petunia apcupsd[9359]: Mains returned. No longer on UPS batteries. Aug 24 19:01:23 petunia apcupsd[9359]: Power is back. UPS running on mains. Aug 24 19:01:23 petunia apcupsd[9359]: Allowing logins Aug 24 19:03:23 petunia emhttp: /usr/local/emhttp/webGui/scripts/tail_log syslog 2>&1 Screenshot of settings page: http://i.imgur.com/nMTwcw6.png When I look at /etc/apcupsd/apccontrol, it appears to do the timeout block but not the doshutdown block timeout) echo "Battery time limit exceeded on UPS ${2}. Doing shutdown." | ${WALL} ;; doshutdown) echo "UPS ${2} initiated Shutdown Sequence" | ${WALL} ${SHUTDOWN} -h now "apcupsd UPS ${2} initiated shutdown" ;; Plugins installed besides default: Dynamix S3 Sleep, Nerd Tools unRAID: 6.1-rc5 cat /var/log/apcupsd.events 2015-08-24 18:51:46 -0400 apcupsd 3.14.13 (02 February 2015) slackware startup succeeded 2015-08-24 18:52:16 -0400 apcupsd exiting, signal 15 2015-08-24 18:52:16 -0400 apcupsd shutdown succeeded 2015-08-24 18:52:16 -0400 apcupsd 3.14.13 (02 February 2015) slackware startup succeeded 2015-08-24 18:58:52 -0400 Power failure. 2015-08-24 18:58:58 -0400 Running on UPS batteries. 2015-08-24 18:59:29 -0400 Reached run time limit on batteries. 2015-08-24 18:59:29 -0400 Initiating system shutdown! 2015-08-24 18:59:29 -0400 User logins prohibited 2015-08-24 19:01:23 -0400 Communications with UPS restored. 2015-08-24 19:01:23 -0400 Mains returned. No longer on UPS batteries. 2015-08-24 19:01:23 -0400 Power is back. UPS running on mains. 2015-08-24 19:01:23 -0400 Allowing logins 2015-08-24 19:37:41 -0400 apcupsd exiting, signal 15 2015-08-24 19:37:41 -0400 apcupsd shutdown succeeded 2015-08-24 19:37:41 -0400 apcupsd 3.14.13 (02 February 2015) slackware startup succeeded 2015-08-24 19:38:26 -0400 apcupsd exiting, signal 15 2015-08-24 19:38:26 -0400 apcupsd shutdown succeeded 2015-08-24 19:38:26 -0400 apcupsd 3.14.13 (02 February 2015) slackware startup succeeded Missing something here... Thoughts? Link to comment
RobJ Posted August 25, 2015 Share Posted August 25, 2015 I wonder if this applies - Other changes (6.1-rc6) ----------------------- - apcupsd: fix regression: 'powerdown' script not invoked correctly Link to comment
joelones Posted August 25, 2015 Author Share Posted August 25, 2015 That could explain a lot, thanks for the heads up! Link to comment
otisk Posted September 5, 2015 Share Posted September 5, 2015 I just installed an ups and experience the exact same thing on 6.1 final. Is there already a solution for this? Link to comment
bonienl Posted September 5, 2015 Share Posted September 5, 2015 I just installed an ups and experience the exact same thing on 6.1 final. Is there already a solution for this? The regression error is fixed in v6.1 final. Link to comment
otisk Posted September 5, 2015 Share Posted September 5, 2015 I tried running the powerdown script in /usr/local/sbin manually through ssh but nothing happened either. shouldn't the server shutdown in this case? Link to comment
bonienl Posted September 6, 2015 Share Posted September 6, 2015 I tried running the powerdown script in /usr/local/sbin manually through ssh but nothing happened either. shouldn't the server shutdown in this case? Powerdown works properly in v6.1, it may take some minutes before the actual shutdown/reboot happens though. Link to comment
otisk Posted September 6, 2015 Share Posted September 6, 2015 I guess I found out why it does not work. I'm running the webGui on port 8008 because plexconnect needs port 80. The powerdown script states that it needs the webGui to be running on port 80. Link to comment
stealth82 Posted October 6, 2015 Share Posted October 6, 2015 It happened to me this morning. I was alerted that the server was running on battery. I had to turn it off manually because the battery/minutes went lower than the threshold and despite the fact that the UPS printed "SHUTTING DOWN" nothing happened. I'm running unRAID 6.1.3 Link to comment
stealth82 Posted November 11, 2015 Share Posted November 11, 2015 I guess I found out why it does not work. I'm running the webGui on port 8008 because plexconnect needs port 80. The powerdown script states that it needs the webGui to be running on port 80. Wait, I just realized it is my problem also. Why this limitation? Link to comment
bubbaQ Posted November 12, 2015 Share Posted November 12, 2015 Same here. I guess I found out why it does not work. I'm running the webGui on port 8008 because plexconnect needs port 80. The powerdown script states that it needs the webGui to be running on port 80. Wait, I just realized it is my problem also. Why this limitation? Link to comment
Frank1940 Posted November 12, 2015 Share Posted November 12, 2015 Have any of you folks tried the Powerdown package as developed in this thread? http://lime-technology.com/forum/index.php?topic=31735.0 It was designed to cure a lot of problem that the original script did not address. Be sure that you get the one for ver 6.0. Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.