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.

UPS Shutdown Troubleshooting apcupsd

Featured Replies

I purchased an APC Back-UPS ES 550 to try and get going with unRAID.  I noticed a few other threads listing it as a cheap functional UPS to use.  The APC UPS is connected with a RJ-45 cable on the UPS end that converts to USB on the computer end.

 

So I have unMENU setup and used the package manager tab to install apcupsd.  Specifically: apcupsd-3.14.3-i486-1kjz.tgz

 

However after tweaking settings every way I still can't get it to shutdown unRAID (tried both "smart" and "usb" for cable type variables).  Looking through the syslog I see that the power loss is detected and the shutdown is initiated, however the system never shuts down, the last entry in the log is always "User logins prohibited" and then nothing else.

 

Here is the log:

Jul 23 23:27:05 Tower kernel: generic-usb 0003:051D:0002.0001: hiddev96,hidraw0: USB HID v1.10 Device [APC Back-UPS ES 550 FW:843.K2 .D USB FW:K2 ] on usb-0000:00:1d.2-2/input0

Jul 23 23:27:05 Tower kernel: i801_smbus 0000:00:1f.3: PCI INT B -> GSI 17 (level, low) -> IRQ 17

Jul 23 23:27:05 Tower kernel: scsi 2:0:0:0: Direct-Access Kingston DataTraveler 2.0 PMAP PQ: 0 ANSI: 0 CCS

Jul 23 23:27:05 Tower kernel: usb-storage: device scan complete

Jul 23 23:27:05 Tower kernel: sd 2:0:0:0: [sdc] 7837696 512-byte logical blocks: (4.01 GB/3.73 GiB)

Jul 23 23:27:05 Tower kernel: sd 2:0:0:0: [sdc] Write Protect is off

Jul 23 23:27:05 Tower kernel: sd 2:0:0:0: [sdc] Mode Sense: 23 00 00 00

Jul 23 23:27:05 Tower kernel: sd 2:0:0:0: [sdc] Assuming drive cache: write through

Jul 23 23:27:05 Tower kernel: sd 2:0:0:0: [sdc] Assuming drive cache: write through

Jul 23 23:27:05 Tower kernel: sdc: sdc1

Jul 23 23:27:05 Tower kernel: sd 2:0:0:0: [sdc] Assuming drive cache: write through

Jul 23 23:27:05 Tower kernel: sd 2:0:0:0: [sdc] Attached SCSI removable disk

Jul 23 23:27:05 Tower logger: /etc/rc.d/rc.inet1: /sbin/ifconfig lo 127.0.0.1

Jul 23 23:27:05 Tower logger: /etc/rc.d/rc.inet1: /sbin/route add -net 127.0.0.0 netmask 255.0.0.0 lo

Jul 23 23:27:05 Tower ifplugd(eth0)[1126]: ifplugd 0.28 initializing.

Jul 23 23:27:05 Tower ifplugd(eth0)[1126]: Using interface eth0/00:13:72:A6:0B:7D with driver (version: 3.102)

Jul 23 23:27:05 Tower ifplugd(eth0)[1126]: Using detection mode: SIOCETHTOOL

Jul 23 23:27:05 Tower ifplugd(eth0)[1126]: Initialization complete, link beat not detected.

Jul 23 23:27:05 Tower rpc.statd[1138]: Version 1.1.4 Starting

Jul 23 23:27:05 Tower emhttp: unRAID System Management Utility version 4.5.6

Jul 23 23:27:05 Tower emhttp: Copyright © 2005-2010, Lime Technology, LLC

Jul 23 23:27:05 Tower emhttp: Basic key detected, GUID:

Jul 23 23:27:05 Tower emhttp: shcmd (1): udevadm settle

Jul 23 23:27:05 Tower emhttp: Device inventory:

Jul 23 23:27:05 Tower emhttp: pci-0000:00:1f.2-scsi-0:0:0:0 host0 (sda) MAXTOR_STM3500630AS_6QG1QQS3

Jul 23 23:27:05 Tower emhttp: pci-0000:00:1f.2-scsi-0:0:1:0 host0 (sdb) ST3500641AS_3PM0V967

