Skip to content
View in the app

A better way to browse. Learn more.
Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.
Unraid Summer Sale in live: 20% off Starter and Unleashed + buy one, get one 50% off

[DEPRECATED] Apcupsd Plugin for V6

dlandon
in 6.0 (Unverified)

Featured Replies

  • Author

I 'upgraded' to this latest version of apcupsd (and hence powerdown) just yesterday (Sept 14).

 

Can you explain why a power cut on Sept 13 allowed a clean restart, yet the restart after a power cut today started running a parity check?

 

On both occasions unRAID v6.0beta9 was running.

 

Sep 13 09:40:54 Tower apcupsd[2078]: Power failure.
Sep 13 09:41:00 Tower apcupsd[2078]: Running on UPS batteries.
Sep 13 09:45:29 Tower sshd[6440]: Received disconnect from 10.2.1.15: 11: disconnected by user
Sep 13 09:45:29 Tower sshd[4563]: Received disconnect from 10.2.1.15: 11: disconnected by user
Sep 13 09:45:29 Tower sshd[4662]: Received disconnect from 10.2.1.15: 11: disconnected by user
Sep 13 09:46:01 Tower apcupsd[2078]: Reached run time limit on batteries.
Sep 13 09:46:01 Tower apcupsd[2078]: Initiating system shutdown!
Sep 13 09:46:01 Tower apcupsd[2078]: User logins prohibited
Sep 13 09:46:01 Tower powerdown[25032]: Powerdown initiated
Sep 13 09:46:01 Tower powerdown[25036]: Powerdown V2.06
Sep 13 09:46:01 Tower rc.unRAID[25038][25039]: Processing /etc/rc.d/rc.unRAID.d/ kill scripts.
Sep 13 09:46:01 Tower rc.unRAID[25038][25043]: Running: "/etc/rc.d/rc.unRAID.d/K00.sh"
Sep 13 09:46:01 Tower rc.unRAID[25038][25047]: Waiting for 0 domains
Sep 13 09:46:01 Tower powerdown[25049]: Initiating Shutdown with ''
Sep 13 09:46:01 Tower shutdown[25050]: shutting down for system halt
Sep 13 09:46:18 Tower init: Switching to runlevel: 0
Sep 13 09:46:20 Tower rc.unRAID[25235][25236]: Powerdown V2.06
Sep 13 09:46:20 Tower rc.unRAID[25235][25237]: Stopping Plugins.
Sep 13 09:46:20 Tower rc.unRAID[25235][25245]: Running: "/etc/rc.d/rc.docker stop"
Sep 13 09:46:20 Tower rc.unRAID[25235][25248]: stopping docker ...
Sep 13 09:46:21 Tower rc.unRAID[25235][25248]: 68d53a8c9096
Sep 13 09:46:22 Tower rc.unRAID[25235][25248]: 4b32e542da76
Sep 13 09:46:23 Tower rc.unRAID[25235][25248]: unmounting docker loopback
Sep 13 09:46:26 Tower rc.unRAID[25235][25359]: Running: "/etc/rc.d/rc.dovecot stop"
Sep 13 09:46:26 Tower rc.unRAID[25235][25362]: Stopping dovecot...
Sep 13 09:46:26 Tower rc.unRAID[25235][25366]: Running: "/etc/rc.d/rc.fan_speed stop"
Sep 13 09:46:26 Tower rc.fan_speed: WARNING: fan_speed called to stop with SERVICE not = disabled
Sep 13 09:46:26 Tower rc.unRAID[25235][25377]: Running: "/etc/rc.d/rc.mpop stop"
Sep 13 09:46:26 Tower rc.unRAID[25235][25380]: usage /etc/rc.d/rc.mpop start|stop|enable|disable|reload
Sep 13 09:46:26 Tower rc.unRAID[25235][25381]: Running: "/etc/rc.d/rc.rsyslogd stop"
Sep 13 09:46:26 Tower rsyslogd: [origin software="rsyslogd" swVersion="8.4.0" x-pid="1180" x-info="http://www.rsyslog.com"] exiting on signal 15.

 

Sep 15 10:50:52 Tower apcupsd[30011]: Power failure.
Sep 15 10:50:58 Tower apcupsd[30011]: Running on UPS batteries.
Sep 15 10:51:14 Tower fan_speed.sh: Highest disk drive temp is: 40C
Sep 15 10:51:14 Tower fan_speed.sh: Changing disk drive fan speed from: [144 (56% @ 1573 rpm) ] to: [180 (70% @ 1856 rpm) ]
Sep 15 10:51:49 Tower emhttp: shcmd (485): /usr/sbin/hdparm -y /dev/sdd &> /dev/null
Sep 15 10:55:48 Tower sshd[13916]: Received disconnect from 10.2.1.15: 11: disconnected by user
Sep 15 10:55:48 Tower sshd[4966]: Received disconnect from 10.2.1.15: 11: disconnected by user
Sep 15 10:55:48 Tower sshd[24977]: Received disconnect from 10.2.1.15: 11: disconnected by user
Sep 15 10:55:59 Tower apcupsd[30011]: Reached run time limit on batteries.
Sep 15 10:55:59 Tower apcupsd[30011]: Initiating system shutdown!
Sep 15 10:55:59 Tower apcupsd[30011]: User logins prohibited
Sep 15 10:55:59 Tower powerdown[23614]: Powerdown initiated
Sep 15 10:55:59 Tower powerdown[23626]: Powerdown V2.07
Sep 15 10:55:59 Tower rc.unRAID[23632][23633]: Processing /etc/rc.d/rc.unRAID.d/ kill scripts.
Sep 15 10:55:59 Tower rc.unRAID[23632][23637]: Running: "/etc/rc.d/rc.unRAID.d/K00.sh"
Sep 15 10:55:59 Tower rc.unRAID[23632][23640]: Shutting down domain 8
Sep 15 10:55:59 Tower rc.unRAID[23632][23640]: Waiting for 1 domains
Sep 15 10:55:59 Tower rpc.mountd[25157]: authenticated unmount request from 10.2.0.104:982 for /mnt/user/mysql (/mnt/user/mysql)
Sep 15 10:55:59 Tower rpc.mountd[25157]: authenticated unmount request from 10.2.0.104:983 for /mnt/user/Photos (/mnt/user/Photos)
Sep 15 10:56:04 Tower kernel: br0: port 2(vif8.0) entered disabled state
Sep 15 10:56:04 Tower rc.unRAID[23632][23640]: Domain 8 has been shut down, reason code 0
Sep 15 10:56:04 Tower powerdown[23766]: Initiating Shutdown with ''
Sep 15 10:56:04 Tower avahi-daemon[24008]: Withdrawing workstation service for vif8.0.
Sep 15 10:56:04 Tower shutdown[23767]: shutting down for system halt
Sep 15 10:56:04 Tower kernel: br0: port 2(vif8.0) entered disabled state
Sep 15 10:56:04 Tower kernel: device vif8.0 left promiscuous mode
Sep 15 10:56:04 Tower kernel: br0: port 2(vif8.0) entered disabled state
Sep 15 10:56:04 Tower logger: /etc/xen/scripts/vif-bridge: offline type_if=vif XENBUS_PATH=backend/vif/8/0
Sep 15 10:56:04 Tower logger: /etc/xen/scripts/vif-bridge: brctl delif br0 vif8.0 failed
Sep 15 10:56:04 Tower logger: /etc/xen/scripts/vif-bridge: ifconfig vif8.0 down failed
Sep 15 10:56:04 Tower logger: /etc/xen/scripts/vif-bridge: Successful vif-bridge offline for vif8.0, bridge br0.
Sep 15 10:56:05 Tower init: Switching to runlevel: 0
Sep 15 10:56:07 Tower rc.unRAID[23911][23912]: Powerdown V2.07
Sep 15 10:56:07 Tower rc.unRAID[23911][23913]: Stopping Plugins.
Sep 15 10:56:07 Tower rc.unRAID[23911][23921]: Running: "/etc/rc.d/rc.apcupsd.new stop"
Sep 15 10:56:07 Tower apcupsd[30011]: apcupsd exiting, signal 15
Sep 15 10:56:07 Tower apcupsd[30011]: apcupsd shutdown succeeded
Sep 15 10:56:07 Tower rc.unRAID[23911][23924]: Stopping apcupsd power management..  Done.
Sep 15 10:56:07 Tower rc.unRAID[23911][23928]: Running: "/etc/rc.d/rc.dovecot stop"
Sep 15 10:56:07 Tower rc.unRAID[23911][23931]: Stopping dovecot...
Sep 15 10:56:07 Tower rc.unRAID[23911][23933]: Running: "/etc/rc.d/rc.fan_speed stop"
Sep 15 10:56:07 Tower rc.fan_speed: WARNING: fan_speed called to stop with SERVICE not = disabled
Sep 15 10:56:07 Tower rc.unRAID[23911][23944]: Running: "/etc/rc.d/rc.mpop stop"
Sep 15 10:56:07 Tower rc.unRAID[23911][23947]: usage /etc/rc.d/rc.mpop start|stop|enable|disable|reload
Sep 15 10:56:07 Tower rc.unRAID[23911][23948]: Running: "/etc/rc.d/rc.rsyslogd stop"
Sep 15 10:56:07 Tower rsyslogd: [origin software="rsyslogd" swVersion="8.4.0" x-pid="1186" x-info="http://www.rsyslog.com"] exiting on signal 15.

 

I'm a little wary of this since we experience an average of 2 power cuts a day (except Sundays!).  The last parity check was performed manually, after 45 days with no parity check, so the old apcupsd/powerdown has been very reliable.

 

Should I revert to powerdown v2.06, or might this be some quirk in the session during which the upgrade was performed?

 

I see a couple of problems.

 

This is probably the reason for the unclean shutdown.  rc.mpop did not accept the stop command.

Sep 15 10:56:07 Tower rc.unRAID[23911][23944]: Running: "/etc/rc.d/rc.mpop stop"

Sep 15 10:56:07 Tower rc.unRAID[23911][23947]: usage /etc/rc.d/rc.mpop start|stop|enable|disable|reload

 

The other problem I see is that powerdown is stopping logging and shouldn't.  LT changed the logging daemon.  I'll fix that.

 

  • Replies 203
  • Views 28.6k
  • Created
  • Last Reply
  • Author

In investigating further, I found that unRAID is not stopping docker on a shutdown that is done outside the webgui - i.e. push the power button.  This can lead to an unclean shutdown.  Powerdown does not shutdown docker.  That is up to unRAID.

In investigating further, I found that unRAID is not stopping docker on a shutdown that is done outside the webgui - i.e. push the power button.  This can lead to an unclean shutdown.  Powerdown does not shutdown docker.  That is up to unRAID.

 

How come it all worked perfectly on Saturday 13th?  Exactly the same setup ... same version of unRAID, same two dockers, same Xen ArchVM and same plugins .... except for the 'upgraded' apcupsd and powerdown.

This is probably the reason for the unclean shutdown.  rc.mpop did not accept the stop command.

Sep 15 10:56:07 Tower rc.unRAID[23911][23944]: Running: "/etc/rc.d/rc.mpop stop"

Sep 15 10:56:07 Tower rc.unRAID[23911][23947]: usage /etc/rc.d/rc.mpop start|stop|enable|disable|reload

 

Okay, thanks for pointing that out.  I have fixed the .plg, but it was inconsequential - all that it was meant to do was to remove an entry from crontab.

 

I can assure you that the plugin has been running like that for a couple of years and has never caused a problem.

 

The other problem I see is that powerdown is stopping logging and shouldn't.  LT changed the logging daemon.  I'll fix that.

 

Okay, thanks.  I'd been puzzled by the new messages relating to the syslog daemon.

  • Author

In investigating further, I found that unRAID is not stopping docker on a shutdown that is done outside the webgui - i.e. push the power button.  This can lead to an unclean shutdown.  Powerdown does not shutdown docker.  That is up to unRAID.

 

How come it all worked perfectly on Saturday 13th?  Exactly the same setup ... same version of unRAID, same two dockers, same Xen ArchVM and same plugins .... except for the 'upgraded' apcupsd and powerdown.

 

Don't know, but I suspect that docker was not in the way then.  The changes in powerdown 2.07 were relatively minor.

Another spectacular failure of the current apcupsd/powerdown combination:

