Run brcontrol add_dm lead to broker crash, and GUI cannot find broker when broker is up

Products

• VMware Smart Assurance

Issue/Introduction

1. When the broker is up, and you try to run below command:

    /opt/InCharge/SAM/smarts/bin/brcontrol add_dm <OI-Domain> <host> <pid> <port>

   It returns below error and broker gets crashed immediately:

[August 7, 2025 7:36:12 PM GMT+00:00 +178ms] t@1011865408 <Primary Thread>
CI-E-EWHILE-While executing function "fillRead"
 CI-EFLOWID-For flow CI_FlowBufferedHead_U [Remote API connection] HEAD|BUFFERED @0x000000000091d3e0
.
.
.
  . ##.##.##.##:<broker_port>KS August 7, 2025 7:36:05 PM GMT+00:00 +572ms, KR August 7, 2025 7:35:40 PM GMT+00:00 +551ms F:0
  . Open fd=8, conn August 7, 2025 7:35:41 PM GMT+00:00, disc N/A,
  . ##.##.##.##:<OI_port>-> ##.##.##.##:<Broker_port>, tmo 0 00:05:00 N/S 1/2
 CI-EWHILEREAD-After reading "0" bytes of "2048" (CI_FlowTCP_U)
 <SYS>-ECONNRESET-Connection reset by peer; in file "/work/redcurrent/DMT-9.4.2.0/10/smarts/clsapi/ci_flow.c" at line 2704

2. In OI domain log you found below error:

[August 7, 2025 at 7:52:08 PM UTC +445ms] t@1677719296 SM_RestartableServer reconnects #1
CI-E-EFLOWID-For flow CI_FlowBufferedHead_U [Client Buffered Head] HEAD|BUFFERED @0x00007f4a6804e870
.
.
.
  . ##.##.##.##:<Broker_port>KS N/A, KR N/A
 CI-IPCONN-##.##.##.##: <SYS>-E-ECONNREFUSED-Connection refused
 CI-CONNFAIL-Unable to connect to host '##.##.##.##', port <Broker_port>.

 

3. However, when you try to restart OI domain with below command it can be registered to broker successfully, so it is add_dm not working

   /opt/InCharge/SAM/smarts/bin/sm_server -n <OI-Domain> --config=icoi --port=0 --output --daemon --ignore-restore-errors --loglevel=Critical

 

4. Also, you found when broker is up on ##.##.##.##:426, SMARTS GUI client cannot find the broker running.

Environment

All supported releases of Smarts

Resolution

• Check if you have a customized sm_authority script linking to your LDAP server.

• This issue might occur if the LDAP server is not responding.

• Disable the LDAP and then only use defualt sm_authority. Raise a case with Broadcom support if this does not resolve this issue.