Environment
- EDR Server: Version 6.x and Higher (formerly CB Response)
Symptoms
- cbcluster start results in Exec failure (1)
- /var/cb/.erlang.cookie eacess errors are present in rabbitmq logs
Cause
- cb-rabbitmq utilizes .erlang.cookie to verify nodes at startup and it has become unusable
Resolution
- Delete /var/cb/.erlang.cookie if it exists
- Make sure home directory of user cb is correct in /etc/passwd
- Restart services
Additional Notes
If cb-enterprise continues to fail on nodes of the cluster, confirm the permissions on the mnesia directory of the affected node(s) are the same as on nodes where cb-enterprise started successfully.