Jul 23 23:27:05 Tower emhttp: shcmd (2): modprobe -rw md-mod 2>&1 | logger

Jul 23 23:27:05 Tower emhttp: shcmd (3): modprobe md-mod super=/boot/config/super.dat slots=8,0,8,16,0,0 2>&1 | logger

Jul 23 23:27:05 Tower kernel: xor: automatically using best checksumming function: pIII_sse

Jul 23 23:27:05 Tower kernel: pIII_sse : 4859.200 MB/sec

Jul 23 23:27:05 Tower kernel: xor: using function: pIII_sse (4859.200 MB/sec)

Jul 23 23:27:05 Tower emhttp: Spinning up all drives...

Jul 23 23:27:05 Tower kernel: md: unRAID driver 0.95.4 installed

Jul 23 23:27:05 Tower kernel: read_file: error 2 opening /boot/config/super.dat

Jul 23 23:27:05 Tower kernel: md: could not read superblock from /boot/config/super.dat

Jul 23 23:27:05 Tower kernel: md: initializing superblock

Jul 23 23:27:05 Tower kernel: md: import disk0: [8,0] (sda) MAXTOR STM350063 6QG1QQS3 offset: 63 size: 488386552

Jul 23 23:27:05 Tower kernel: md: disk0 new disk

Jul 23 23:27:05 Tower kernel: md: import disk1: [8,16] (sdb) ST3500641AS 3PM0V967 offset: 63 size: 488386552

Jul 23 23:27:05 Tower kernel: md: disk1 new disk

Jul 23 23:27:05 Tower kernel: mdcmd (2): set md_num_stripes 1280

Jul 23 23:27:05 Tower kernel: mdcmd (3): set md_write_limit 768

Jul 23 23:27:05 Tower kernel: mdcmd (4): set md_sync_window 288

Jul 23 23:27:05 Tower kernel: mdcmd (5): set spinup_group 0 2

Jul 23 23:27:05 Tower kernel: mdcmd (6): set spinup_group 1 1

Jul 23 23:27:05 Tower kernel: mdcmd (7): spinup 0

Jul 23 23:27:05 Tower kernel: mdcmd (8): spinup 1

Jul 23 23:27:05 Tower emhttp: stale configuration

Jul 23 23:27:05 Tower emhttp: shcmd (4): rm /etc/samba/smb-shares.conf >/dev/null 2>&1

Jul 23 23:27:05 Tower emhttp: _shcmd: shcmd (4): exit status: 1

Jul 23 23:27:05 Tower emhttp: shcmd (5): cp /etc/exports- /etc/exports

Jul 23 23:27:05 Tower emhttp: shcmd (6): killall -HUP smbd

Jul 23 23:27:05 Tower emhttp: shcmd (7): /etc/rc.d/rc.nfsd restart | logger

Jul 23 23:27:06 Tower unmenu-status: Starting unmenu web-server

Jul 23 23:27:08 Tower kernel: tg3: eth0: Link is up at 1000 Mbps, full duplex.

Jul 23 23:27:08 Tower kernel: tg3: eth0: Flow control is on for TX and on for RX.

Jul 23 23:27:08 Tower ifplugd(eth0)[1126]: Link beat detected.

Jul 23 23:27:08 Tower apcupsd[1389]: apcupsd 3.14.3 (20 January 2008) slackware startup succeeded

Jul 23 23:27:08 Tower apcupsd[1389]: NIS server startup succeeded

Jul 23 23:27:09 Tower ifplugd(eth0)[1126]: Executing '/etc/ifplugd/ifplugd.action eth0 up'.

Jul 23 23:27:09 Tower ifplugd(eth0)[1126]: client: Polling for DHCP server on interface eth0:

Jul 23 23:27:10 Tower kernel: tg3 0000:02:00.0: PME# enabled

Jul 23 23:27:10 Tower logger: /etc/rc.d/rc.inet1: /sbin/dhcpcd -d -t 30 -h Tower eth0

