powered by Jive Software

S2s problems

I am having problems with s2s communications. I have 2 servers set up. I origionaly had 2.5.1 running on the one and 2.4.0 running on the other and s2s was working. I updated the 2.4.0 to 2.5.1 and now the s2s does not work between them. I have them set up to use the whitelist and both on the default port. I get the error listed below when I try to add someone to my list from the other server.

2006.03.22 09:43:36 Created context values, attempting to create context…

2006.03.22 09:43:36 … context created successfully, returning.

2006.03.22 09:44:09 OS - Connection to 192.168.1.100:5269 successful

2006.03.22 09:44:09 OS - Sent dialback key to host: 192.168.1.100 id: d3811748 from domain: 192.168.1.101

2006.03.22 09:44:29 OS - Time out waiting for answer in validation from: 192.168.1.100 id: d3811748 for domain: 192.168.1.101

2006.03.22 09:44:29 Error sending packet to remote server:

java.lang.Exception: Failed to create connection to remote server

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

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

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

at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)

at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)

at java.lang.Thread.run(Unknown Source)

2006.03.22 09:44:29 Finishing Outgoing Server Reader. No session to close.

java.net.SocketException: socket closed

at java.net.SocketInputStream.socketRead0(Native Method)

at java.net.SocketInputStream.read(Unknown Source)

at sun.nio.cs.StreamDecoder$CharsetSD.readBytes(Unknown Source)

at sun.nio.cs.StreamDecoder$CharsetSD.implRead(Unknown Source)

at sun.nio.cs.StreamDecoder.read(Unknown Source)

at java.io.InputStreamReader.read(Unknown Source)

at org.xmlpull.mxp1.MXParser.fillBuf(MXParser.java:2971)

at org.xmlpull.mxp1.MXParser.more(MXParser.java:3025)

at org.jivesoftware.wildfire.net.MXParser.nextImpl(MXParser.java:75)

at org.xmlpull.mxp1.MXParser.nextToken(MXParser.java:1100)

at org.dom4j.io.XMPPPacketReader.parseDocument(XMPPPacketReader.java:290)

at org.jivesoftware.wildfire.server.OutgoingServerSocketReader$1.run(OutgoingServe rSocketReader.java:91)

2006.03.22 09:44:29 OS - Going to try connecting using server dialback

2006.03.22 09:44:29 OS - Trying to connect to 192.168.1.100:5269

2006.03.22 09:45:04 Connect Socket[addr=/192.168.1.100,port=1509,localport=5269]

2006.03.22 09:45:04 AS - Verifying key for host: 192.168.1.100 id: d3811748

2006.03.22 09:45:04 AS - Key was: VALID for host: 192.168.1.100 id: d3811748

2006.03.22 09:45:04 AS - Connection closed for host: 192.168.1.100 id: d3811748

I just don’'t understand why it was working with the 2.4.0 and not after I upgraded to the newest version.

Any help would be great

thanks

Can you check netstat on the servers and make sure they are listening on all the correct ports? It almost looks like 192.168.1.101 isnt listening for s2s connections, which it would need for dialback to work correctly, obviously.

Yeah I checked both servers and they are both listening on the correct port. 5269.

Have you tried a second time without shutting down any of the servers?

Sometimes I might come to think that the s2s is not very stable for Jive (at least on slower machines). I have a similar problem appearing occassionally but when I do the same action the second time it’'s fine.

I have tired a couple of different times with a couple of different cofigurations. But yes it does seem that s2s is not that stable.