Can anyone help me with this error showing up my my syslog about apcupsd?  How do I fix it?

 

Jul 29 04:40:01 TODD-Svr apcupsd[15726]: Valid lock file for pid=1466, but not ours pid=15726

Jul 29 04:40:01 TODD-Svr apcupsd[15727]: Valid lock file for pid=1466, but not ours pid=15727

Jul 29 04:40:01 TODD-Svr apcupsd[15727]: 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)

Jul 29 04:40:01 TODD-Svr apcupsd[15727]: Valid lock file for pid=1466, but not ours pid=15727

Jul 29 04:40:01 TODD-Svr apcupsd[15727]: apcupsd error shutdown completed (Errors)

 

One thing I noticed is we had a few minute long power failure before this error appeared in the syslog.  I've been out of town since then, but my wife tells me we had several power failures while I was gone due to storms.  The system never shut down so it wasn't off long enough to drain the battery.  However I don't see the power failures recorded in the syslog like I did before the error first occurred.  I'm guessing this is connected?

 

Also, while I am asking what does this mean?

Jul 19 23:39:42 TODD-Svr unmenu[2249]: Precleared disk sdd not found in drivedb[] (Drive related)

Seems to pop up now and then in my syslog recently.  sdd is my parity drive.

 

Info about my system is accurate and up to date in my signature.

 

I attached the full syslog but don't see anything else related other than a similar instance of the same error.

 

 

 

 

Thanks for any help.

syslog-2012-08-03_1.txt

2nd half of syslog.  I havne't rebooted in a while so it's pretty big.

 

syslog-2012-08-03_2.txt

Any help with this error?

Any help with this error?

it is pretty clear.  You have several instances of apcupsd running.  (or rather, it appears one is running and you are attempting to start another)

 

Jul 29 04:40:01 TODD-Svr apcupsd[15726]: Valid lock file for pid=1466, but not ours pid=15726

Jul 29 04:40:01 TODD-Svr apcupsd[15727]: Valid lock file for pid=1466, but not ours pid=15727

Jul 29 04:40:01 TODD-Svr apcupsd[15727]: 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.

Jul 29 04:40:01 TODD-Svr apcupsd[15727]: Valid lock file for pid=1466, but not ours pid=15727

Jul 29 04:40:01 TODD-Svr apcupsd[15727]: apcupsd error shutdown completed

 

Stop apcupsd, then re-start it.  (apparently you tried starting it, and it complained it is already running) Or just stop the array and reboot

As far as unmenu complaining, it was not coded to deal with you swapping out disks.  Simply re-start it. (there is a button on the user-scripts page)

Any help with this error?

it is pretty clear.  You have several instances of apcupsd running.  (or rather, it appears one is running and you are attempting to start another)

 

Jul 29 04:40:01 TODD-Svr apcupsd[15726]: Valid lock file for pid=1466, but not ours pid=15726

Jul 29 04:40:01 TODD-Svr apcupsd[15727]: Valid lock file for pid=1466, but not ours pid=15727

Jul 29 04:40:01 TODD-Svr apcupsd[15727]: 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.

Jul 29 04:40:01 TODD-Svr apcupsd[15727]: Valid lock file for pid=1466, but not ours pid=15727

Jul 29 04:40:01 TODD-Svr apcupsd[15727]: apcupsd error shutdown completed

 

Stop apcupsd, then re-start it.  (apparently you tried starting it, and it complained it is already running) Or just stop the array and reboot

 

Unsure how I could have ended up with several instances of apcupsd running, but I did remove it, reboot, and reinstall it.  No errors since. 

 

I am unclear about your comment on me "swapping out discs" in the next response.  I have never made disc changes with the server running.  There would always be a shut down/start up involved. Can you explain further?