Jul 23 23:27:10 Tower kernel: tg3 0000:02:00.0: PME# disabled

Jul 23 23:27:10 Tower dhcpcd[1456]: broadcasting DHCP_DISCOVER

Jul 23 23:27:13 Tower kernel: tg3: eth0: Link is up at 1000 Mbps, full duplex.

Jul 23 23:27:13 Tower kernel: tg3: eth0: Flow control is on for TX and on for RX.

Jul 23 23:27:15 Tower dhcpcd[1456]: broadcastAddr option is missing in DHCP server response. Assuming 192.168.1.255

Jul 23 23:27:15 Tower dhcpcd[1456]: dhcpIPaddrLeaseTime=86400 in DHCP server response.

Jul 23 23:27:15 Tower dhcpcd[1456]: dhcpT1value is missing in DHCP server response. Assuming 43200 sec

Jul 23 23:27:15 Tower dhcpcd[1456]: dhcpT2value is missing in DHCP server response. Assuming 75600 sec

Jul 23 23:27:15 Tower dhcpcd[1456]: DHCP_OFFER received from (192.168.1.1)

Jul 23 23:27:15 Tower dhcpcd[1456]: broadcasting DHCP_REQUEST for 192.168.1.108

Jul 23 23:27:15 Tower dhcpcd[1456]: dhcpIPaddrLeaseTime=86400 in DHCP server response.

Jul 23 23:27:15 Tower dhcpcd[1456]: dhcpT1value is missing in DHCP server response. Assuming 43200 sec

Jul 23 23:27:15 Tower dhcpcd[1456]: dhcpT2value is missing in DHCP server response. Assuming 75600 sec

Jul 23 23:27:15 Tower dhcpcd[1456]: DHCP_ACK received from (192.168.1.1)

Jul 23 23:27:15 Tower ifplugd(eth0)[1126]: client: dhcpcd: MAC address = 00:13:72:a6:0b:7d

Jul 23 23:27:15 Tower ifplugd(eth0)[1126]: client: dhcpcd: your IP address = 192.168.1.108

Jul 23 23:27:15 Tower ifplugd(eth0)[1126]: client: dhcpcd: MAC address = 00:13:72:a6:0b:7d

Jul 23 23:27:15 Tower ifplugd(eth0)[1126]: client: dhcpcd: your IP address = 192.168.1.108

Jul 23 23:27:15 Tower ifplugd(eth0)[1126]: Program executed successfully.

Jul 23 23:28:46 Tower apcupsd[1389]: Power failure.

Jul 23 23:28:52 Tower apcupsd[1389]: Running on UPS batteries.

Jul 23 23:28:52 Tower apcupsd[1389]: Reached remaining time percentage limit on batteries.

Jul 23 23:28:52 Tower apcupsd[1389]: Initiating system shutdown!

Jul 23 23:28:52 Tower apcupsd[1389]: User logins prohibited

I purchased an APC Back-UPS ES 550 to try and get going with unRAID.  I noticed a few other threads listing it as a cheap functional UPS to use.  The APC UPS is connected with a RJ-45 cable on the UPS end that converts to USB on the computer end.

 

So I have unMENU setup and used the package manager tab to install apcupsd.  Specifically: apcupsd-3.14.3-i486-1kjz.tgz

 

However after tweaking settings every way I still can't get it to shutdown unRAID (tried both "smart" and "usb" for cable type variables).  Looking through the syslog I see that the power loss is detected and the shutdown is initiated, however the system never shuts down, the last entry in the log is always "User logins prohibited" and then nothing else.

 

Here is the log:

Jul 23 23:27:05 Tower kernel: generic-usb 0003:051D:0002.0001: hiddev96,hidraw0: USB HID v1.10 Device [APC Back-UPS ES 550 FW:843.K2 .D USB FW:K2 ] on usb-0000:00:1d.2-2/input0

Jul 23 23:27:05 Tower kernel: i801_smbus 0000:00:1f.3: PCI INT B -> GSI 17 (level, low) -> IRQ 17

Jul 23 23:27:05 Tower kernel: scsi 2:0:0:0: Direct-Access Kingston DataTraveler 2.0 PMAP PQ: 0 ANSI: 0 CCS

