Re: apcupsd lock file error

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



david walcroft wrote:
Hi,
  Would anyone tell me what needs to be done to fix this lockfile

Sun Feb 12 16:19:04 EST 2006 Valid lock file for pid=2296, but not ours pid=21621
Sun Feb 12 16:19:04 EST 2006  apcupsd FATAL ERROR in apcdevice.c at line 77
Unable to create UPS lock file.
Sun Feb 12 16:19:04 EST 2006 Valid lock file for pid=2296, but not ours pid=21621
Sun Feb 12 16:19:04 EST 2006  apcupsd error shutdown completed
Sun Feb 12 16:20:38 EST 2006 Valid lock file for pid=2296, but not ours pid=21942
Sun Feb 12 16:20:38 EST 2006  apcupsd FATAL ERROR in apcdevice.c at line 77
Unable to create UPS lock file.
Sun Feb 12 16:20:38 EST 2006 Valid lock file for pid=2296, but not ours pid=21942
Sun Feb 12 16:20:38 EST 2006  apcupsd error shutdown completed

I can't find "apcdevice.c" it's probably a binary and I'm hopeless at
It's probably the source file and the problem was detected at line 77 therein.

binary.
But 'ls /var/lock/subsys/apcupsd' exists.

Make sure the program isn't running:
ps xa | egrep apc[u]
Kill it if it is.

Delete the offending file:
rm -f /var/lock/subsys/apcupsd
Start the program using its startup script.

You could also search around and check that the file gets deleted when the program is stopped normally and when it fails to start: failing either is just cause to report a bug.

--

Cheers
John

-- spambait
1aaaaaaa@xxxxxxxxxxxxxxxxxxxxxxx  Z1aaaaaaa@xxxxxxxxxxxxxxxxxxxxxxx
Tourist pics http://portgeographe.environmentaldisasters.cds.merseine.nu/

do not reply off-list


[Index of Archives]     [Current Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]     [Fedora Docs]

  Powered by Linux