CB Response: cbcluster start timeout failure after adding node to cluster

Products

• Carbon Black EDR (formerly Cb Response)

Issue/Introduction

• After adding a new node to the cluster, services timeout when attempting to run /usr/share/cbcluster start
• /var/log/cb/datagrid/debug.log contains: 

  Wrong bind request from [192.168.103.38]:5701! This node is not requested endpoint: [192.168.103.41]:5701

Environment

• CB Response 6.x: All Supported Versions

Cause

ClusterNodeId has been duplicated across the nodes' /etc/cb/cb.conf

Resolution

Ensure that ClusterNodeId is set to the same value as /etc/cb/cluster.conf for each node.

Additional Information

To find the current value of ClusterNodeId on each minion, run:

grep "ClusterNodeId" /etc/cb/cb.conf