Jul 23 23:27:05 Tower kernel: usb-storage: device scan complete

Jul 23 23:27:05 Tower kernel: sd 2:0:0:0: [sdc] 7837696 512-byte logical blocks: (4.01 GB/3.73 GiB)

Jul 23 23:27:05 Tower kernel: sd 2:0:0:0: [sdc] Write Protect is off

Jul 23 23:27:05 Tower kernel: sd 2:0:0:0: [sdc] Mode Sense: 23 00 00 00

Jul 23 23:27:05 Tower kernel: sd 2:0:0:0: [sdc] Assuming drive cache: write through

Jul 23 23:27:05 Tower kernel: sd 2:0:0:0: [sdc] Assuming drive cache: write through

Jul 23 23:27:05 Tower kernel: sdc: sdc1

Jul 23 23:27:05 Tower kernel: sd 2:0:0:0: [sdc] Assuming drive cache: write through

Jul 23 23:27:05 Tower kernel: sd 2:0:0:0: [sdc] Attached SCSI removable disk

Jul 23 23:27:05 Tower logger: /etc/rc.d/rc.inet1: /sbin/ifconfig lo 127.0.0.1

Jul 23 23:27:05 Tower logger: /etc/rc.d/rc.inet1: /sbin/route add -net 127.0.0.0 netmask 255.0.0.0 lo

Jul 23 23:27:05 Tower ifplugd(eth0)[1126]: ifplugd 0.28 initializing.

Jul 23 23:27:05 Tower ifplugd(eth0)[1126]: Using interface eth0/00:13:72:A6:0B:7D with driver (version: 3.102)

Jul 23 23:27:05 Tower ifplugd(eth0)[1126]: Using detection mode: SIOCETHTOOL

Jul 23 23:27:05 Tower ifplugd(eth0)[1126]: Initialization complete, link beat not detected.

Jul 23 23:27:05 Tower rpc.statd[1138]: Version 1.1.4 Starting

Jul 23 23:27:05 Tower emhttp: unRAID System Management Utility version 4.5.6

Jul 23 23:27:05 Tower emhttp: Copyright © 2005-2010, Lime Technology, LLC

Jul 23 23:27:05 Tower emhttp: Basic key detected, GUID:

Jul 23 23:27:05 Tower emhttp: shcmd (1): udevadm settle

Jul 23 23:27:05 Tower emhttp: Device inventory:

Jul 23 23:27:05 Tower emhttp: pci-0000:00:1f.2-scsi-0:0:0:0 host0 (sda) MAXTOR_STM3500630AS_6QG1QQS3

Jul 23 23:27:05 Tower emhttp: pci-0000:00:1f.2-scsi-0:0:1:0 host0 (sdb) ST3500641AS_3PM0V967

Jul 23 23:27:05 Tower emhttp: shcmd (2): modprobe -rw md-mod 2>&1 | logger

Jul 23 23:27:05 Tower emhttp: shcmd (3): modprobe md-mod super=/boot/config/super.dat slots=8,0,8,16,0,0 2>&1 | logger

Jul 23 23:27:05 Tower kernel: xor: automatically using best checksumming function: pIII_sse

Jul 23 23:27:05 Tower kernel: pIII_sse : 4859.200 MB/sec

Jul 23 23:27:05 Tower kernel: xor: using function: pIII_sse (4859.200 MB/sec)

Jul 23 23:27:05 Tower emhttp: Spinning up all drives...

Jul 23 23:27:05 Tower kernel: md: unRAID driver 0.95.4 installed

Jul 23 23:27:05 Tower kernel: read_file: error 2 opening /boot/config/super.dat

Jul 23 23:27:05 Tower kernel: md: could not read superblock from /boot/config/super.dat

Jul 23 23:27:05 Tower kernel: md: initializing superblock

Jul 23 23:27:05 Tower kernel: md: import disk0: [8,0] (sda) MAXTOR STM350063 6QG1QQS3 offset: 63 size: 488386552

