S2s problem: "Error trying to connect to remote server" (v3.1.1;FC4;jdk1.6)

I’'m running wildfire 3.1.1 and s2s has started failing in the last few days with the error indicated below

(where REMOTE_SERVER is any one of the commonly connected remote s2s servers for our system)

the only change I’'ve made recently to the server was to add a second NIC which resides on our internal 10.x.y.z netowrk.

once I noticed the s2s issue I restarted wildfire with “”, however the problem is still occurring, even with wildfired bound to the public ip.

has anyone else seen this behavior or know of a fix?

at the moment I can’'t upgrade to 3.2.2 because we have a number of users on pandion, see: pandion login issues


  1. error.log

2007.03.08 18:50:26 org.jivesoftware.wildfire.server.OutgoingServerSession.createOutgoingSession(Out goingServerSession.java:259) Error trying to connect to remote server: REMOTE_SERVER(DNS lookup: REMOTE_DNS:5269)

java.net.SocketTimeoutException: connect timed out

at java.net.PlainSocketImpl.socketConnect(Native Method)

at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)

at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)

at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)

at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)

at java.net.Socket.connect(Socket.java:519)

at org.jivesoftware.wildfire.server.OutgoingServerSession.createOutgoingSession(Ou tgoingServerSession.java:254)

at org.jivesoftware.wildfire.server.OutgoingServerSession.authenticateDomain(Outgo ingServerSession.java:140)

at org.jivesoftware.wildfire.server.OutgoingSessionPromise.createSessionAndSendPac ket(OutgoingSessionPromise.java:130)

at org.jivesoftware.wildfire.server.OutgoingSessionPromise.access$300(OutgoingSess ionPromise.java:40)

at org.jivesoftware.wildfire.server.OutgoingSessionPromise$1$1.run(OutgoingSession Promise.java:95)

at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java: 885)

at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)

at java.lang.Thread.run(Thread.java:619)

#/error.log


  1. warn.log

2007.03.08 18:50:38 Error verifying key of remote server: REMOTE_SERVER

java.net.SocketTimeoutException: connect timed out

at java.net.PlainSocketImpl.socketConnect(Native Method)

at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)

at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)

at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)

at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)

at java.net.Socket.connect(Socket.java:519)

at org.jivesoftware.wildfire.server.ServerDialback.verifyKey(ServerDialback.java:5 21)

at org.jivesoftware.wildfire.server.ServerDialback.validateRemoteDomain(ServerDial back.java:457)

at org.jivesoftware.wildfire.server.ServerDialback.createIncomingSession(ServerDia lback.java:340)

at org.jivesoftware.wildfire.server.IncomingServerSession.createSession(IncomingSe rverSession.java:98)

at org.jivesoftware.wildfire.net.ServerSocketReader.createSession(ServerSocketRead er.java:211)

at org.jivesoftware.wildfire.net.SocketReader.createSession(SocketReader.java:469)

at org.jivesoftware.wildfire.net.BlockingReadingMode.run(BlockingReadingMode.java: 53)

at org.jivesoftware.wildfire.net.SocketReader.run(SocketReader.java:123)

at java.lang.Thread.run(Thread.java:619)

#/warn.log


Message was edited by: aramprice

Hi,

can you connect to the remote server using “telnet REMOTE_DNS 5269”? It would be good to know that you don’'t have a routing or firewall problem.

LG

not a firewall problem but sadly a bit of routing weirdness that took a lot of head scratching to figure out.

thanks, your post got me off in the right direction.