EDR: 7.x EDR Server Cluster Fails to start/stop/status without CTRL+C

[#1]

Environment

• EDR Server: 7.2, 7.3

Symptoms

• Upon usage of the /usr/share/cb/cbcluster start/stop/status command, script hangs and must be stopped via ctrl + c.  Once the command is killed the services appear to be running/stopped without issue.
• Exception received after pressing ctrl + c on /usr/share/cb/cbcluster <command> usage:

Node[ 1 ] Connecting to sample1.carbonblack.com...

Node[ 2 ] Connecting to sample2.carbonblack.com...

Node[ 3] Connecting to sample3.carbonblack.com...

^CException ignored in: <Finalize object, dead>
Traceback (most recent call last):
Process ForkPoolWorker-7:

File "/usr/lib64/python3.8/multiprocessing/util.py", line 201, in __call__

Process ForkPoolWorker-4:

res = self._callback(*self._args, **self._kwargs)
File "/usr/lib64/python3.8/multiprocessing/pool.py", line 689, in _terminate_pool

Process ForkPoolWorker-5:

 

Cause

• This does not effect all EDR installations, but the reporting back to the master does not appear to confirm services running on both master and minion(s).

Resolution

• Reach out to VMWare CB Support for remediation, referencing this KB article.