Jul 23 23:27:05 Tower kernel: md: disk0 new disk

Jul 23 23:27:05 Tower kernel: md: import disk1: [8,16] (sdb) ST3500641AS 3PM0V967 offset: 63 size: 488386552

Jul 23 23:27:05 Tower kernel: md: disk1 new disk

Jul 23 23:27:05 Tower kernel: mdcmd (2): set md_num_stripes 1280

Jul 23 23:27:05 Tower kernel: mdcmd (3): set md_write_limit 768

Jul 23 23:27:05 Tower kernel: mdcmd (4): set md_sync_window 288

Jul 23 23:27:05 Tower kernel: mdcmd (5): set spinup_group 0 2

Jul 23 23:27:05 Tower kernel: mdcmd (6): set spinup_group 1 1

Jul 23 23:27:05 Tower kernel: mdcmd (7): spinup 0

Jul 23 23:27:05 Tower kernel: mdcmd (8): spinup 1

Jul 23 23:27:05 Tower emhttp: stale configuration

Jul 23 23:27:05 Tower emhttp: shcmd (4): rm /etc/samba/smb-shares.conf >/dev/null 2>&1

Jul 23 23:27:05 Tower emhttp: _shcmd: shcmd (4): exit status: 1

Jul 23 23:27:05 Tower emhttp: shcmd (5): cp /etc/exports- /etc/exports

Jul 23 23:27:05 Tower emhttp: shcmd (6): killall -HUP smbd

Jul 23 23:27:05 Tower emhttp: shcmd (7): /etc/rc.d/rc.nfsd restart | logger

Jul 23 23:27:06 Tower unmenu-status: Starting unmenu web-server

Jul 23 23:27:08 Tower kernel: tg3: eth0: Link is up at 1000 Mbps, full duplex.

Jul 23 23:27:08 Tower kernel: tg3: eth0: Flow control is on for TX and on for RX.

Jul 23 23:27:08 Tower ifplugd(eth0)[1126]: Link beat detected.

Jul 23 23:27:08 Tower apcupsd[1389]: apcupsd 3.14.3 (20 January 2008) slackware startup succeeded

Jul 23 23:27:08 Tower apcupsd[1389]: NIS server startup succeeded

Jul 23 23:27:09 Tower ifplugd(eth0)[1126]: Executing '/etc/ifplugd/ifplugd.action eth0 up'.

Jul 23 23:27:09 Tower ifplugd(eth0)[1126]: client: Polling for DHCP server on interface eth0:

Jul 23 23:27:10 Tower kernel: tg3 0000:02:00.0: PME# enabled

Jul 23 23:27:10 Tower logger: /etc/rc.d/rc.inet1: /sbin/dhcpcd -d -t 30 -h Tower eth0

Jul 23 23:27:10 Tower kernel: tg3 0000:02:00.0: PME# disabled

Jul 23 23:27:10 Tower dhcpcd[1456]: broadcasting DHCP_DISCOVER

Jul 23 23:27:13 Tower kernel: tg3: eth0: Link is up at 1000 Mbps, full duplex.

Jul 23 23:27:13 Tower kernel: tg3: eth0: Flow control is on for TX and on for RX.

Jul 23 23:27:15 Tower dhcpcd[1456]: broadcastAddr option is missing in DHCP server response. Assuming 192.168.1.255

Jul 23 23:27:15 Tower dhcpcd[1456]: dhcpIPaddrLeaseTime=86400 in DHCP server response.

Jul 23 23:27:15 Tower dhcpcd[1456]: dhcpT1value is missing in DHCP server response. Assuming 43200 sec

Jul 23 23:27:15 Tower dhcpcd[1456]: dhcpT2value is missing in DHCP server response. Assuming 75600 sec

Jul 23 23:27:15 Tower dhcpcd[1456]: DHCP_OFFER received from (192.168.1.1)

Jul 23 23:27:15 Tower dhcpcd[1456]: broadcasting DHCP_REQUEST for 192.168.1.108

Jul 23 23:27:15 Tower dhcpcd[1456]: dhcpIPaddrLeaseTime=86400 in DHCP server response.

