-
Titel
Export idle and socket_test fails with Error 146 calling connect_to_server. -
Beschreibung
You see the errors in the event log at the time when Export is not able to send messages to the target:
07/10/08 20:57 Cannot connect to host dbserhrrdp50.ddc.vzwcorp.com
Connection timed out
07/10/08 20:57 Process exited sp_xport (to dbserhrrdp50.ddc.vzwcorp.com
queue obpspayprd-sp) [pid = 16564] - exit(1)
The corresponding "status" output from sp_ctrl shows that the Export is indeed idle:
sp_ctrl (obpspayprd-sp:3001)> status
Brief Status for obpspayprd-sp
Process State PID Running
Since
--------------- ------------------------------ --------
--------------------
Cop Running 30785 09-Jul-08
13:43:44
Read Running 785 09-Jul-08
13:44:22
Export Idle
Capture Running 20589 10-Jul-08
14:31:52
Cmd & Ctrl Running 28626 10-Jul-08
20:58:27
You then run a socket_test (see SOL6678 for further details on running one) and see the following errors on the client side:
$ socket_test client <IP address>
/opt/app/splex/.app-modules/socket_test - version: 1.3
SunOS dbserhrrdp50 5.10 Generic_125100-10 sun4u sparc SUNW,Netra-T12
Program executing as client..., Thu Jul 10 22:16:17 2008
Using client host name, dbserhrrdp50.ddc.vzwcorp.com, from environment variable, SP_SYS_HOST_NAME
client host name: dbserhrrdp50.ddc.vzwcorp.com
client IP: <IP address>
Client is try to connect to.....
Server Host: <IP address>
Server Port: 3001
Error calling connect in connect_to_server
Error 146: Connection refused
Error 146 calling connect_to_server
CE:ReadWriteCnt = 0, readCnt=0, totalRBytes=0, writeCnt=0, totalWBytes=0
Error in client, Thu Jul 10 22:16:17 2008 -
Ursache
Some firewall issue may be causing this.
-
Lösung
You may want to rule out any firewall issues by first running the socket test on yet another port where Shareplex is successfully running (by shutting down that instance of Shareplex) and if that socket test ran fine, then the problem is most likely due to firewall. Another thing that can be done is to rule out network issues first by examining the /etc/host file on both source and target and ensuring that the source have entries for target IP and hostname and vice versa. If other investigation rule out network configuration issues, then the problem may have to be looked at from firewall angle and the issue referred to network administrators. The port on which Shareplex communicates needs to be opened in both directions for UDP and TCP traffic and firewall sometimes prevent this. Once the firewall issues are addressed, then the Export should be able to connect to Import on the other side.