Sep 17 03:16:27 Tower apcupsd[11170]: Power failure.
Sep 17 03:16:33 Tower apcupsd[11170]: Running on UPS batteries.
Sep 17 03:18:58 Tower fan_speed.sh: Highest disk drive temp is: 38C
Sep 17 03:18:58 Tower fan_speed.sh: Changing disk drive fan speed from: [144 (56% @ 1603 rpm) ] to: [108 (42% @ 1241 rpm) ]
Sep 17 03:20:57 Tower sshd[3965]: Received disconnect from 10.2.1.15: 11: disconnected by user
Sep 17 03:21:34 Tower apcupsd[11170]: Reached run time limit on batteries.
Sep 17 03:21:34 Tower apcupsd[11170]: Initiating system shutdown!
Sep 17 03:21:34 Tower apcupsd[11170]: User logins prohibited
Sep 17 03:23:12 Tower fan_speed.sh: Highest disk drive temp is: 39C
Sep 17 03:23:12 Tower fan_speed.sh: Changing disk drive fan speed from: [108 (42% @ 1239 rpm) ] to: [144 (56% @ 1599 rpm) ]
Sep 17 03:25:21 Tower fan_speed.sh: Highest disk drive temp is: 38C
Sep 17 03:25:21 Tower fan_speed.sh: Changing disk drive fan speed from: [144 (56% @ 1605 rpm) ] to: [108 (42% @ 1245 rpm) ]
Sep 17 03:28:32 Tower fan_speed.sh: Highest disk drive temp is: 39C
Sep 17 03:28:32 Tower fan_speed.sh: Changing disk drive fan speed from: [108 (42% @ 1239 rpm) ] to: [144 (56% @ 1597 rpm) ]
Sep 17 03:31:28 Tower kernel: mdcmd (24): spindown 2
Sep 17 03:31:44 Tower fan_speed.sh: Highest disk drive temp is: 38C
Sep 17 03:31:44 Tower fan_speed.sh: Changing disk drive fan speed from: [144 (56% @ 1603 rpm) ] to: [108 (42% @ 1241 rpm) ]
Sep 17 03:32:16 Tower apcupsd[11170]: Mains returned. No longer on UPS batteries.
Sep 17 03:32:16 Tower apcupsd[11170]: Power is back. UPS running on mains.
Sep 17 03:32:16 Tower apcupsd[11170]: Allowing logins

 

Luckily power returned before the UPS battery was exhausted.  I couldn't start the generator at 3.20am - the neighbours would have become more than a little annoyed.

 

 

Here's the plugin installation:

Sep 16 19:27:29 Tower logger: Installing user plugins
Sep 16 19:27:29 Tower logger: plugin: installing: /boot/config/plugins/AWindowTitle.plg
Sep 16 19:27:29 Tower logger: plugin: creating: /tmp/WindowTitle.sh - from INLINE content
Sep 16 19:27:29 Tower logger: plugin: setting: /tmp/WindowTitle.sh - mode to 0770
Sep 16 19:27:29 Tower logger: plugin: running: /tmp/WindowTitle.sh
Sep 16 19:27:29 Tower logger: plugin: installed
Sep 16 19:27:29 Tower logger: plugin: installing: /boot/config/plugins/Apcupsd-x86_64.plg
Sep 16 19:27:29 Tower logger: plugin: skipping: /boot/packages/apcupsd-3.14.12-x86_64-4.tgz already exists
Sep 16 19:27:29 Tower logger: plugin: running: /boot/packages/apcupsd-3.14.12-x86_64-4.tgz
Sep 16 19:27:29 Tower kernel: e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
Sep 16 19:27:29 Tower kernel: br0: port 1(eth0) entered listening state
Sep 16 19:27:29 Tower kernel: br0: port 1(eth0) entered listening state
Sep 16 19:27:29 Tower logger: 
Sep 16 19:27:29 Tower logger: +==============================================================================
Sep 16 19:27:29 Tower logger: | Installing new package /boot/packages/apcupsd-3.14.12-x86_64-4.tgz
Sep 16 19:27:29 Tower logger: +==============================================================================
Sep 16 19:27:29 Tower logger: 
Sep 16 19:27:30 Tower logger: Verifying package apcupsd-3.14.12-x86_64-4.tgz.
Sep 16 19:27:30 Tower logger: Installing package apcupsd-3.14.12-x86_64-4.tgz:
Sep 16 19:27:30 Tower logger: PACKAGE DESCRIPTION:
Sep 16 19:27:30 Tower logger: # apcupsd (APC UPS Daemon)
Sep 16 19:27:30 Tower logger: #
Sep 16 19:27:30 Tower logger: # Apcupsd can be used for power mangement and controlling most of APC's
Sep 16 19:27:30 Tower logger: # UPS models on Unix and Windows machines. Apcupsd works with most of
Sep 16 19:27:30 Tower logger: # APC's Smart-UPS models as well as most simple signalling models such
Sep 16 19:27:30 Tower logger: # as Back-UPS, and BackUPS-Office.
Sep 16 19:27:30 Tower logger: #
Sep 16 19:27:30 Tower logger: # See /usr/doc/apcupsd-3.14.12/README.SLACKWARE
Sep 16 19:27:30 Tower logger: #
Sep 16 19:27:30 Tower logger: Executing install script for apcupsd-3.14.12-x86_64-4.tgz.
Sep 16 19:27:30 Tower logger: Package apcupsd-3.14.12-x86_64-4.tgz installed.
Sep 16 19:27:30 Tower logger: 
Sep 16 19:27:30 Tower logger: 
Sep 16 19:27:30 Tower logger: plugin: skipping: /boot/config/plugins/powerdown-x86_64.plg already exists
Sep 16 19:27:30 Tower logger: plugin: skipping: /boot/config/plugins/apcupsd/apcupsd.png already exists
Sep 16 19:27:30 Tower logger: plugin: skipping: /boot/config/plugins/apcupsd/apcupsd.cfg already exists
Sep 16 19:27:30 Tower logger: plugin: creating: /usr/local/emhttp/plugins/apcupsd/apcupsd.png - copying LOCAL file /boot/config/plugins/apcupsd/apcupsd.png
Sep 16 19:27:30 Tower logger: plugin: creating: /usr/local/emhttp/plugins/apcupsd/Apcupsd.page - from INLINE content
Sep 16 19:27:30 Tower logger: plugin: creating: /usr/local/emhttp/plugins/apcupsd/Apcupsd.php - from INLINE content
Sep 16 19:27:30 Tower logger: plugin: creating: /usr/local/emhttp/plugins/apcupsd/apcupsdctl.php - from INLINE content
Sep 16 19:27:30 Tower logger: plugin: creating: /usr/local/emhttp/plugins/apcupsd/README.md - from INLINE content
Sep 16 19:27:30 Tower logger: plugin: creating: /tmp/apcupsd-install - from INLINE content
Sep 16 19:27:30 Tower logger: plugin: running: /tmp/apcupsd-install
Sep 16 19:27:30 Tower logger: Saving Settings...Completed
Sep 16 19:27:30 Tower logger: #015 Applying Settings...Completed
Sep 16 19:27:30 Tower apcupsd[1819]: apcupsd 3.14.12 (29 March 2014) slackware startup succeeded
Sep 16 19:27:30 Tower apcupsd[1819]: NIS server startup succeeded
Sep 16 19:27:34 Tower apcupsd[1819]: Power failure.
Sep 16 19:27:35 Tower logger: #015Starting apcupsd...Completed
Sep 16 19:27:35 Tower logger: #015plugin: installing: /boot/config/plugins/powerdown-x86_64.plg
Sep 16 19:27:35 Tower logger: plugin: skipping: /boot/packages/powerdown-2.08-noarch-unRAID.tgz already exists
Sep 16 19:27:35 Tower logger: plugin: running: /boot/packages/powerdown-2.08-noarch-unRAID.tgz
Sep 16 19:27:35 Tower logger: 
Sep 16 19:27:35 Tower logger: +==============================================================================
Sep 16 19:27:35 Tower logger: | Installing new package /boot/packages/powerdown-2.08-noarch-unRAID.tgz
Sep 16 19:27:35 Tower logger: +==============================================================================
Sep 16 19:27:35 Tower logger: 
Sep 16 19:27:35 Tower logger: Verifying package powerdown-2.08-noarch-unRAID.tgz.
Sep 16 19:27:35 Tower logger: Installing package powerdown-2.08-noarch-unRAID.tgz:
Sep 16 19:27:35 Tower logger: PACKAGE DESCRIPTION:
Sep 16 19:27:35 Tower logger: #
Sep 16 19:27:35 Tower logger: # powerdown  Control scripts for the unRAID server Environment.
Sep 16 19:27:35 Tower logger: #
Sep 16 19:27:35 Tower logger: # Copyright (C) 2008-2014 by Robert Cotrone & Dan Landon
Sep 16 19:27:35 Tower logger: #
Sep 16 19:27:35 Tower logger: # Adds /sbin/powerdown script to assist with quick unRAID poweroff
Sep 16 19:27:35 Tower logger: #
Sep 16 19:27:35 Tower logger: # Install Variable options:
Sep 16 19:27:35 Tower logger: # CTRLALTDEL=yes set ctrl-alt-del to do powerdown instead of reboot
Sep 16 19:27:35 Tower logger: # SYSLOG=YES     do initial syslog saving upon installation
Sep 16 19:27:35 Tower logger: # STATUS=YES     Show status upon installation
Sep 16 19:27:35 Tower logger: # START=YES      do initial start upon installation
Sep 16 19:27:35 Tower logger: # 
Sep 16 19:27:35 Tower logger: # Install with VAR's as defined above like:
Sep 16 19:27:35 Tower logger: # VAR=YES OTHERVAR=YES installpkg powerdown-2.08-noarch-unRAID.tgz
Sep 16 19:27:35 Tower logger: # Like Like: 
Sep 16 19:27:35 Tower logger: # CTRLALTDEL=yes installpkg powerdown-2.08-noarch-unRAID.tgz
Sep 16 19:27:35 Tower logger: # 
Sep 16 19:27:35 Tower logger: # /etc/rc.d/rc.unRAID script has basic pre-power down functions
Sep 16 19:27:35 Tower logger: # Hooks are placed in /etc/rc.d/rc.local_shutdown
Sep 16 19:27:35 Tower logger: # to allow normal poweroff/shutdown commands do a graceful shutdown
Sep 16 19:27:35 Tower logger: # 
Sep 16 19:27:35 Tower logger: # Diagnostic mode for quick syslog dump/save to /boot/logs
Sep 16 19:27:35 Tower logger: # call as /etc/rc.d/ec.unRAID diag
Sep 16 19:27:35 Tower logger: # call as /etc/rc.d/rc.unRAID syslog 
Sep 16 19:27:35 Tower logger: #
Sep 16 19:27:35 Tower logger: Executing install script for powerdown-2.08-noarch-unRAID.tgz.
Sep 16 19:27:35 Tower init: Re-reading inittab
Sep 16 19:27:35 Tower logger: kernel.poweroff_cmd = /sbin/powerdown
Sep 16 19:27:35 Tower logger: Package powerdown-2.08-noarch-unRAID.tgz installed.
Sep 16 19:27:35 Tower logger: 
Sep 16 19:27:35 Tower logger: 
Sep 16 19:27:35 Tower logger: plugin: skipping: /boot/config/plugins/powerdown/powerdown.png already exists
Sep 16 19:27:35 Tower logger: plugin: creating: /usr/local/emhttp/plugins/powerdown/powerdown.png - copying LOCAL file /boot/config/plugins/powerdown/powerdown.png
Sep 16 19:27:35 Tower logger: plugin: running: 'anonymous'
Sep 16 19:27:35 Tower logger: 
Sep 16 19:27:35 Tower logger: Removing package /var/log/packages/powerdown-2.08-noarch-unRAID...
Sep 16 19:27:35 Tower logger: Removing files:
Sep 16 19:27:35 Tower logger:   --> Deleting /etc/rc.d/rc.unRAID
Sep 16 19:27:35 Tower logger:   --> Deleting /etc/rc.d/rcdstock
Sep 16 19:27:35 Tower logger:   --> Deleting /sbin/powerdown
Sep 16 19:27:35 Tower logger:   --> Deleting /usr/doc/powerdown-2.08/powerdown.SlackBuild
Sep 16 19:27:35 Tower logger:   --> Deleting /usr/doc/powerdown-2.08/slack-desc
Sep 16 19:27:35 Tower logger:   --> Deleting empty directory /usr/doc/powerdown-2.08/
Sep 16 19:27:35 Tower logger: WARNING: Unique directory /etc/rc.d/rc.unRAID.d/ contains new files
Sep 16 19:27:35 Tower logger: plugin: creating: /usr/local/emhttp/plugins/powerdown/README.md - from INLINE content

 

My desktop machine, which is slaved to the unRAID apcupsd, did shutdown correctly.

  • Author

The powerdown package was removed during installation.  I think you caught me in the middle of making a few adjustments to the plugin and it was not finished yet.

 

Remove powerdown, re-install it and post a log of the installation so I can confirm it installed properly.

The powerdown package was removed during installation.  I think you caught me in the middle of making a few adjustments to the plugin and it was not finished yet.

 

Remove powerdown, re-install it and post a log of the installation so I can confirm it installed properly.

 

