Well...I've been running fine for ~6 months now with a APC Back-UPS ES 550, and I noticed these lines in the syslog the other day:

Apr  3 04:40:01 Tower apcupsd[1645]: apcupsd exiting, signal 15

Apr  3 04:40:01 Tower apcupsd[9249]: Valid lock file for pid=1645, but not ours pid=9249

Apr  3 04:40:01 Tower apcupsd[9250]: Valid lock file for pid=1645, but not ours pid=9250

Apr  3 04:40:01 Tower apcupsd[9250]: apcupsd FATAL ERROR in device.c at line 71 Unable to create UPS lock file.   If apcupsd or apctest is already running,   please stop it and run this program again.  (Errors)

Apr  3 04:40:01 Tower apcupsd[9250]: Valid lock file for pid=1645, but not ours pid=9250

Apr  3 04:40:01 Tower apcupsd[9250]: apcupsd error shutdown completed (Errors)

 

First, what caused this?  And how can I restart apcupsd?  Will a simple restart of the server clear this error?

 

APCUPSD Version:  3.14.8

 

I did read this warning in the unMENU package manager, but wasn't certain it was still valid:

Several users have reported that this version of apcupsd stops responding to status requests after a period of time. For that reason, unless you need some feature added or fixed in this version, the older 3.14.3 version is the better choice. This newer version is here if you wish to give it a try and take the risk of it not responding.

I guess I took the risk...and failed.

 

 

I did switch USB ports as you can see from this syslog entry (after the failure), and it recognized my UPS.

Apr  5 19:18:07 Tower kernel: generic-usb 0003:051D:0002.0002: hiddev96,hidraw0: USB HID v1.10 Device [APC Back-UPS ES 550 FW:843.K2 .D USB FW:K2 ] on usb-0000:00:12.1-1/input0 (Drive related)

 

Thank you for the help.

 

Edit:  About 5 days prior to this I disassembled by server and added a drive (may have put USB cable on another port).

Edit2:  The server restarted from a power outage on 4/1.

 

syslog-2011-04-05.txt

This appears to be the problem:

 

http://www.linuxquestions.org/questions/linux-software-2/apcupsd-unable-to-create-ups-lock-file-196444/

This appears to be the problem:

 

http://www.linuxquestions.org/questions/linux-software-2/apcupsd-unable-to-create-ups-lock-file-196444/

 

I can't see how this can be the problem on unRAID.  /var is on ramdisk - it cannot survive a reboot.

 

I would also comment that I've noticed APCUPSD v3.14.3 sometimes fails to invoke a clean shutdown when the power fails.  Is it certain that the problem reported against v3.14.8 doesn't also afflict v3.14.3?