qpidd starting displays Failed chown: cannot access `/var/suraj/apigee4/var/lock/subsys/qpidd': No such file or

asurajpai
Participant V

While starting on the qpidd profile server in a 13 node instance using ./all-start.sh I get the following error.

mo-34a6a7165:/var/suraj/apigee4/bin # ./all-start.sh
Starting Datastore, Edge and API Backend
Starting qpidd Checking if qpidd is up. ....................................... Last chance. Waiting 2 minutes longer. 
Failed chown: cannot access `/var/suraj/apigee4/var/lock/subsys/qpidd': No such file or Starting apigee-qpid-server 
Checking if apigee-qpid-server is up. Connection to 172.18.0.172 8083 port [tcp/*] succeeded!
Success apigee-qpid-server is up.
Checking if we can get the qpid-server uuid: ................... 
Last chance. Waiting 2 minutes longer. 
qpid-server may have failed to start. 
Check /var/suraj/apigee4/var/log/apigee/qpid-server/logs/system.log for errors.

But the all-status.sh command displays all is ok as well as check.sh

mo-34a6a7165:/var/suraj/apigee4/bin # ./all-status.sh qpidd is not running qpid-server (pid 37450) is running... mo-34a6a7165:/var/suraj/apigee4/bin # ./check.sh

Check Processes: ----------------

qpidd is not running qpid-server (pid 37450) is running...

Check Services: ---------------

Qpid Server:

UUID=5d858acb-f0b8-4673-9031-f410534ca51b ==> 200

Please let me know if the qpidd has started correctly and why the initial error are coming.

BR, Suraj

0 1 375
1 REPLY 1

try this,

1. /var/suraj/apigee4/bin/all-stop.sh

2. check for any qpid process, ps -ef | grep qpid

3. Kill all of them you find in 2

4. then /var/suraj/apigee4/bin/all-start.sh