cb-enterprise Times Out Waiting for RabbitMQ to Initialize.

Products

• Carbon Black EDR

Issue/Introduction

cb-enterprise fails to startup with cb-rabbitmq waiting to initialize. journalctl shows this message.  

Mar 27 14:36:58 localhost.localdomain cb-enterprise[81197]: Starting cb-supervisord (via systemctl):  [  OK  ]
Mar 27 14:37:07 localhost.localdomain cb-enterprise[81226]: Starting cb-pgsql:                                         [  OK  ]
Mar 27 14:37:15 localhost.localdomain cb-enterprise[81278]: Starting cb-datagrid:                                      [  OK  ]
Mar 27 14:37:25 localhost.localdomain cb-enterprise[81377]: Starting cb-redis:                                         [  OK  ]
Mar 27 14:37:38 localhost.localdomain cb-enterprise[81404]: Starting cb-rabbitmq:                                      [FAILED]
Mar 27 14:44:01 localhost.localdomain systemd[1]: cb-enterprise.service: start operation timed out. Terminating.
Mar 27 14:44:01 localhost.localdomain cb-enterprise[80941]: Waiting for cb-rabbitmq to initialize...........
Mar 27 14:44:01 localhost.localdomain systemd[1]: cb-enterprise.service: Failed with result 'timeout'.

/var/log/cb/rabbitmq/startup_log shows this message. 

2025-03-27 14:53:18.450291-04:00 [error] <0.131.0> ERROR: node with name "rabbit" is already running on host "CB-SERVER-CLUSTER-HEAD-NODE"

Environment

• Carbon Black EDR Server: All Versions

Cause

rabbitmq-server has been started up outside of Carbon Black.  

Resolution

1. Stop the incorrect rabbitmq-server service. 

   systemctl stop rabbitmq-server

2. Verify the service is not set to start at boot, if they are disable the service. 

   systemctl is-enabled rabbitmq-server
   systemctl disable rabbitmq-server

3. Run this command to reset systemctl 

   systemctl reset-failed

4. Stop then start the EDR services again. 

Additional Information

• Carbon Black EDR process for RabbitMQ is cb-rabbitmq, this service is run by the cb user.