Server Manager command-line : "Handshake Failed" for newly installed Siebel Server
(Doc ID 1551471.1)
Last updated on JANUARY 29, 2022
Applies to:Siebel CRM - Version 184.108.40.206  and later
Information in this document applies to any platform.
The customer has 7 Siebel Servers running within one Siebel enterprise. All of the servers were on the Red Hat Linux platform.
The customer installed a new Siebel Server. The install worked correctly. The customer was seeing these symptoms, for the new Siebel Server ...
Logging in to this new Siebel Server, using srvrmgr command-line was showing "Handshake failed".
The enterprise log shows the Server Manager port being created:
ServerLog LstnObjCreate 1 00011e6b51710557:0 2013-04-19 21:13:30 Created port 49160 for Server Manager
However, when starting srvrmgr, the srvrmgr.log shows a connection problem on this port, 49160:
GenericLog GenericError 1 000000245171115e:0 2013-04-19 21:16:15 (smconn.cpp (284) err=1180866 sys=49160) SBL-NET-01218: The connection was refused by server server3. No component is listening on port 49160.
In order to troubleshoot this, we ran two strace commands;
The first strace for the Siebel Server startup (enterprise is SBA_81_UAT, server is server3) :
strace -f -v -s 1024 -o strace_server_start.txt start_server -e SBA_81_UAT server3
This provides us with a trace, forking to all child Siebel processes. In this way, we can see from the target side of the connection, what is happening when the connection request is performed by srvrmgr.
The second trace for the srvrmgr command (gtwy-name:2320 is the gateway server and port, enterprise is SBA_81_UAT, server is server3) :
strace -f -v -s 1024 -o strace_srvrmgr.txt srvrmgr -g gtwy-name:2320 -e SBA_81_UAT -s server3 -u sadmin -p [password]
This provides us with the source of the connection attempt.
We also gathered netstat -anp and output this to a file.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document