Server is not getting registered to broker and getting terminated during startup; with the following error: SYS>-EADDRINUSE-Address already in use

Products

• VMware Smart Assurance
• Network Observability

Issue/Introduction

Domain startup fails with the following error message is found in the log file:

[Date & Time>] t@<epoch> dmboot
CI-W-EWHILE-While executing function "HttpServer::_setupListener"
HTTP-FPF-No HTTP listener configured on IPv4, because:
CI-EWHILE-While executing function "open"
CI-EFLOWID-For flow CI_FlowTCP_U NOREAD|NOWRITE|PHYSICAL|ACCEPTOR @0x00007f824acfb290
. *:v4:39202* KS N/A, KR N/A
. Closed, conn N/A, disc <Date & Time>,
. {Unconnected} -> {Unconnected}, tmo End of time N/S 1/0
<SYS>-EADDRINUSE-Address already in use
CI-BINDFAIL-Unable to bind to local address '*:v4', port <Port>.
 
[Date & Time>] t@<epoch>  dmboot
HTTP-E-NOFLOW-Could not create any listener flows (see log for details); in file "/work/redcurrent/DMT-9.4.1.0/13/smarts/http/sm_httpd.c" at line 639

Environment

Smarts 10.1.X , 24.3.X

Cause

The service startup command explains the error:

Example uses --port=39202

sm_server --name=<Domain Example OI> --config=icoi --port=39202 --ignore-restore-errors --clean-topology  --output 

Error points to the same port:

Example:

<SYS>-EADDRINUSE-Address already in use
CI-BINDFAIL-Unable to bind to local address '*:v4', port 39202.

So, the logs indicates that the server was terminated during startup. The port 39202 - used by the sm_server was already in use by some other process; Since the sm_server is started with --port=39202 option and the port was not available, the sm_server has exited with the above error.

Resolution

• Check the running process on port <Port> 

Example: netstat -anlp | grep -i 39202

• Stop the already running sm_server process (if any already running on this port) 
• If the process running on this port is crucial and cannot be changed, try using a different port for the sm_server
  
  

Additional Information

Also check if the startup command has --noregister, this will not register domain to broker, though it might be up and running fine, giving the impression that the service is down/unregistered on broker.

Information about no-register is available at sm_server --help section as follows:
--noregister            Do not register the server with the Broker.