Jul 23 23:27:15 Tower dhcpcd[1456]: dhcpT1value is missing in DHCP server response. Assuming 43200 sec

Jul 23 23:27:15 Tower dhcpcd[1456]: dhcpT2value is missing in DHCP server response. Assuming 75600 sec

Jul 23 23:27:15 Tower dhcpcd[1456]: DHCP_ACK received from (192.168.1.1)

Jul 23 23:27:15 Tower ifplugd(eth0)[1126]: client: dhcpcd: MAC address = 00:13:72:a6:0b:7d

Jul 23 23:27:15 Tower ifplugd(eth0)[1126]: client: dhcpcd: your IP address = 192.168.1.108

Jul 23 23:27:15 Tower ifplugd(eth0)[1126]: client: dhcpcd: MAC address = 00:13:72:a6:0b:7d

Jul 23 23:27:15 Tower ifplugd(eth0)[1126]: client: dhcpcd: your IP address = 192.168.1.108

Jul 23 23:27:15 Tower ifplugd(eth0)[1126]: Program executed successfully.

Jul 23 23:28:46 Tower apcupsd[1389]: Power failure.

Jul 23 23:28:52 Tower apcupsd[1389]: Running on UPS batteries.

Jul 23 23:28:52 Tower apcupsd[1389]: Reached remaining time percentage limit on batteries.

Jul 23 23:28:52 Tower apcupsd[1389]: Initiating system shutdown!

Jul 23 23:28:52 Tower apcupsd[1389]: User logins prohibited

before you go too crazy...

 

Do you have the "powerdown" package installed?  (I see no evidence of it in your syslog.) The package in unMENU depends on it to exist to shut down the server.

Do you have ACPI enabled in your BIOS?  (If not, nothing can power down your server)  To test, first "Stop" your array, then type

poweroff

If the server does not power itself off, then you do not have the BIOS setting enabled for ACPI.

The messages in the partial log you posted show the UPS itself is connected and working just fine.  Next time,attach the full log file to the post as an attachment. (zip it up if needed to make it smaller)

 

Joe L.

  • Author

Well poweroff was working but it was unRAID poweroff not unMENU poweroff  :-\.

 

Installed unMENU poweroff and bingo works .  Thanks  :)

 

Do you have the "powerdown" package installed?  (I see no evidence of it in your syslog.) The package in unMENU depends on it to exist to shut down the server.

Do you have ACPI enabled in your BIOS?  (If not, nothing can power down your server)  To test, first "Stop" your array, then type

poweroff

If the server does not power itself off, then you do not have the BIOS setting enabled for ACPI.

The messages in the partial log you posted show the UPS itself is connected and working just fine.  Next time,attach the full log file to the post as an attachment. (zip it up if needed to make it smaller)

 

Joe L.

 

I'm glad I saw this thread because I didn't have the "powerdown" package installed on my system either.  Thanks Joe!

Well poweroff was working but it was unRAID poweroff not unMENU poweroff  :-\.

 

Installed unMENU poweroff and bingo works .  Thanks  :)

Not "poweroff" since it does NOT cleanly shut down the server.

There are two "powerdown" commands.  One was added fairly recently by "lime-technology"  It is installed in /usr/local/sbin and basically pressed the button on the management interface.  It will NOT stop the server and NOT power down if any disk in the array is "busy."  It will wait for the disk to not be busy and then stop the array and power down.  If you just type "powerdown" you'll get the lime-tech version since it is first in the search path.  To get the powerdown package WeeboTech wrote (if you install it) you must use the full path to the command and type:

/sbin/powerdown

 

The original "powerdown" command was written by WeeboTech and it will terminate processes that are holding disks busy.  As I said it resides in /sbin/powerdown.

 

If you install the APC UPS package via unMENU you must also install WeeboTech's "powerdown" package available in the package-manager.  if you do not, the UPS will not be able to power down the server as it specifically invokes /sbin/powerdown.

 

Make sure you set both the APC UPS package and "powerdown" package to re-install on reboot.

 

Joe L.

Archived

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

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.