Red Hat Bugzilla – Bug 458465
RHEL4: qpidd server fails to start -- Data directory is locked by another process:
Last modified: 2008-10-06 14:59:47 EDT
+++ This bug was initially created as a clone of Bug #458401 +++
Description of problem:
Startup of the qpidd service fails with:
[root@xxx]: /etc/init.d/qpidd start
Starting Qpid AMQP daemon: Daemon startup failed: Data directory is locked by another process: /var/lib/qpidd
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. 'service qpidd start'
2. reach over and un-plug the machine (force a crash)
3. after re-booting, the qpidd service refuses to start
The init scripts should somehow (?) realize that its a stale lock.
--- Additional comment from email@example.com on 2008-08-08 10:15:52 EDT ---
After reading "src/qpid/DataDir.cpp" its obvious that:
is a work-around for this problem. But its *not* an actual fix. Most
users are not prepared to read C++ to figure out how to get the qpidd
running after a system crash.
I think the real fix is to modify the /etc/init.d/qpidd startup script
0) it uses the $pidfile so it *knows* whether a qpidd process is
actually running or not
1) if qpidd is not running, then delete the /var/lib/qpidd/lock
before trying to start a new one
Verified manually and also using RHTS test (MRG_Messaging/qpid_start_fails_bz458466) which proves it on different machines. (ON_QA->VERIFIED)
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.