Troubleshooting
Problem
Invalid response from OpsServer or Timeout message encountered during SI 5.1 startup process right after installation
Symptom
xxx/install/bin]:-> run.sh
OPS_PID: /xxx/install/ops.pid
Including run.sh extentions
Starting ActiveMQ
please check logs/activemqBroker.log file for startup details
ActiveMQ server started with PID=10158282
PreRegistering Event Listeners
Starting Ops
Starting CmdLine2 client...
CmdLine2 started with PID=16384206
Including run.sh extentions
Starting SAP Controller...
checking for central ops.
. !
running server on http://localhost:8080/
Enter passphrase: -->
Found internal config file /com/sterlingcommerce/security/jcae/provider.txt, loading it now!
Done loading it.
Security Providers: IBMJCE, Certicom, STERCOMM, IBMJSSE2, IBMJGSSProvider, IBMCertPath, SCIKS, SCIKM
DbConnectionTest.runTest(): currentCount = 1
Checking License for central Ops
Central ops is licensed
Controller loading lists...
OpsSymmetric Initializing
OpsSymmetric: Got properties
OpsSymmetric: Algorithm = DESede
-----------------------
Starting SI Server
-----------------------
-----------------------
Waiting for SI JNDI
-----------------------
...!
-----------------------
Initializing Security
-----------------------
Invalid response from OpsServer or Timeout (retrying).
Invalid response from OpsServer or Timeout (retry #1).
Invalid response from OpsServer or Timeout (retry #2).
Invalid response from OpsServer or Timeout (retry #3).
Invalid response from OpsServer or Timeout (retry #4).
Invalid response from OpsServer or Timeout (retry #5).
Invalid response from OpsServer or Timeout (retry #6).
Invalid response from OpsServer or Timeout (retry #7).
Invalid response from OpsServer or Timeout (retrying).
Invalid response from OpsServer or Timeout (retry #1)
Resolving The Problem
This is a two node cluster installation where user installed Sterling Integrator using the aliased DNS name that in return can resolve to two IP Addresses for node1 and node2.
This causes issues Sterling Integrator startup process for one of the node since SI tried to start up the ports on the node that is already occupied instead of the desired node.
Fix:
Verify the <install_dir>/properties/sandbox.cfg file and correct the following:
INSTALL_IP=<actual_server_name>
HOST_NAME=<actual_server_name>
Replace anywhere that has the aliased name
Save the file
from <install_dir>/bin directory run the command below:
./setupfiles.sh and hit Enter
./run.sh to start up SI again to verify
Historical Number
NFX10593
Product Synonym
[<p><b>]Severity[</b><p>];Normal;[<p><b>]Type[</b><p>];NormalFix
Was this topic helpful?
Document Information
Modified date:
14 November 2019
UID
swg21555699