Access official resources from Carbon Black experts
This solution applies to Carbon Black 5.0 Patch 2 (220.127.116.11428.1537) and v5.1 (150625.0500).
The /usr/share/cb/cbcluster script hangs during a cbcluster service start.
Attempting to start the cluster on the master may cause the script to hang. Some services on the Master will report as dead or not running, while the minions are unaffected.
As of this writing (08/06/2015), a permanent solution does not exist. There are currently three scenarios that cause the cluster start script to hang:
1. On the Master server, ensure that there is not a hidden scrub_cbmodules file:
ls -la /etc/cb/.scrub_cbmodules
1a. If the above file exists, please remove it.
rm -f /etc/cb/.scrub_cbmodules
2. On the Master server, ensure there is not a CbTools process running:
ps -ef|grep CbTools
2a. If the above process is running, kill it manually.
kill -9 <PID> (where PID is left over CbTools process on the MASTER)
3. Start the cluster and ensure it is no longer hanging.
Please follow solution 871 to resolve the issue.
Scenario 3: Workaround using cb-enterprise start.
1. On the Master server, stop and start the cluster:
/usr/share/cb/cbcluster stop /usr/share/cb/cbcluster start
2. When the script hangs, verify all services are running on all minions:
service cb-enterprise status
3. Once they are, break out of the script on the Master server:
Ctrl + c
4. On the Master server, run these commands to remove PID and LOCK files, then start the cb-rabbitmq service:
rm -rf /var/run/cb/rabbitmq/pidrm -rf /var/lock/subsys/cb-rabbitmqservice cb-rabbitmq start
rm -rf /var/run/cb/rabbitmq/pid
rm -rf /var/lock/subsys/cb-rabbitmq
service cb-rabbitmq start
5. Verify all services are running and then test CB UI functionality:
Please create a support case if you've encountered this issue for tracking and diagnosis.
Copyright © 2005-2023 Broadcom. All Rights Reserved. The term “Broadcom” refers to Broadcom Inc. and/or its subsidiaries.