Okay, I removed powerdown and upgraded apcupsd, which re-added powerdown, but all that appears in the log is:

Sep 17 07:31:03 Tower apcupsd[14365]: apcupsd exiting, signal 15
Sep 17 07:31:03 Tower apcupsd[14365]: apcupsd shutdown succeeded
Sep 17 07:31:03 Tower apcupsd[15417]: apcupsd 3.14.12 (29 March 2014) slackware startup succeeded
Sep 17 07:31:03 Tower apcupsd[15417]: NIS server startup succeeded
Sep 17 07:31:10 Tower init: Re-reading inittab

 

Is it necessary to reboot in order to complete the upgrade?

  • Author

The powerdown package was removed during installation.  I think you caught me in the middle of making a few adjustments Remove powerdown, re-install it and post a log of the installation so I can confirm it installed properly.

to the plugin and it was not finished yet.

 

 

Okay, I removed powerdown and upgraded apcupsd, which re-added powerdown, but all that appears in the log is:

Sep 17 07:31:03 Tower apcupsd[14365]: apcupsd exiting, signal 15
Sep 17 07:31:03 Tower apcupsd[14365]: apcupsd shutdown succeeded
Sep 17 07:31:03 Tower apcupsd[15417]: apcupsd 3.14.12 (29 March 2014) slackware startup succeeded
Sep 17 07:31:03 Tower apcupsd[15417]: NIS server startup succeeded
Sep 17 07:31:10 Tower init: Re-reading inittab

 

Is it necessary to reboot in order to complete the upgrade?

 

I think when a plugin is updated, all the messages from the update are directed to the lower line of the plugin manager web page.  I don't think they are logged like when installing from a re-boot.  It's not necessary to reboot.

 

Does the powerdown show up in the plugin manager web page?  If it does, then powerdown should be installed.

 

EDIT: A quick check to see if it is installed is to go to a telnet or console and ls /etc/rc.d/rc.unRAID.  If it shows the script file, the package is installed.

I think when a plugin is updated, all the messages from the update are directed to the lower line of the plugin manager web page.  I don't think they are logged like when installing from a re-boot.  It's not necessary to reboot.

 

Ah, okay.  These pages are becoming so long that, even on a large screen it's necessary to scroll ... trouble is that I don't always think to do that!

 

Does the powerdown show up in the plugin manager web page?  If it does, then powerdown should be installed.

 

Yes, both apcupsd and powerdown are showing as 2014.09.15.  However, powerdown was showing before, but you say that the installation was incomplete.

 

EDIT: A quick check to see if it is installed is to go to a telnet or console and ls /etc/rc.d/rc.unRAID.  If it shows the script file, the package is installed.

 

Yes, rc.unRAID exists and starts with VERSION="2.08".

 

Hopefully, this will work a little better on the next powercut.

 

Actually, the failure during the night was a blessing in disguise - the system was about 9 hours through the parity correction after the previous powercut (1551 corrections!).

 

This is one of my problems here ... having sufficient continuous power in order to complete parity operations, and why safe shutdown is so important to me!

  • Author

I was having a bit of trouble trying to get the update for powerdown to work.  It's very hard to test a plugin update without involving the repository.  I had several attempts at updating powerdown on the GitHub repository for a very short period.  One of them I did a stupid thing and had a removepkg when updating.  That was not necessary, and in fact was a bad thing to do.  Anyway, I think you happened to catch the update for powerdown at the time my bad code was on GitHub.

 

The reason the powerdown did not work for you was that the package had been removed right after being installed, so the default powerdown was initiated.

Anyway, I think you happened to catch the update for powerdown at the time my bad code was on GitHub.

 

The reason the powerdown did not work for you was that the package had been removed right after being installed, so the default powerdown was initiated.

 

Okay, thanks for the explanation  ... I'll let you off, just this once!  :P

 

Anyway, I've just rebooted and this is in the logfile:

Sep 17 09:41:54 Tower logger: plugin: installing: /boot/config/plugins/Apcupsd-x86_64.plg
Sep 17 09:41:54 Tower logger: plugin: running: 'anonymous'
Sep 17 09:41:54 Tower logger: plugin: skipping: /boot/packages/apcupsd-3.14.12-x86_64-4.tgz already exists
Sep 17 09:41:54 Tower logger: plugin: running: /boot/packages/apcupsd-3.14.12-x86_64-4.tgz
Sep 17 09:41:54 Tower logger: 
Sep 17 09:41:54 Tower logger: +==============================================================================
Sep 17 09:41:54 Tower logger: | Installing new package /boot/packages/apcupsd-3.14.12-x86_64-4.tgz
Sep 17 09:41:54 Tower logger: +==============================================================================
Sep 17 09:41:54 Tower logger: 
Sep 17 09:41:54 Tower logger: Verifying package apcupsd-3.14.12-x86_64-4.tgz.
Sep 17 09:41:55 Tower logger: Installing package apcupsd-3.14.12-x86_64-4.tgz:
Sep 17 09:41:55 Tower logger: PACKAGE DESCRIPTION:
Sep 17 09:41:55 Tower logger: # apcupsd (APC UPS Daemon)
Sep 17 09:41:55 Tower logger: #
Sep 17 09:41:55 Tower logger: # Apcupsd can be used for power mangement and controlling most of APC's
Sep 17 09:41:55 Tower logger: # UPS models on Unix and Windows machines. Apcupsd works with most of
Sep 17 09:41:55 Tower logger: # APC's Smart-UPS models as well as most simple signalling models such
Sep 17 09:41:55 Tower logger: # as Back-UPS, and BackUPS-Office.
Sep 17 09:41:55 Tower logger: #
Sep 17 09:41:55 Tower logger: # See /usr/doc/apcupsd-3.14.12/README.SLACKWARE
Sep 17 09:41:55 Tower logger: #
Sep 17 09:41:55 Tower logger: Executing install script for apcupsd-3.14.12-x86_64-4.tgz.
Sep 17 09:41:55 Tower logger: Package apcupsd-3.14.12-x86_64-4.tgz installed.
Sep 17 09:41:55 Tower logger: 
Sep 17 09:41:55 Tower logger: 
Sep 17 09:41:55 Tower logger: plugin: skipping: /boot/config/plugins/powerdown-x86_64.plg already exists
Sep 17 09:41:55 Tower logger: plugin: skipping: /boot/config/plugins/apcupsd/apcupsd.png already exists
Sep 17 09:41:55 Tower logger: plugin: skipping: /boot/config/plugins/apcupsd/apcupsd.cfg already exists
Sep 17 09:41:55 Tower logger: plugin: creating: /usr/local/emhttp/plugins/apcupsd/apcupsd.png - copying LOCAL file /boot/config/plugins/apcupsd/apcupsd.png
Sep 17 09:41:55 Tower logger: plugin: creating: /usr/local/emhttp/plugins/apcupsd/Apcupsd.page - from INLINE content
Sep 17 09:41:55 Tower logger: plugin: creating: /usr/local/emhttp/plugins/apcupsd/Apcupsd.php - from INLINE content
Sep 17 09:41:55 Tower logger: plugin: creating: /usr/local/emhttp/plugins/apcupsd/apcupsdctl.php - from INLINE content
Sep 17 09:41:55 Tower logger: plugin: creating: /usr/local/emhttp/plugins/apcupsd/README.md - from INLINE content
Sep 17 09:41:55 Tower logger: plugin: creating: /tmp/apcupsd-install - from INLINE content
Sep 17 09:41:55 Tower logger: plugin: running: /tmp/apcupsd-install
Sep 17 09:41:55 Tower logger: Saving Settings...Completed
Sep 17 09:41:55 Tower logger: #015 Applying Settings...Completed
Sep 17 09:41:55 Tower apcupsd[1863]: apcupsd 3.14.12 (29 March 2014) slackware startup succeeded
Sep 17 09:41:55 Tower apcupsd[1863]: NIS server startup succeeded
Sep 17 09:42:00 Tower logger: #015Starting apcupsd...Completed
Sep 17 09:42:00 Tower logger: #015plugin: installing: /boot/config/plugins/powerdown-x86_64.plg
Sep 17 09:42:00 Tower logger: plugin: running: 'anonymous'
Sep 17 09:42:00 Tower logger: plugin: skipping: /boot/packages/powerdown-2.08-noarch-unRAID.tgz already exists
Sep 17 09:42:00 Tower logger: plugin: running: /boot/packages/powerdown-2.08-noarch-unRAID.tgz
Sep 17 09:42:00 Tower logger: 
Sep 17 09:42:00 Tower logger: +==============================================================================
Sep 17 09:42:00 Tower logger: | Installing new package /boot/packages/powerdown-2.08-noarch-unRAID.tgz
Sep 17 09:42:00 Tower logger: +==============================================================================
Sep 17 09:42:00 Tower logger: 
Sep 17 09:42:00 Tower logger: Verifying package powerdown-2.08-noarch-unRAID.tgz.
Sep 17 09:42:00 Tower logger: Installing package powerdown-2.08-noarch-unRAID.tgz:
Sep 17 09:42:00 Tower logger: PACKAGE DESCRIPTION:
Sep 17 09:42:00 Tower logger: #
Sep 17 09:42:00 Tower logger: # powerdown  Control scripts for the unRAID server Environment.
Sep 17 09:42:00 Tower logger: #
Sep 17 09:42:00 Tower logger: # Copyright (C) 2008-2014 by Robert Cotrone & Dan Landon
Sep 17 09:42:00 Tower logger: #
Sep 17 09:42:00 Tower logger: # Adds /sbin/powerdown script to assist with quick unRAID poweroff
Sep 17 09:42:00 Tower logger: #
Sep 17 09:42:00 Tower logger: # Install Variable options:
Sep 17 09:42:00 Tower logger: # CTRLALTDEL=yes set ctrl-alt-del to do powerdown instead of reboot
Sep 17 09:42:00 Tower logger: # SYSLOG=YES     do initial syslog saving upon installation
Sep 17 09:42:00 Tower logger: # STATUS=YES     Show status upon installation
Sep 17 09:42:00 Tower logger: # START=YES      do initial start upon installation
Sep 17 09:42:00 Tower logger: # 
Sep 17 09:42:00 Tower logger: # Install with VAR's as defined above like:
Sep 17 09:42:00 Tower logger: # VAR=YES OTHERVAR=YES installpkg powerdown-2.08-noarch-unRAID.tgz
Sep 17 09:42:00 Tower logger: # Like Like: 
Sep 17 09:42:00 Tower logger: # CTRLALTDEL=yes installpkg powerdown-2.08-noarch-unRAID.tgz
Sep 17 09:42:00 Tower logger: # 
Sep 17 09:42:00 Tower logger: # /etc/rc.d/rc.unRAID script has basic pre-power down functions
Sep 17 09:42:00 Tower logger: # Hooks are placed in /etc/rc.d/rc.local_shutdown
Sep 17 09:42:00 Tower logger: # to allow normal poweroff/shutdown commands do a graceful shutdown
Sep 17 09:42:00 Tower logger: # 
Sep 17 09:42:00 Tower logger: # Diagnostic mode for quick syslog dump/save to /boot/logs
Sep 17 09:42:00 Tower logger: # call as /etc/rc.d/ec.unRAID diag
Sep 17 09:42:00 Tower logger: # call as /etc/rc.d/rc.unRAID syslog 
Sep 17 09:42:00 Tower logger: #
Sep 17 09:42:00 Tower logger: Executing install script for powerdown-2.08-noarch-unRAID.tgz.
Sep 17 09:42:00 Tower init: Re-reading inittab
Sep 17 09:42:00 Tower logger: kernel.poweroff_cmd = /sbin/powerdown
Sep 17 09:42:00 Tower logger: Package powerdown-2.08-noarch-unRAID.tgz installed.
Sep 17 09:42:00 Tower logger: 
Sep 17 09:42:00 Tower logger: 
Sep 17 09:42:00 Tower logger: plugin: skipping: /boot/config/plugins/powerdown/powerdown.png already exists
Sep 17 09:42:00 Tower logger: plugin: creating: /usr/local/emhttp/plugins/powerdown/powerdown.png - copying LOCAL file /boot/config/plugins/powerdown/powerdown.png
Sep 17 09:42:00 Tower logger: plugin: creating: /usr/local/emhttp/plugins/powerdown/README.md - from INLINE content
Sep 17 09:42:00 Tower logger: plugin: installed
Sep 17 09:42:00 Tower logger: plugin: installed

 

Hopefully that all looks good now?

Well, after a power cut this morning:

Parity-Check in progress. 		Cancel will stop the Parity-Check.
Write corrections to parity disk
Total size: 	3 TB 	
Current position: 	2.02 TB (67.5 %) 	
Estimated speed: 	108.4 MB/sec 	
Estimated finish: 	2 hours, 30 minutes 	
Sync errors corrected: 	122977

 

