Last updated on JULY 20, 2016
Applies to:Siebel CRM - Version 18.104.22.168  and later
Information in this document applies to any platform.
*** Checked for relevance on 20-Jun-2016 ***
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 rasapp3. 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 rasapp3) :
strace -f -v -s 1024 -o strace_server_start.txt start_server -e SBA_81_UAT rasapp3
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 (rastst:2320 is the gateway server and port, enterprise is SBA_81_UAT, server is rasapp3) :
strace -f -v -s 1024 -o strace_srvrmgr.txt srvrmgr -g rastst:2320 -e SBA_81_UAT -s rasapp3 -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.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms