Server to Server problems with conferences

Bob_Jewell · June 25, 2010, 9:36pm

We have two servers on the same network which will support two user groups. One of these servers has been in use for years, now.

im1.domain.com -> original server

JIDs are in the form of username@im1.domain.com

im2.domain.com -> new server

JIDS: username@im2.domain.com

Each also has a conference service (conference.imx.domain.com)

Server to server at least partially works:

Users on both servers can log in and do simple chats with users on either server.
Users on im2 (the new one) can join group chats that are served from both conference.im1.domain.com AND conference.im2.domain.com
Users on im1 can only connect to group chats on conference.im1.domain.com

I don’t believe it is a DNS issue. Because we’re doing simple domains (i.e. NOT xmpp.domain.com with JID of username@domain.com)… we don’t need srv records. And because regular chat works both ways, the servers can obviously find eachother.

I don’t believe it is a firewall issue, either. They are on the same VLAN. I can get to the ports from both sides. Server to Server connections DO get established, and show arrows pointing both ways.

The other weird thing is that users on im1.domain.com can actually get a room list from the conference.im2.domain.com service… they just fail to join the room.

I keep looking over the configurations and can’t find anything notably different. It’s a pretty simple setup. im1.domain.com is a little more complex, having gone through upgrades over the years. it also uses a different database backend, and has fastpath going.

Debug logs:

im1 debug logs are boring…

2010.06.25 17:21:03 69528724 (01/05/00) - Connection #16 tested: OK

etc etc

im2:

2010.06.25 17:19:44 000069 (01/05/00) - Connection #2 tested: OK
2010.06.25 17:19:44 000070 (01/05/00) - Connection #2 tested: OK
2010.06.25 17:19:44 000070 (01/05/00) - Connection #1 tested: OK
2010.06.25 17:19:44 000071 (01/05/00) - Connection #1 tested: OK
2010.06.25 17:19:49 LdapManager: Trying to find a user’s DN based on their username. uid: jewell06, Base DN: dc=“domain”,dc=“com”…
2010.06.25 17:19:49 LdapManager: Creating a DirContext in LdapManager.getContext()…
2010.06.25 17:19:49 LdapManager: Created hashtable with context values, attempting to create context…
2010.06.25 17:19:49 000071 (01/05/00) - Connection #3 tested: OK
2010.06.25 17:19:49 000072 (01/05/00) - Connection #3 tested: OK
2010.06.25 17:19:49 LocalOutgoingServerSession: OS - Trying to connect to im1.domain.com:5269(DNS lookup: im1.domain.com:5269)
2010.06.25 17:19:49 LocalOutgoingServerSession: OS - Plain connection to im1.domain.com:5269 successful
2010.06.25 17:19:49 LocalOutgoingServerSession: OS - Indicating we want TLS to im1.domain.com
2010.06.25 17:19:49 LocalOutgoingServerSession: OS - Negotiating TLS with im1.domain.com
2010.06.25 17:19:50 LdapManager: … context created successfully, returning.
2010.06.25 17:19:50 LdapManager: Starting LDAP search…
2010.06.25 17:19:50 LdapManager: … search finished
2010.06.25 17:19:50 LdapManager: Trying to find a user’s DN based on their username. uid: jewell06, Base DN: dc=“domain”,dc=“com”…
2010.06.25 17:19:50 LdapManager: Creating a DirContext in LdapManager.getContext()…
2010.06.25 17:19:50 LdapManager: Created hashtable with context values, attempting to create context…
2010.06.25 17:19:50 LocalOutgoingServerSession: OS - Going to try connecting using server dialback with: im.franklin.edu
2010.06.25 17:19:50 ServerDialback: OS - Trying to connect to im1.domain.com:5269(DNS lookup: im1.domain.com:5269)
2010.06.25 17:19:50 ServerDialback: OS - Connection to im1.domain.com:5269 successful
2010.06.25 17:19:50 ServerDialback: OS - Sent dialback key to host: im1.domain.com id: 437071b9 from domain: im2.domain.com
2010.06.25 17:19:50 Connect Socket[addr=/10.0.1.97,port=48544,localport=5269]
2010.06.25 17:19:50 ServerDialback: AS - Verifying key for host: im1.domain.com id: 437071b9
2010.06.25 17:19:50 LdapManager: … context created successfully, returning.
2010.06.25 17:19:50 LdapManager: Starting LDAP search…
2010.06.25 17:19:50 ServerDialback: AS - Key was: VALID for host: im1.domain.com id: 437071b9
2010.06.25 17:19:50 ServerDialback: AS - Connection closed for host: im1.domain.com id: 437071b9
2010.06.25 17:19:50 Connection closed before session established
Socket[addr=/10.0.1.97,port=48544,localport=5269]
2010.06.25 17:19:50 LdapManager: … search finished
2010.06.25 17:19:50 LdapManager: Creating a DirContext in LdapManager.getContext()…
2010.06.25 17:19:50 LdapManager: Created hashtable with context values, attempting to create context…
2010.06.25 17:19:50 ServerDialback: OS - Validation GRANTED from: im1.domain.com id: 437071b9 for domain: im2.domain.com
2010.06.25 17:19:50 Connect Socket[addr=/10.0.1.97,port=48545,localport=5269]
2010.06.25 17:19:50 Connection closed before session established
Socket[addr=/10.0.1.97,port=48545,localport=5269]
2010.06.25 17:19:50 Connect Socket[addr=/10.0.1.97,port=48546,localport=5269]
2010.06.25 17:19:50 LdapManager: … context created successfully, returning.
2010.06.25 17:19:50 000072 (01/05/00) - Connection #4 tested: OK
2010.06.25 17:19:50 ServerDialback: RS - Received dialback key from host: im1.domain.com to: im2.domain.com
2010.06.25 17:19:50 000073 (01/05/00) - Connection #4 tested: OK
2010.06.25 17:19:50 ServerDialback: RS - Trying to connect to Authoritative Server: im1.domain.com:5269(DNS lookup: im1.domain.com:5269)
2010.06.25 17:19:50 ServerDialback: RS - Connection to AS: im1.domain.com:5269 successful
2010.06.25 17:19:50 ServerDialback: RS - Asking AS to verify dialback key for id9e1b784e
2010.06.25 17:19:50 ServerDialback: RS - Key was VERIFIED by the Authoritative Server for: im1.domain.com
2010.06.25 17:19:50 ServerDialback: RS - Closing connection to Authoritative Server: im1.domain.com
2010.06.25 17:19:50 ServerDialback: RS - Sending key verification result to OS: im1.domain.com
2010.06.25 17:20:09 Connect Socket[addr=/10.0.1.97,port=48547,localport=5269]
2010.06.25 17:20:09 Connection closed before session established
Socket[addr=/10.0.1.97,port=48547,localport=5269]
2010.06.25 17:20:09 Connect Socket[addr=/10.0.1.97,port=48548,localport=5269]
2010.06.25 17:20:09 ServerDialback: RS - Received dialback key from host: im1.domain.com to: conference.im2.domain.com
2010.06.25 17:20:09 ServerDialback: RS - Trying to connect to Authoritative Server: im1.domain.com:5269(DNS lookup: im1.domain.com:5269)
2010.06.25 17:20:09 ServerDialback: RS - Connection to AS: im1.domain.com:5269 successful
2010.06.25 17:20:09 ServerDialback: RS - Asking AS to verify dialback key for id14c581bf
2010.06.25 17:20:09 ServerDialback: RS - Key was VERIFIED by the Authoritative Server for: im1.domain.com
2010.06.25 17:20:09 ServerDialback: RS - Closing connection to Authoritative Server: im1.domain.com
2010.06.25 17:20:09 ServerDialback: RS - Sending key verification result to OS: im1.domain.com
2010.06.25 17:20:09 ServerDialback: OS - Sent dialback key to host: im.franklin.edu id: 437071b9 from domain: conference.im2.domain.com
2010.06.25 17:20:09 Connect Socket[addr=/10.0.1.97,port=48549,localport=5269]
2010.06.25 17:20:09 ServerDialback: AS - Verifying key for host: im1.domain.com id: 437071b9
2010.06.25 17:20:09 ServerDialback: AS - Key was: VALID for host: im1.domain.com id: 437071b9
2010.06.25 17:20:09 ServerDialback: AS - Connection closed for host: im1.domain.com id: 437071b9
2010.06.25 17:20:09 Connection closed before session established
Socket[addr=/10.0.1.97,port=48549,localport=5269]
2010.06.25 17:20:09 ServerDialback: OS - Validation GRANTED from: im1.domain.com id: 437071b9 for domain: conference.im2.domain.com