Yes, almost 123,000 parity errors!

 

The machine powered down as expected, and the UPS switched off, but when power returned an automatic parity check was started.

 

Syslog extract:

Sep 20 06:33:18 Tower apcupsd[1863]: Power failure.
Sep 20 06:33:18 Tower apcupsd[1863]: Power is back. UPS running on mains.
Sep 20 06:33:19 Tower apcupsd[1863]: Power failure.
Sep 20 06:33:19 Tower apcupsd[1863]: Power is back. UPS running on mains.
Sep 20 06:33:19 Tower apcupsd[1863]: Power failure.
Sep 20 06:33:19 Tower apcupsd[1863]: Power is back. UPS running on mains.
Sep 20 06:33:20 Tower apcupsd[1863]: Power failure.
Sep 20 06:33:20 Tower apcupsd[1863]: Power is back. UPS running on mains.
Sep 20 06:33:21 Tower apcupsd[1863]: Power failure.
Sep 20 06:33:21 Tower apcupsd[1863]: Power is back. UPS running on mains.
Sep 20 06:33:21 Tower apcupsd[1863]: Power failure.
Sep 20 06:33:21 Tower apcupsd[1863]: Power is back. UPS running on mains.
Sep 20 06:33:22 Tower apcupsd[1863]: Power failure.
Sep 20 06:33:22 Tower apcupsd[1863]: Power is back. UPS running on mains.
Sep 20 06:33:22 Tower apcupsd[1863]: Power failure.
Sep 20 06:33:22 Tower apcupsd[1863]: Power is back. UPS running on mains.
Sep 20 06:33:23 Tower apcupsd[1863]: Power failure.
Sep 20 06:33:23 Tower apcupsd[1863]: Power is back. UPS running on mains.
Sep 20 06:33:23 Tower apcupsd[1863]: Power failure.
Sep 20 06:33:23 Tower apcupsd[1863]: Power is back. UPS running on mains.
Sep 20 06:33:24 Tower apcupsd[1863]: Power failure.
Sep 20 06:33:24 Tower apcupsd[1863]: Power is back. UPS running on mains.
Sep 20 06:33:24 Tower apcupsd[1863]: Power failure.
Sep 20 06:33:24 Tower apcupsd[1863]: Power is back. UPS running on mains.
Sep 20 06:33:25 Tower apcupsd[1863]: Power failure.
Sep 20 06:33:25 Tower apcupsd[1863]: Power is back. UPS running on mains.
Sep 20 06:33:25 Tower apcupsd[1863]: Power failure.
Sep 20 06:33:25 Tower apcupsd[1863]: Power is back. UPS running on mains.
Sep 20 06:33:26 Tower apcupsd[1863]: Power failure.
Sep 20 06:33:26 Tower apcupsd[1863]: Power is back. UPS running on mains.
Sep 20 06:33:27 Tower apcupsd[1863]: Power failure.
Sep 20 06:33:27 Tower apcupsd[1863]: Power is back. UPS running on mains.
Sep 20 06:33:27 Tower apcupsd[1863]: Power failure.
Sep 20 06:33:27 Tower apcupsd[1863]: Power is back. UPS running on mains.
Sep 20 06:33:28 Tower apcupsd[1863]: Power failure.
Sep 20 06:33:28 Tower apcupsd[1863]: Power is back. UPS running on mains.
Sep 20 06:33:28 Tower apcupsd[1863]: Power failure.
Sep 20 06:33:28 Tower apcupsd[1863]: Power is back. UPS running on mains.
Sep 20 06:33:29 Tower apcupsd[1863]: Power failure.
Sep 20 06:33:29 Tower apcupsd[1863]: Power is back. UPS running on mains.
Sep 20 06:33:29 Tower apcupsd[1863]: Power failure.
Sep 20 06:33:29 Tower apcupsd[1863]: Power is back. UPS running on mains.
Sep 20 06:33:30 Tower apcupsd[1863]: Power failure.
Sep 20 06:33:30 Tower apcupsd[1863]: Power is back. UPS running on mains.
Sep 20 06:33:30 Tower apcupsd[1863]: Power failure.
Sep 20 06:33:30 Tower apcupsd[1863]: Power is back. UPS running on mains.
Sep 20 06:33:31 Tower apcupsd[1863]: Power failure.
Sep 20 06:33:31 Tower apcupsd[1863]: Power is back. UPS running on mains.
Sep 20 06:33:32 Tower apcupsd[1863]: Power failure.
Sep 20 06:33:32 Tower apcupsd[1863]: Power is back. UPS running on mains.
Sep 20 06:33:32 Tower rpc.mountd[3915]: authenticated unmount request from 10.2.1.15:716 for /mnt/user/Photos (/mnt/user/Photos)
Sep 20 06:33:32 Tower apcupsd[1863]: Power failure.
Sep 20 06:33:32 Tower apcupsd[1863]: Power is back. UPS running on mains.
Sep 20 06:33:33 Tower apcupsd[1863]: Power failure.
Sep 20 06:33:33 Tower apcupsd[1863]: Power is back. UPS running on mains.
Sep 20 06:33:33 Tower rpc.mountd[3915]: authenticated mount request from 10.2.1.15:693 for /mnt/user/Photos (/mnt/user/Photos)
Sep 20 06:33:33 Tower apcupsd[1863]: Power failure.
Sep 20 06:33:33 Tower apcupsd[1863]: Power is back. UPS running on mains.
Sep 20 06:33:34 Tower apcupsd[1863]: Power failure.
Sep 20 06:33:34 Tower apcupsd[1863]: Power is back. UPS running on mains.
Sep 20 06:33:34 Tower apcupsd[1863]: Power failure.
Sep 20 06:33:34 Tower apcupsd[1863]: Power is back. UPS running on mains.
Sep 20 06:33:35 Tower apcupsd[1863]: Power failure.
Sep 20 06:33:35 Tower apcupsd[1863]: Power is back. UPS running on mains.
Sep 20 06:33:35 Tower apcupsd[1863]: Power failure.
Sep 20 06:33:35 Tower apcupsd[1863]: Power is back. UPS running on mains.
Sep 20 06:33:36 Tower apcupsd[1863]: Power failure.
Sep 20 06:33:36 Tower apcupsd[1863]: Power is back. UPS running on mains.
Sep 20 06:33:37 Tower apcupsd[1863]: Power failure.
Sep 20 06:33:37 Tower apcupsd[1863]: Power is back. UPS running on mains.
Sep 20 06:33:37 Tower apcupsd[1863]: Power failure.
Sep 20 06:33:37 Tower apcupsd[1863]: Power is back. UPS running on mains.
Sep 20 06:33:38 Tower apcupsd[1863]: Power failure.
Sep 20 06:33:38 Tower apcupsd[1863]: Power is back. UPS running on mains.
Sep 20 06:33:38 Tower apcupsd[1863]: Power failure.
Sep 20 06:33:38 Tower apcupsd[1863]: Power is back. UPS running on mains.
Sep 20 06:33:39 Tower apcupsd[1863]: Power failure.
Sep 20 06:33:39 Tower apcupsd[1863]: Power is back. UPS running on mains.
Sep 20 06:33:39 Tower apcupsd[1863]: Power failure.
Sep 20 06:33:39 Tower apcupsd[1863]: Power is back. UPS running on mains.
Sep 20 06:33:40 Tower apcupsd[1863]: Power failure.
Sep 20 06:33:40 Tower apcupsd[1863]: Power is back. UPS running on mains.
Sep 20 06:33:40 Tower apcupsd[1863]: Power failure.
Sep 20 06:33:40 Tower apcupsd[1863]: Power is back. UPS running on mains.
Sep 20 06:33:41 Tower apcupsd[1863]: Power failure.
Sep 20 06:33:41 Tower apcupsd[1863]: Power is back. UPS running on mains.
Sep 20 06:33:42 Tower apcupsd[1863]: Power failure.
Sep 20 06:33:42 Tower apcupsd[1863]: Power is back. UPS running on mains.
Sep 20 06:33:42 Tower apcupsd[1863]: Power failure.
Sep 20 06:33:42 Tower apcupsd[1863]: Power is back. UPS running on mains.
Sep 20 06:33:43 Tower apcupsd[1863]: Power failure.
Sep 20 06:33:43 Tower apcupsd[1863]: Power is back. UPS running on mains.
Sep 20 06:33:43 Tower apcupsd[1863]: Power failure.
Sep 20 06:33:43 Tower apcupsd[1863]: Power is back. UPS running on mains.
Sep 20 06:33:44 Tower apcupsd[1863]: Power failure.
Sep 20 06:33:44 Tower apcupsd[1863]: Power is back. UPS running on mains.
Sep 20 06:33:44 Tower apcupsd[1863]: Power failure.
Sep 20 06:33:44 Tower apcupsd[1863]: Power is back. UPS running on mains.
Sep 20 06:33:45 Tower apcupsd[1863]: Power failure.
Sep 20 06:33:45 Tower apcupsd[1863]: Power is back. UPS running on mains.
Sep 20 06:33:45 Tower apcupsd[1863]: Power failure.
Sep 20 06:33:51 Tower apcupsd[1863]: Running on UPS batteries.
Sep 20 06:34:48 Tower rpc.mountd[3915]: authenticated unmount request from 10.2.1.15:930 for /mnt/user/Photos (/mnt/user/Photos)
Sep 20 06:34:49 Tower rpc.mountd[3915]: authenticated mount request from 10.2.1.15:756 for /mnt/user/Photos (/mnt/user/Photos)
Sep 20 06:36:04 Tower rpc.mountd[3915]: authenticated unmount request from 10.2.1.15:945 for /mnt/user/Photos (/mnt/user/Photos)
Sep 20 06:36:05 Tower rpc.mountd[3915]: authenticated mount request from 10.2.1.15:1015 for /mnt/user/Photos (/mnt/user/Photos)
Sep 20 06:36:14 Tower fan_speed.sh: Highest disk drive temp is: 37C
Sep 20 06:36:14 Tower fan_speed.sh: Changing disk drive fan speed from: [108 (42% @ 1239 rpm) ] to: [72 (28% @ 851 rpm) ]
Sep 20 06:37:19 Tower rpc.mountd[3915]: authenticated unmount request from 10.2.1.15:965 for /mnt/user/Photos (/mnt/user/Photos)
Sep 20 06:37:20 Tower rpc.mountd[3915]: authenticated mount request from 10.2.1.15:935 for /mnt/user/Photos (/mnt/user/Photos)
Sep 20 06:37:48 Tower sshd[31074]: Received disconnect from 10.2.1.15: 11: disconnected by user
Sep 20 06:37:49 Tower rpc.mountd[3915]: authenticated unmount request from 10.2.1.15:995 for /mnt/user/Photos (/mnt/user/Photos)
Sep 20 06:38:52 Tower apcupsd[1863]: Reached run time limit on batteries.
Sep 20 06:38:52 Tower apcupsd[1863]: Initiating system shutdown!
Sep 20 06:38:52 Tower apcupsd[1863]: User logins prohibited
Sep 20 06:38:52 Tower powerdown[16998]: Powerdown initiated
Sep 20 06:38:52 Tower powerdown[17002]: Powerdown V2.08
Sep 20 06:38:52 Tower rc.unRAID[17004][17005]: Processing /etc/rc.d/rc.unRAID.d/ kill scripts.
Sep 20 06:38:52 Tower rc.unRAID[17004][17009]: Running: "/etc/rc.d/rc.unRAID.d/K00.sh"
Sep 20 06:38:52 Tower rc.unRAID[17004][17012]: Shutting down domain 4
Sep 20 06:38:52 Tower rc.unRAID[17004][17012]: Waiting for 1 domains
Sep 20 06:38:52 Tower rpc.mountd[3915]: authenticated unmount request from 10.2.0.104:632 for /mnt/user/mysql (/mnt/user/mysql)
Sep 20 06:39:03 Tower kernel: br0: port 2(vif4.0) entered disabled state
Sep 20 06:39:03 Tower rc.unRAID[17004][17012]: Domain 4 has been shut down, reason code 0
Sep 20 06:39:03 Tower kernel: br0: port 2(vif4.0) entered disabled state
Sep 20 06:39:03 Tower avahi-daemon[2948]: Withdrawing workstation service for vif4.0.
Sep 20 06:39:03 Tower powerdown[17215]: Initiating Shutdown with ''
Sep 20 06:39:03 Tower shutdown[17217]: shutting down for system halt
Sep 20 06:39:03 Tower kernel: device vif4.0 left promiscuous mode
Sep 20 06:39:03 Tower kernel: br0: port 2(vif4.0) entered disabled state
Sep 20 06:39:03 Tower logger: /etc/xen/scripts/vif-bridge: offline type_if=vif XENBUS_PATH=backend/vif/4/0
Sep 20 06:39:03 Tower logger: /etc/xen/scripts/vif-bridge: brctl delif br0 vif4.0 failed
Sep 20 06:39:03 Tower logger: /etc/xen/scripts/vif-bridge: ifconfig vif4.0 down failed
Sep 20 06:39:03 Tower logger: /etc/xen/scripts/vif-bridge: Successful vif-bridge offline for vif4.0, bridge br0.
Sep 20 06:39:03 Tower init: Switching to runlevel: 0
Sep 20 06:39:05 Tower rc.unRAID[17338][17339]: Powerdown V2.08
Sep 20 06:39:05 Tower rc.unRAID[17338][17340]: Stopping Plugins.
Sep 20 06:39:05 Tower rc.unRAID[17338][17348]: Running: "/etc/rc.d/rc.dovecot stop"
Sep 20 06:39:05 Tower rc.unRAID[17338][17351]: Stopping dovecot...
Sep 20 06:39:05 Tower rc.unRAID[17338][17353]: Running: "/etc/rc.d/rc.fan_speed stop"
Sep 20 06:39:05 Tower rc.fan_speed: WARNING: fan_speed called to stop with SERVICE not = disabled
Sep 20 06:39:05 Tower rc.unRAID[17338][17364]: Running: "/etc/rc.d/rc.mpop stop"
Sep 20 06:39:06 Tower rc.unRAID[17338][17393]: Running: "/etc/rc.d/rc.tftp-hpa stop"
Sep 20 06:39:06 Tower rc.unRAID[17338][17396]: command /etc/rc.d/rc.tftp-hpa stop 
Sep 20 06:39:06 Tower rc.unRAID[17338][17397]: Stopping unRAID.
Sep 20 06:39:06 Tower rpc.mountd[3915]: Caught signal 15, un-registering and exiting.
Sep 20 06:39:08 Tower kernel: nfsd: last server has exited, flushing export cache
Sep 20 06:39:08 Tower rc.unRAID[17338][17433]: umount2: Device or resource busy
Sep 20 06:39:08 Tower rc.unRAID[17338][17433]: umount: /var/lib/docker: device is busy.
Sep 20 06:39:08 Tower rc.unRAID[17338][17433]:         (In some cases useful info about processes that use
Sep 20 06:39:08 Tower rc.unRAID[17338][17433]:          the device is found by lsof( or fuser(1))
Sep 20 06:39:08 Tower rc.unRAID[17338][17433]: umount2: Device or resource busy
Sep 20 06:39:08 Tower rc.unRAID[17338][17439]: Killing active pids on the array drives
Sep 20 06:39:08 Tower rc.unRAID[17338][17443]: Sync filesystems
Sep 20 06:39:08 Tower rc.unRAID[17338][17445]: Umounting the drives
Sep 20 06:39:08 Tower rc.unRAID[17338][17449]: umount2: Device or resource busy
Sep 20 06:39:08 Tower rc.unRAID[17338][17449]: umount: /mnt/disk1: device is busy.
Sep 20 06:39:08 Tower rc.unRAID[17338][17449]:         (In some cases useful info about processes that use
Sep 20 06:39:08 Tower rc.unRAID[17338][17449]:          the device is found by lsof( or fuser(1))
Sep 20 06:39:08 Tower rc.unRAID[17338][17449]: umount2: Device or resource busy
Sep 20 06:39:08 Tower rc.unRAID[17338][17449]: /dev/md2 has been unmounted
Sep 20 06:39:08 Tower rc.unRAID[17338][17449]: umount2: Device or resource busy
Sep 20 06:39:08 Tower rc.unRAID[17338][17449]: umount: /mnt/disk3: device is busy.
Sep 20 06:39:08 Tower rc.unRAID[17338][17449]:         (In some cases useful info about processes that use
Sep 20 06:39:08 Tower rc.unRAID[17338][17449]:          the device is found by lsof( or fuser(1))
Sep 20 06:39:08 Tower rc.unRAID[17338][17449]: umount2: Device or resource busy
Sep 20 06:39:08 Tower rc.unRAID[17338][17449]: /dev/md4 has been unmounted
Sep 20 06:39:08 Tower rc.unRAID[17338][17449]: /dev/md5 has been unmounted
Sep 20 06:39:08 Tower rc.unRAID[17338][17455]: Active pids left on the array drives
Sep 20 06:39:08 Tower rc.unRAID[17338][17458]:                      USER        PID ACCESS COMMAND
Sep 20 06:39:08 Tower rc.unRAID[17338][17458]: /dev/md1:            root     kernel mount /mnt/disk1
Sep 20 06:39:08 Tower rc.unRAID[17338][17458]:                      root       3095 F.... shfs
Sep 20 06:39:08 Tower rc.unRAID[17338][17458]: /dev/md3:            root     kernel mount /mnt/disk3
Sep 20 06:39:08 Tower rc.unRAID[17338][17458]:                      root       3095 f.... shfs
Sep 20 06:39:08 Tower rc.unRAID[17338][17459]: Stopping the Array
Sep 20 06:39:08 Tower rc.unRAID[17338][17465]: /root/mdcmd: line 11: echo: write error: Device or resource busy
Sep 20 06:39:08 Tower kernel: mdcmd (65): stop 
Sep 20 06:39:08 Tower kernel: md: 5 devices still in use.

 

I'm reverting to powerdown v2.06, because I know that has worked perfectly in the past.  Refer back to my reply #24 above, with a log from Sep 13, where v6.0beta9 was running with powerdown v2.06.  It can be seen there that rc.docker stop was called, and two docker containers  were identified, presumably as they exited.

  • Author

As part of the process of shutting down, powerdown walks through the /etc/rc.d directory and issues a stop command on all rc. files found.  There is a list of these files that powerdown skips because it is not appropriate to issue the stop command to LT provided scripts.  A list of the files to skip is in a file called rcdstock.  This list is generated from a bare metal unRAID boot.  The list of files to skip is all the files in the /etc/rc.d directory from a boot into Xen with no plugins.

 

As V6 has progressed along, files have been added to powerdown's list.  V2.08 added the rc.docker to the list.  Previous to V2.08, powerdown stopped docker with the 'rc.docker stop'.  While this shuts down docker in the earlier versions of V6 betas, it is not the job of powerdown to shutdown docker.  LT needs to add shutting down docker to a file called rc.local_shutdown.  This is where Xen is stopped when unRAID is being shutdown.  Docker is stopped from the gui but not when a shutdown occurs outside of the gui.

 

This same issue occurred earlier before LT added the Xen stop to the rc.local_shutdown script.

 

To get around this until LT fixes it, put the following kill file in /boot/config/plugins/powerdown/rc.unRAID.d/K00.sh

 

# shutdown docker
if [ -x /etc/rc.d/rc.docker ]
then
/etc/rc.d/rc.docker stop
fi

 

Please keep in mind that V6 is in beta and things are changing as we go.  While I do my best to keep up with the changes, these kinds of issues will happen.  You like many others are considering the betas as production releases and then getting testy when there are issues.  This is beta software!  There will be glitches and things will happen.  If you don't want to deal with these kinds of problems, don't use beta software, use the latest stable release.

 

I know you just want powerdown to shut everything down cleanly and just do whatever it takes.  It is not intended that powerdown make up for deficiencies in unRAID and plugins.  It is up to LT to provide a clean shutdown of XEN and docker.  Plugin authors need to provide rc. scripts that shut down their plugins properly.  I really don't appreciate the comments about powerdown being such a failure and it doesn't work.  If you feel you can do a better job, pull the code and modify it yourself.

As part of the process of shutting down, powerdown walks through the /etc/rc.d directory and issues a stop command on all rc. files found.  There is a list of these files that powerdown skips because it is not appropriate to issue the stop command to LT provided scripts.  A list of the files to skip is in a file called rcdstock.  This list is generated from a bare metal unRAID boot.  The list of files to skip is all the files in the /etc/rc.d directory from a boot into Xen with no plugins.

 

As V6 has progressed along, files have been added to powerdown's list.  V2.08 added the rc.docker to the list.  Previous to V2.08, powerdown stopped docker with the 'rc.docker stop'.  While this shuts down docker in the earlier versions of V6 betas, it is not the job of powerdown to shutdown docker.  LT needs to add shutting down docker to a file called rc.local_shutdown.  This is where Xen is stopped when unRAID is being shutdown.  Docker is stopped from the gui but not when a shutdown occurs outside of the gui.

 

Thanks for the detailed explanation - that all makes sense, and explains the apparent reversion between 2.06/2.08.  Of course, 2.06 did allow my machine to shutdown cleanly during a powercut last night

 

This same issue occurred earlier before LT added the Xen stop to the rc.local_shutdown script.

 

To get around this until LT fixes it, put the following kill file in /boot/config/plugins/powerdown/rc.unRAID.d/K00.sh

 

# shutdown docker
if [ -x /etc/rc.d/rc.docker ]
then
/etc/rc.d/rc.docker stop
fi

 

Thank you for the detailed instructions - that made it very simple to implement,  I note that my K00.sh has the following line:

xl shutdown -a -w

 

Is that left over from a previous version of powerdown, and should it now be removed?

 

Please keep in mind that V6 is in beta and things are changing as we go.  While I do my best to keep up with the changes, these kinds of issues will happen.  You like many others are considering the betas as production releases and then getting testy when there are issues.  This is beta software!  There will be glitches and things will happen.  If you don't want to deal with these kinds of problems, don't use beta software, use the latest stable release.

 

I fully understand what beta software is, but hope that I can contribute to the project by running the beta versions,  After many years working in the IT industry, I heve learned that however rigorous the formal testing procedures are, it is inevitable that live use of software will quickly expose issues that weren't caught by the formal testing.  I was certainly able to make Tom aware of a couple of issues during the V5 beta cycle.

 

I know you just want powerdown to shut everything down cleanly and just do whatever it takes.

 

Of course!  ;D

 

It is not intended that powerdown make up for deficiencies in unRAID and plugins.  It is up to LT to provide a clean shutdown of XEN and docker.  Plugin authors need to provide rc. scripts that shut down their plugins properly.

 

Indeed, I do understand that - and that is why I refused to add code to my early 64-bit conversion of apcupsd, in order to work around the fact the unRAID was loading plugins before the network was up.  However, in that case there was a very obvious way to overcome the problem ... by installing the plugin manually, rather than relying on automatic install at boot time.

 

Having said that, in a sense, the entire powerdown script exists in order to work around weaknesses in the way that unRAID behaves in 'emergency' shutdown situations.  One of these weaknesses still catches me out very frequently - the fact that the array will not stop from the gui while there are terminal sessions whose current working directory is on one of the array devices.  Thankfully, powerdown does deal very effectively with this problem.

 

I really don't appreciate the comments about powerdown being such a failure and it doesn't work.  If you feel you can do a better job, pull the code and modify it yourself.

 

I'm sorry - I think that you misunderstand the tone of some of my postings - often a problem when using informal written communication between people who don't know each other.  I really do appreciate everything you are contributing to the project, but I can see how the phrases I have used can appear to be critical.

 

Apologies!

  • Author
Thank you for the detailed instructions - that made it very simple to implement,  I note that my K00.sh has the following line:

xl shutdown -a -w

 

Is that left over from a previous version of powerdown, and should it now be removed?

 

Yes, but powerdown did not add it.  That is something I recommended you do to shutdown Xen because LT had not added the shutdown of Xen to the rc.local_shutdown script.  Xen is now shutdown properly on a non-webgui shutdown so it is no longer needed.

 

The docker stop will only be needed temporarily until LT adds it to the rc.local_shutdown script.  I expect LT will add it in one of the upcoming betas.

Arghhhh ... I've just had another unclean shutdown after a power cut this evening.  :'(

 

This was with powerdown v2.08 and the K00.sh script set up to stop docker:

root@Tower:~# cat /boot/config/plugins/powerdown/rc.unRAID.d/K00.sh
# shutdown docker
if [ -x /etc/rc.d/rc.docker ]
then
/etc/rc.d/rc.docker stop
fi

 

End of the log file:

Sep 22 16:35:19 Tower apcupsd[1899]: Reached run time limit on batteries.
Sep 22 16:35:19 Tower apcupsd[1899]: Initiating system shutdown!
Sep 22 16:35:19 Tower apcupsd[1899]: User logins prohibited
Sep 22 16:35:19 Tower powerdown[24464]: Powerdown initiated
Sep 22 16:35:19 Tower powerdown[24468]: Powerdown V2.08
Sep 22 16:35:19 Tower rc.unRAID[24470][24471]: Processing /etc/rc.d/rc.unRAID.d/ kill scripts.
Sep 22 16:35:19 Tower rc.unRAID[24470][24475]: Running: "/etc/rc.d/rc.unRAID.d/K00.sh"
Sep 22 16:35:19 Tower rc.unRAID[24470][24478]: Shutting down domain 1
Sep 22 16:35:19 Tower rc.unRAID[24470][24478]: Waiting for 1 domains
Sep 22 16:35:19 Tower rpc.mountd[4067]: authenticated unmount request from 10.2.0.104:988 for /mnt/user/mysql (/mnt/user/mysql)
Sep 22 16:35:24 Tower kernel: br0: port 2(vif1.0) entered disabled state
Sep 22 16:35:24 Tower rc.unRAID[24470][24478]: Domain 1 has been shut down, reason code 0
Sep 22 16:35:24 Tower powerdown[24579]: Initiating Shutdown with ''
Sep 22 16:35:24 Tower shutdown[24581]: shutting down for system halt
Sep 22 16:35:24 Tower avahi-daemon[2988]: Withdrawing workstation service for vif1.0.
Sep 22 16:35:24 Tower kernel: br0: port 2(vif1.0) entered disabled state
Sep 22 16:35:24 Tower kernel: device vif1.0 left promiscuous mode
Sep 22 16:35:24 Tower kernel: br0: port 2(vif1.0) entered disabled state
Sep 22 16:35:24 Tower logger: /etc/xen/scripts/vif-bridge: offline type_if=vif XENBUS_PATH=backend/vif/1/0
Sep 22 16:35:24 Tower logger: /etc/xen/scripts/vif-bridge: brctl delif br0 vif1.0 failed
Sep 22 16:35:24 Tower logger: /etc/xen/scripts/vif-bridge: ifconfig vif1.0 down failed
Sep 22 16:35:24 Tower logger: /etc/xen/scripts/vif-bridge: Successful vif-bridge offline for vif1.0, bridge br0.
Sep 22 16:35:24 Tower init: Switching to runlevel: 0
Sep 22 16:35:26 Tower rc.unRAID[24686][24687]: Powerdown V2.08
Sep 22 16:35:26 Tower rc.unRAID[24686][24688]: Stopping Plugins.
Sep 22 16:35:26 Tower rc.unRAID[24686][24696]: Running: "/etc/rc.d/rc.dovecot stop"
Sep 22 16:35:26 Tower rc.unRAID[24686][24699]: Stopping dovecot...
Sep 22 16:35:26 Tower rc.unRAID[24686][24701]: Running: "/etc/rc.d/rc.fan_speed stop"
Sep 22 16:35:26 Tower rc.fan_speed: WARNING: fan_speed called to stop with SERVICE not = disabled
Sep 22 16:35:26 Tower rc.unRAID[24686][24712]: Running: "/etc/rc.d/rc.mpop stop"
Sep 22 16:35:27 Tower rc.unRAID[24686][24743]: Running: "/etc/rc.d/rc.tftp-hpa stop"
Sep 22 16:35:27 Tower rc.unRAID[24686][24746]: command /etc/rc.d/rc.tftp-hpa stop 
Sep 22 16:35:27 Tower rc.unRAID[24686][24747]: Stopping unRAID.
Sep 22 16:35:27 Tower rpc.mountd[4067]: Caught signal 15, un-registering and exiting.
Sep 22 16:35:29 Tower kernel: nfsd: last server has exited, flushing export cache
Sep 22 16:35:29 Tower rc.unRAID[24686][24782]: umount2: Device or resource busy
Sep 22 16:35:29 Tower rc.unRAID[24686][24782]: umount: /var/lib/docker: device is busy.
Sep 22 16:35:29 Tower rc.unRAID[24686][24782]:         (In some cases useful info about processes that use
Sep 22 16:35:29 Tower rc.unRAID[24686][24782]:          the device is found by lsof( or fuser(1))
Sep 22 16:35:29 Tower rc.unRAID[24686][24782]: umount2: Device or resource busy
Sep 22 16:35:29 Tower rc.unRAID[24686][24797]: Killing active pids on the array drives
Sep 22 16:35:29 Tower rc.unRAID[24686][24803]: Sync filesystems
Sep 22 16:35:29 Tower rc.unRAID[24686][24805]: Umounting the drives
Sep 22 16:35:29 Tower rc.unRAID[24686][24809]: umount2: Device or resource busy
Sep 22 16:35:29 Tower rc.unRAID[24686][24809]: umount: /mnt/disk1: device is busy.
Sep 22 16:35:29 Tower rc.unRAID[24686][24809]:         (In some cases useful info about processes that use
Sep 22 16:35:29 Tower rc.unRAID[24686][24809]:          the device is found by lsof( or fuser(1))
Sep 22 16:35:29 Tower rc.unRAID[24686][24809]: umount2: Device or resource busy
Sep 22 16:35:29 Tower rc.unRAID[24686][24809]: /dev/md2 has been unmounted
Sep 22 16:35:29 Tower rc.unRAID[24686][24809]: umount2: Device or resource busy
Sep 22 16:35:29 Tower rc.unRAID[24686][24809]: umount: /mnt/disk3: device is busy.
Sep 22 16:35:29 Tower rc.unRAID[24686][24809]:         (In some cases useful info about processes that use
Sep 22 16:35:29 Tower rc.unRAID[24686][24809]:          the device is found by lsof( or fuser(1))
Sep 22 16:35:29 Tower rc.unRAID[24686][24809]: umount2: Device or resource busy
Sep 22 16:35:29 Tower rc.unRAID[24686][24809]: /dev/md4 has been unmounted
Sep 22 16:35:29 Tower rc.unRAID[24686][24809]: /dev/md5 has been unmounted
Sep 22 16:35:29 Tower rc.unRAID[24686][24815]: Active pids left on the array drives
Sep 22 16:35:29 Tower rc.unRAID[24686][24818]:                      USER        PID ACCESS COMMAND
Sep 22 16:35:29 Tower rc.unRAID[24686][24818]: /dev/md1:            root     kernel mount /mnt/disk1
Sep 22 16:35:29 Tower rc.unRAID[24686][24818]:                      root       3132 F.... shfs
Sep 22 16:35:29 Tower rc.unRAID[24686][24818]: /dev/md3:            root     kernel mount /mnt/disk3
Sep 22 16:35:29 Tower rc.unRAID[24686][24818]:                      root       3132 f.... shfs
Sep 22 16:35:29 Tower rc.unRAID[24686][24819]: Stopping the Array
Sep 22 16:35:29 Tower rc.unRAID[24686][24825]: /root/mdcmd: line 11: echo: write error: Device or resource busy
Sep 22 16:35:29 Tower kernel: mdcmd (41): stop 
Sep 22 16:35:29 Tower kernel: md: 5 devices still in use.
Sep 22 16:35:34 Tower mdstatusdiff[24922]: --- /tmp/mdcmd.24686.1#0112014-09-22 16:35:29.386915250 +0800
Sep 22 16:35:34 Tower mdstatusdiff[24922]: +++ /tmp/mdcmd.24686.2#0112014-09-22 16:35:34.396904667 +0800
Sep 22 16:35:34 Tower mdstatusdiff[24922]: @@ -72,7 +72,7 @@
Sep 22 16:35:34 Tower mdstatusdiff[24922]:  rdevSize.3=1953514552
Sep 22 16:35:34 Tower mdstatusdiff[24922]:  rdevId.3=SAMSUNG_HD204UI_S2H7J90B602221
Sep 22 16:35:34 Tower mdstatusdiff[24922]:  rdevNumErrors.3=0
Sep 22 16:35:34 Tower mdstatusdiff[24922]: -rdevLastIO.3=1411374929
Sep 22 16:35:34 Tower mdstatusdiff[24922]: +rdevLastIO.3=1411374933
Sep 22 16:35:34 Tower mdstatusdiff[24922]:  rdevSpinupGroup.3=0
Sep 22 16:35:34 Tower mdstatusdiff[24922]:  diskNumber.4=4

 

 

I currently only have one Xen domain set to autostart, and it appears that it was closed down successfully.  However, it would seem that K00.sh didn't shut down my two dockers, because devices associated with those didn't dismount.

 

Ah .... I'm just wondering .... perhaps I should have rebooted after I edited /boot/config/plugins/powerdown/rc.unRAID.d/K00.sh.  It seems that K00.sh is executed from the volatile memory disk, and I guess that it takes a reboot to propogate from the flash drive to the system drive.  :-[

 

Okay, let's hope that the power stays up for long enough to allow the parity check to complete and that all will be well next time!

 

One puzzle is that it is reported that md2, md3 and md5 have been unmounted, yet further down there is a report 

Sep 22 16:35:29 Tower kernel: md: 5 devices still in use.

 

I wonder which the five devices are ... I only have five data devices, (plus parity, cache and another drive, outside of the protected array, for docker).

 

I'm also puzzled by this:

29:59 Tower apcupsd[1899]: Power failure.
Sep 22 16:29:59 Tower apcupsd[1899]: Power is back. UPS running on mains.
Sep 22 16:29:59 Tower apcupsd[1899]: Power failure.
Sep 22 16:29:59 Tower apcupsd[1899]: Power is back. UPS running on mains.
Sep 22 16:30:00 Tower apcupsd[1899]: Power failure.
Sep 22 16:30:00 Tower apcupsd[1899]: Power is back. UPS running on mains.
Sep 22 16:30:00 Tower apcupsd[1899]: Power failure.
Sep 22 16:30:00 Tower apcupsd[1899]: Power is back. UPS running on mains.
Sep 22 16:30:01 Tower apcupsd[1899]: Power failure.
Sep 22 16:30:01 Tower apcupsd[1899]: Power is back. UPS running on mains.
Sep 22 16:30:01 Tower apcupsd[1899]: Power failure.
Sep 22 16:30:01 Tower apcupsd[1899]: Power is back. UPS running on mains.
Sep 22 16:30:02 Tower apcupsd[1899]: Power failure.
Sep 22 16:30:02 Tower apcupsd[1899]: Power is back. UPS running on mains.
Sep 22 16:30:03 Tower apcupsd[1899]: Power failure.
Sep 22 16:30:03 Tower apcupsd[1899]: Power is back. UPS running on mains.
Sep 22 16:30:03 Tower apcupsd[1899]: Power failure.
Sep 22 16:30:03 Tower apcupsd[1899]: Power is back. UPS running on mains.
Sep 22 16:30:04 Tower apcupsd[1899]: Power failure.
Sep 22 16:30:04 Tower apcupsd[1899]: Power is back. UPS running on mains.
Sep 22 16:30:04 Tower apcupsd[1899]: Power failure.
Sep 22 16:30:04 Tower apcupsd[1899]: Power is back. UPS running on mains.
Sep 22 16:30:05 Tower apcupsd[1899]: Power failure.
Sep 22 16:30:05 Tower apcupsd[1899]: Power is back. UPS running on mains.
Sep 22 16:30:05 Tower apcupsd[1899]: Power failure.
Sep 22 16:30:05 Tower apcupsd[1899]: Power is back. UPS running on mains.
Sep 22 16:30:06 Tower apcupsd[1899]: Power failure.
Sep 22 16:30:06 Tower apcupsd[1899]: Power is back. UPS running on mains.
Sep 22 16:30:06 Tower apcupsd[1899]: Power failure.
Sep 22 16:30:06 Tower apcupsd[1899]: Power is back. UPS running on mains.
Sep 22 16:30:07 Tower apcupsd[1899]: Power failure.
Sep 22 16:30:07 Tower apcupsd[1899]: Power is back. UPS running on mains.
Sep 22 16:30:08 Tower apcupsd[1899]: Power failure.
Sep 22 16:30:08 Tower apcupsd[1899]: Power is back. UPS running on mains.
Sep 22 16:30:08 Tower apcupsd[1899]: Power failure.
Sep 22 16:30:08 Tower apcupsd[1899]: Power is back. UPS running on mains.
Sep 22 16:30:09 Tower apcupsd[1899]: Power failure.
Sep 22 16:30:09 Tower apcupsd[1899]: Power is back. UPS running on mains.
Sep 22 16:30:09 Tower apcupsd[1899]: Power failure.
Sep 22 16:30:09 Tower apcupsd[1899]: Power is back. UPS running on mains.
Sep 22 16:30:10 Tower apcupsd[1899]: Power failure.
Sep 22 16:30:10 Tower apcupsd[1899]: Power is back. UPS running on mains.
Sep 22 16:30:10 Tower apcupsd[1899]: Power failure.
Sep 22 16:30:10 Tower apcupsd[1899]: Power is back. UPS running on mains.
Sep 22 16:30:11 Tower apcupsd[1899]: Power failure.
Sep 22 16:30:11 Tower apcupsd[1899]: Power is back. UPS running on mains.
Sep 22 16:30:11 Tower apcupsd[1899]: Power failure.
Sep 22 16:30:11 Tower apcupsd[1899]: Power is back. UPS running on mains.
Sep 22 16:30:12 Tower apcupsd[1899]: Power failure.

in the logfile.

 

I don't recall having seen the repeated messages in the past.

  • Author

Arghhhh ... I've just had another unclean shutdown after a power cut this evening.  :'(

 

This was with powerdown v2.08 and the K00.sh script set up to stop docker:

root@Tower:~# cat /boot/config/plugins/powerdown/rc.unRAID.d/K00.sh
# shutdown docker
if [ -x /etc/rc.d/rc.docker ]
then
/etc/rc.d/rc.docker stop
fi

 

End of the log file:

Sep 22 16:35:19 Tower apcupsd[1899]: Reached run time limit on batteries.
Sep 22 16:35:19 Tower apcupsd[1899]: Initiating system shutdown!
Sep 22 16:35:19 Tower apcupsd[1899]: User logins prohibited
Sep 22 16:35:19 Tower powerdown[24464]: Powerdown initiated
Sep 22 16:35:19 Tower powerdown[24468]: Powerdown V2.08
Sep 22 16:35:19 Tower rc.unRAID[24470][24471]: Processing /etc/rc.d/rc.unRAID.d/ kill scripts.
Sep 22 16:35:19 Tower rc.unRAID[24470][24475]: Running: "/etc/rc.d/rc.unRAID.d/K00.sh"
Sep 22 16:35:19 Tower rc.unRAID[24470][24478]: Shutting down domain 1
Sep 22 16:35:19 Tower rc.unRAID[24470][24478]: Waiting for 1 domains
Sep 22 16:35:19 Tower rpc.mountd[4067]: authenticated unmount request from 10.2.0.104:988 for /mnt/user/mysql (/mnt/user/mysql)
Sep 22 16:35:24 Tower kernel: br0: port 2(vif1.0) entered disabled state
Sep 22 16:35:24 Tower rc.unRAID[24470][24478]: Domain 1 has been shut down, reason code 0
Sep 22 16:35:24 Tower powerdown[24579]: Initiating Shutdown with ''
Sep 22 16:35:24 Tower shutdown[24581]: shutting down for system halt
Sep 22 16:35:24 Tower avahi-daemon[2988]: Withdrawing workstation service for vif1.0.
Sep 22 16:35:24 Tower kernel: br0: port 2(vif1.0) entered disabled state
Sep 22 16:35:24 Tower kernel: device vif1.0 left promiscuous mode
Sep 22 16:35:24 Tower kernel: br0: port 2(vif1.0) entered disabled state
Sep 22 16:35:24 Tower logger: /etc/xen/scripts/vif-bridge: offline type_if=vif XENBUS_PATH=backend/vif/1/0
Sep 22 16:35:24 Tower logger: /etc/xen/scripts/vif-bridge: brctl delif br0 vif1.0 failed
Sep 22 16:35:24 Tower logger: /etc/xen/scripts/vif-bridge: ifconfig vif1.0 down failed
Sep 22 16:35:24 Tower logger: /etc/xen/scripts/vif-bridge: Successful vif-bridge offline for vif1.0, bridge br0.
Sep 22 16:35:24 Tower init: Switching to runlevel: 0
Sep 22 16:35:26 Tower rc.unRAID[24686][24687]: Powerdown V2.08
Sep 22 16:35:26 Tower rc.unRAID[24686][24688]: Stopping Plugins.
Sep 22 16:35:26 Tower rc.unRAID[24686][24696]: Running: "/etc/rc.d/rc.dovecot stop"
Sep 22 16:35:26 Tower rc.unRAID[24686][24699]: Stopping dovecot...
Sep 22 16:35:26 Tower rc.unRAID[24686][24701]: Running: "/etc/rc.d/rc.fan_speed stop"
Sep 22 16:35:26 Tower rc.fan_speed: WARNING: fan_speed called to stop with SERVICE not = disabled
Sep 22 16:35:26 Tower rc.unRAID[24686][24712]: Running: "/etc/rc.d/rc.mpop stop"
Sep 22 16:35:27 Tower rc.unRAID[24686][24743]: Running: "/etc/rc.d/rc.tftp-hpa stop"
Sep 22 16:35:27 Tower rc.unRAID[24686][24746]: command /etc/rc.d/rc.tftp-hpa stop 
Sep 22 16:35:27 Tower rc.unRAID[24686][24747]: Stopping unRAID.
Sep 22 16:35:27 Tower rpc.mountd[4067]: Caught signal 15, un-registering and exiting.
Sep 22 16:35:29 Tower kernel: nfsd: last server has exited, flushing export cache
Sep 22 16:35:29 Tower rc.unRAID[24686][24782]: umount2: Device or resource busy
Sep 22 16:35:29 Tower rc.unRAID[24686][24782]: umount: /var/lib/docker: device is busy.
Sep 22 16:35:29 Tower rc.unRAID[24686][24782]:         (In some cases useful info about processes that use
Sep 22 16:35:29 Tower rc.unRAID[24686][24782]:          the device is found by lsof( or fuser(1))
Sep 22 16:35:29 Tower rc.unRAID[24686][24782]: umount2: Device or resource busy
Sep 22 16:35:29 Tower rc.unRAID[24686][24797]: Killing active pids on the array drives
Sep 22 16:35:29 Tower rc.unRAID[24686][24803]: Sync filesystems
Sep 22 16:35:29 Tower rc.unRAID[24686][24805]: Umounting the drives
Sep 22 16:35:29 Tower rc.unRAID[24686][24809]: umount2: Device or resource busy
Sep 22 16:35:29 Tower rc.unRAID[24686][24809]: umount: /mnt/disk1: device is busy.
Sep 22 16:35:29 Tower rc.unRAID[24686][24809]:         (In some cases useful info about processes that use
Sep 22 16:35:29 Tower rc.unRAID[24686][24809]:          the device is found by lsof( or fuser(1))
Sep 22 16:35:29 Tower rc.unRAID[24686][24809]: umount2: Device or resource busy
Sep 22 16:35:29 Tower rc.unRAID[24686][24809]: /dev/md2 has been unmounted
Sep 22 16:35:29 Tower rc.unRAID[24686][24809]: umount2: Device or resource busy
Sep 22 16:35:29 Tower rc.unRAID[24686][24809]: umount: /mnt/disk3: device is busy.
Sep 22 16:35:29 Tower rc.unRAID[24686][24809]:         (In some cases useful info about processes that use
Sep 22 16:35:29 Tower rc.unRAID[24686][24809]:          the device is found by lsof( or fuser(1))
Sep 22 16:35:29 Tower rc.unRAID[24686][24809]: umount2: Device or resource busy
Sep 22 16:35:29 Tower rc.unRAID[24686][24809]: /dev/md4 has been unmounted
Sep 22 16:35:29 Tower rc.unRAID[24686][24809]: /dev/md5 has been unmounted
Sep 22 16:35:29 Tower rc.unRAID[24686][24815]: Active pids left on the array drives
Sep 22 16:35:29 Tower rc.unRAID[24686][24818]:                      USER        PID ACCESS COMMAND
Sep 22 16:35:29 Tower rc.unRAID[24686][24818]: /dev/md1:            root     kernel mount /mnt/disk1
Sep 22 16:35:29 Tower rc.unRAID[24686][24818]:                      root       3132 F.... shfs
Sep 22 16:35:29 Tower rc.unRAID[24686][24818]: /dev/md3:            root     kernel mount /mnt/disk3
Sep 22 16:35:29 Tower rc.unRAID[24686][24818]:                      root       3132 f.... shfs
Sep 22 16:35:29 Tower rc.unRAID[24686][24819]: Stopping the Array
Sep 22 16:35:29 Tower rc.unRAID[24686][24825]: /root/mdcmd: line 11: echo: write error: Device or resource busy
Sep 22 16:35:29 Tower kernel: mdcmd (41): stop 
Sep 22 16:35:29 Tower kernel: md: 5 devices still in use.
Sep 22 16:35:34 Tower mdstatusdiff[24922]: --- /tmp/mdcmd.24686.1#0112014-09-22 16:35:29.386915250 +0800
Sep 22 16:35:34 Tower mdstatusdiff[24922]: +++ /tmp/mdcmd.24686.2#0112014-09-22 16:35:34.396904667 +0800
Sep 22 16:35:34 Tower mdstatusdiff[24922]: @@ -72,7 +72,7 @@
Sep 22 16:35:34 Tower mdstatusdiff[24922]:  rdevSize.3=1953514552
Sep 22 16:35:34 Tower mdstatusdiff[24922]:  rdevId.3=SAMSUNG_HD204UI_S2H7J90B602221
Sep 22 16:35:34 Tower mdstatusdiff[24922]:  rdevNumErrors.3=0
Sep 22 16:35:34 Tower mdstatusdiff[24922]: -rdevLastIO.3=1411374929
Sep 22 16:35:34 Tower mdstatusdiff[24922]: +rdevLastIO.3=1411374933
Sep 22 16:35:34 Tower mdstatusdiff[24922]:  rdevSpinupGroup.3=0
Sep 22 16:35:34 Tower mdstatusdiff[24922]:  diskNumber.4=4

 

 

I currently only have one Xen domain set to autostart, and it appears that it was closed down successfully.  However, it would seem that K00.sh didn't shut down my two dockers, because devices associated with those didn't dismount.

 

Ah .... I'm just wondering .... perhaps I should have rebooted after I edited /boot/config/plugins/powerdown/rc.unRAID.d/K00.sh.  It seems that K00.sh is executed from the volatile memory disk, and I guess that it takes a reboot to propogate from the flash drive to the system drive.  :-[

 

Okay, let's hope that the power stays up for long enough to allow the parity check to complete and that all will be well next time!

 

One puzzle is that it is reported that md2, md3 and md5 have been unmounted, yet further down there is a report 

Sep 22 16:35:29 Tower kernel: md: 5 devices still in use.

 

I wonder which the five devices are ... I only have five data devices, (plus parity, cache and another drive, outside of the protected array, for docker).

 

I'm also puzzled by this:

29:59 Tower apcupsd[1899]: Power failure.
Sep 22 16:29:59 Tower apcupsd[1899]: Power is back. UPS running on mains.
Sep 22 16:29:59 Tower apcupsd[1899]: Power failure.
Sep 22 16:29:59 Tower apcupsd[1899]: Power is back. UPS running on mains.
Sep 22 16:30:00 Tower apcupsd[1899]: Power failure.
Sep 22 16:30:00 Tower apcupsd[1899]: Power is back. UPS running on mains.
Sep 22 16:30:00 Tower apcupsd[1899]: Power failure.
Sep 22 16:30:00 Tower apcupsd[1899]: Power is back. UPS running on mains.
Sep 22 16:30:01 Tower apcupsd[1899]: Power failure.
Sep 22 16:30:01 Tower apcupsd[1899]: Power is back. UPS running on mains.
Sep 22 16:30:01 Tower apcupsd[1899]: Power failure.
Sep 22 16:30:01 Tower apcupsd[1899]: Power is back. UPS running on mains.
Sep 22 16:30:02 Tower apcupsd[1899]: Power failure.
Sep 22 16:30:02 Tower apcupsd[1899]: Power is back. UPS running on mains.
Sep 22 16:30:03 Tower apcupsd[1899]: Power failure.
Sep 22 16:30:03 Tower apcupsd[1899]: Power is back. UPS running on mains.
Sep 22 16:30:03 Tower apcupsd[1899]: Power failure.
Sep 22 16:30:03 Tower apcupsd[1899]: Power is back. UPS running on mains.
Sep 22 16:30:04 Tower apcupsd[1899]: Power failure.
Sep 22 16:30:04 Tower apcupsd[1899]: Power is back. UPS running on mains.
Sep 22 16:30:04 Tower apcupsd[1899]: Power failure.
Sep 22 16:30:04 Tower apcupsd[1899]: Power is back. UPS running on mains.
Sep 22 16:30:05 Tower apcupsd[1899]: Power failure.
Sep 22 16:30:05 Tower apcupsd[1899]: Power is back. UPS running on mains.
Sep 22 16:30:05 Tower apcupsd[1899]: Power failure.
Sep 22 16:30:05 Tower apcupsd[1899]: Power is back. UPS running on mains.
Sep 22 16:30:06 Tower apcupsd[1899]: Power failure.
Sep 22 16:30:06 Tower apcupsd[1899]: Power is back. UPS running on mains.
Sep 22 16:30:06 Tower apcupsd[1899]: Power failure.
Sep 22 16:30:06 Tower apcupsd[1899]: Power is back. UPS running on mains.
Sep 22 16:30:07 Tower apcupsd[1899]: Power failure.
Sep 22 16:30:07 Tower apcupsd[1899]: Power is back. UPS running on mains.
Sep 22 16:30:08 Tower apcupsd[1899]: Power failure.
Sep 22 16:30:08 Tower apcupsd[1899]: Power is back. UPS running on mains.
Sep 22 16:30:08 Tower apcupsd[1899]: Power failure.
Sep 22 16:30:08 Tower apcupsd[1899]: Power is back. UPS running on mains.
Sep 22 16:30:09 Tower apcupsd[1899]: Power failure.
Sep 22 16:30:09 Tower apcupsd[1899]: Power is back. UPS running on mains.
Sep 22 16:30:09 Tower apcupsd[1899]: Power failure.
Sep 22 16:30:09 Tower apcupsd[1899]: Power is back. UPS running on mains.
Sep 22 16:30:10 Tower apcupsd[1899]: Power failure.
Sep 22 16:30:10 Tower apcupsd[1899]: Power is back. UPS running on mains.
Sep 22 16:30:10 Tower apcupsd[1899]: Power failure.
Sep 22 16:30:10 Tower apcupsd[1899]: Power is back. UPS running on mains.
Sep 22 16:30:11 Tower apcupsd[1899]: Power failure.
Sep 22 16:30:11 Tower apcupsd[1899]: Power is back. UPS running on mains.
Sep 22 16:30:11 Tower apcupsd[1899]: Power failure.
Sep 22 16:30:11 Tower apcupsd[1899]: Power is back. UPS running on mains.
Sep 22 16:30:12 Tower apcupsd[1899]: Power failure.

in the logfile.

 

I don't recall having seen the repeated messages in the past.

 

The K*.sh scripts are copied from the flash to the ram fs when the plugin is installed.  Editing the script on the flash is not live - they are only source copies.  To make them operate on the next powerdown, go to a cli and type '/etc/rc.d/rc.unRAID update' to move the scripts from the flash to the ram fs.

The power cut early this morning occured, I think, before the parity check had completed:

Sep 23 06:36:35 Tower kernel: md: md_do_sync: got signal, exit...
Sep 23 06:36:36 Tower kernel: md: recovery thread sync completion status: -4

 

However, it should have passed the end of my largest data drive (2TB) and gone into the unised part of the parity drive (3TB).  There ar no log entries for any corrected sectors.

 

The powerdown was clean, so no new parity check!  :)

 

However, there are still many repeated power failure messages from apcupsd:

Sep 23 06:30:25 Tower apcupsd[1867]: Power failure.
Sep 23 06:30:25 Tower apcupsd[1867]: Power is back. UPS running on mains.
Sep 23 06:30:26 Tower apcupsd[1867]: Power failure.
Sep 23 06:30:26 Tower apcupsd[1867]: Power is back. UPS running on mains.
Sep 23 06:30:26 Tower apcupsd[1867]: Power failure.
Sep 23 06:30:26 Tower apcupsd[1867]: Power is back. UPS running on mains.
Sep 23 06:30:27 Tower apcupsd[1867]: Power failure.
Sep 23 06:30:27 Tower apcupsd[1867]: Power is back. UPS running on mains.
Sep 23 06:30:27 Tower apcupsd[1867]: Power failure.
Sep 23 06:30:27 Tower apcupsd[1867]: Power is back. UPS running on mains.
Sep 23 06:30:28 Tower apcupsd[1867]: Power failure.
Sep 23 06:30:28 Tower apcupsd[1867]: Power is back. UPS running on mains.
Sep 23 06:30:28 Tower apcupsd[1867]: Power failure.
Sep 23 06:30:28 Tower apcupsd[1867]: Power is back. UPS running on mains.
Sep 23 06:30:29 Tower apcupsd[1867]: Power failure.
Sep 23 06:30:29 Tower apcupsd[1867]: Power is back. UPS running on mains.
Sep 23 06:30:29 Tower apcupsd[1867]: Power failure.
Sep 23 06:30:29 Tower apcupsd[1867]: Power is back. UPS running on mains.
Sep 23 06:30:30 Tower apcupsd[1867]: Power failure.
Sep 23 06:30:30 Tower apcupsd[1867]: Power is back. UPS running on mains.
Sep 23 06:30:30 Tower apcupsd[1867]: Power failure.
Sep 23 06:30:30 Tower apcupsd[1867]: Power is back. UPS running on mains.
Sep 23 06:30:31 Tower apcupsd[1867]: Power failure.
Sep 23 06:30:31 Tower apcupsd[1867]: Power is back. UPS running on mains.
Sep 23 06:30:32 Tower apcupsd[1867]: Power failure.
Sep 23 06:30:32 Tower apcupsd[1867]: Power is back. UPS running on mains.
Sep 23 06:30:32 Tower apcupsd[1867]: Power failure.
Sep 23 06:30:32 Tower apcupsd[1867]: Power is back. UPS running on mains.
Sep 23 06:30:33 Tower apcupsd[1867]: Power failure.
Sep 23 06:30:33 Tower apcupsd[1867]: Power is back. UPS running on mains.
Sep 23 06:30:33 Tower apcupsd[1867]: Power failure.
Sep 23 06:30:33 Tower apcupsd[1867]: Power is back. UPS running on mains.
Sep 23 06:30:34 Tower apcupsd[1867]: Power failure.
Sep 23 06:30:34 Tower apcupsd[1867]: Power is back. UPS running on mains.
Sep 23 06:30:34 Tower apcupsd[1867]: Power failure.
Sep 23 06:30:34 Tower apcupsd[1867]: Power is back. UPS running on mains.
Sep 23 06:30:35 Tower apcupsd[1867]: Power failure.
Sep 23 06:30:35 Tower apcupsd[1867]: Power is back. UPS running on mains.
Sep 23 06:30:35 Tower apcupsd[1867]: Power failure.
Sep 23 06:30:35 Tower apcupsd[1867]: Power is back. UPS running on mains.
Sep 23 06:30:36 Tower apcupsd[1867]: Power failure.
Sep 23 06:30:36 Tower apcupsd[1867]: Power is back. UPS running on mains.
Sep 23 06:30:37 Tower apcupsd[1867]: Power failure.
Sep 23 06:30:37 Tower apcupsd[1867]: Power is back. UPS running on mains.
Sep 23 06:30:37 Tower apcupsd[1867]: Power failure.
Sep 23 06:30:37 Tower apcupsd[1867]: Power is back. UPS running on mains.
Sep 23 06:30:38 Tower apcupsd[1867]: Power failure.
Sep 23 06:30:38 Tower apcupsd[1867]: Power is back. UPS running on mains.
Sep 23 06:30:38 Tower apcupsd[1867]: Power failure.
Sep 23 06:30:38 Tower apcupsd[1867]: Power is back. UPS running on mains.
Sep 23 06:30:39 Tower apcupsd[1867]: Power failure.
Sep 23 06:30:39 Tower apcupsd[1867]: Power is back. UPS running on mains.
Sep 23 06:30:39 Tower apcupsd[1867]: Power failure.
Sep 23 06:30:39 Tower apcupsd[1867]: Power is back. UPS running on mains.
Sep 23 06:30:40 Tower apcupsd[1867]: Power failure.
Sep 23 06:30:40 Tower apcupsd[1867]: Power is back. UPS running on mains.
Sep 23 06:30:40 Tower apcupsd[1867]: Power failure.
Sep 23 06:30:40 Tower apcupsd[1867]: Power is back. UPS running on mains.
Sep 23 06:30:41 Tower apcupsd[1867]: Power failure.
Sep 23 06:30:41 Tower apcupsd[1867]: Power is back. UPS running on mains.
Sep 23 06:30:42 Tower apcupsd[1867]: Power failure.
Sep 23 06:30:42 Tower apcupsd[1867]: Power is back. UPS running on mains.
Sep 23 06:30:42 Tower apcupsd[1867]: Power failure.
Sep 23 06:30:42 Tower apcupsd[1867]: Power is back. UPS running on mains.
Sep 23 06:30:43 Tower apcupsd[1867]: Power failure.
Sep 23 06:30:43 Tower apcupsd[1867]: Power is back. UPS running on mains.
Sep 23 06:30:43 Tower apcupsd[1867]: Power failure.
Sep 23 06:30:43 Tower apcupsd[1867]: Power is back. UPS running on mains.
Sep 23 06:30:44 Tower apcupsd[1867]: Power failure.
Sep 23 06:30:44 Tower apcupsd[1867]: Power is back. UPS running on mains.
Sep 23 06:30:44 Tower apcupsd[1867]: Power failure.
Sep 23 06:30:44 Tower apcupsd[1867]: Power is back. UPS running on mains.
Sep 23 06:30:45 Tower apcupsd[1867]: Power failure.
Sep 23 06:30:45 Tower apcupsd[1867]: Power is back. UPS running on mains.
Sep 23 06:30:45 Tower apcupsd[1867]: Power failure.
Sep 23 06:30:45 Tower apcupsd[1867]: Power is back. UPS running on mains.
Sep 23 06:30:46 Tower apcupsd[1867]: Power failure.
Sep 23 06:30:46 Tower apcupsd[1867]: Power is back. UPS running on mains.
Sep 23 06:30:47 Tower apcupsd[1867]: Power failure.
Sep 23 06:30:47 Tower apcupsd[1867]: Power is back. UPS running on mains.
Sep 23 06:30:47 Tower apcupsd[1867]: Power failure.
Sep 23 06:30:47 Tower apcupsd[1867]: Power is back. UPS running on mains.
Sep 23 06:30:48 Tower apcupsd[1867]: Power failure.
Sep 23 06:30:48 Tower apcupsd[1867]: Power is back. UPS running on mains.
Sep 23 06:30:48 Tower apcupsd[1867]: Power failure.
Sep 23 06:30:48 Tower apcupsd[1867]: Power is back. UPS running on mains.
Sep 23 06:30:49 Tower apcupsd[1867]: Power failure.
Sep 23 06:30:49 Tower apcupsd[1867]: Power is back. UPS running on mains.
Sep 23 06:30:49 Tower apcupsd[1867]: Power failure.
Sep 23 06:30:49 Tower apcupsd[1867]: Power is back. UPS running on mains.
Sep 23 06:30:50 Tower apcupsd[1867]: Power failure.
Sep 23 06:30:50 Tower apcupsd[1867]: Power is back. UPS running on mains.
Sep 23 06:30:50 Tower apcupsd[1867]: Power failure.
Sep 23 06:30:50 Tower apcupsd[1867]: Power is back. UPS running on mains.
Sep 23 06:30:51 Tower apcupsd[1867]: Power failure.
Sep 23 06:30:51 Tower apcupsd[1867]: Power is back. UPS running on mains.
Sep 23 06:30:52 Tower apcupsd[1867]: Power failure.
Sep 23 06:30:52 Tower apcupsd[1867]: Power is back. UPS running on mains.
Sep 23 06:30:52 Tower apcupsd[1867]: Power failure.
Sep 23 06:30:52 Tower apcupsd[1867]: Power is back. UPS running on mains.
Sep 23 06:30:53 Tower apcupsd[1867]: Power failure.

 

Do the same messages occur if you simulate a power failure using the lamp method (unRAID plugged into mains, lamp into ups, then unplug the ups from mains)?

 

  • Author

Looks like a low mains voltage (brownout?).

Looks like a low mains voltage (brownout?).

 

Yes, that was my first thought ... but going on and off twice per second, for almost 30 seconds....  ???  I've been running the apcupsd package/plugin on unRAID for three years, and haven't seen this happen before, until last week.

 

Here is an extract of the apcupsd.events log for another system (a Raspberry Pi, running ArchLinux), covering the same power outage:

2014-09-22 17:43:25 +0800  Power is back. UPS running on mains.
2014-09-23 06:30:25 +0800  Power failure.
2014-09-23 06:30:30 +0800  Running on UPS batteries.
2014-09-23 07:52:26 +0800  Mains returned. No longer on UPS batteries.
2014-09-23 07:52:26 +0800  Power is back. UPS running on mains.

Same ups?

Same ups?

 

Nope.  But I've never seen the issue on either system before last week, and with an average of 2 power cuts a day for the last three years, I would think that I would have noticed it before!

 

Either the nature of our power cuts has changed, the behaviour of the UPS has changed, or the behaviour of apcupsd has changed.

  • Author

Same ups?

 

Nope.  But I've never seen the issue on either system before last week, and with an average of 2 power cuts a day for the last three years, I would think that I would have noticed it before!

 

Either the nature of our power cuts has changed, the behaviour of the UPS has changed, or the behaviour of apcupsd has changed.

 

Apcupsd only reports what the UPS tells it.  Maybe you have the sensitivity set too high on the UPS.  I set mine to 'Medium' to keep that from happening too much.  The 'High' setting is pretty sensitive to voltage fluctuations and will transfer to battery power a lot.  APC recommends the 'Medium' setting if the UPS goes on battery power too often from dirty power.

Archived

This topic is now archived and is closed to further replies.

Go to topic listing

Account

Navigation

Search

Search

Configure browser push notifications
Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.