I use Jive Messenger (nightly build from 13/06/05) and can not connect to another server (jabberd 1.4). Jive Messenger can send, but can not receive messages.
Is anyone able to help me with this?
Hey Jonathan,
First off, download the latest nightly build that contains many s2s improvements and better logging.
Things to check/do:
. The hostname used by your JM server must be registered in the DNS so that remote servers may be able to connect to your JM server
. Servers will communicate using port 5269 so make sure that that port is opened in the firewall. A simple test that you can try is doing a telnet to the JM’'s hostname at port 5269 from the remote server.
. Open the Admin Console. Click on Logs > Debug and enable the Debug Log. Copy the information in the debug.log so I can analyze where the problem is.
If your jabberd1.4 server is publicly accesible I may try connecting from my local(development) server and check the issue. So give me the hostname of the jabberd server if the server is publicly accesible.
Regards,
– Gato
The jabber 1.4 i used is the amessage.de server of Matthias Wimmer with public access.
But certainly you are right, i found a problem with the DNS.
Message was edited by:
Jonathan Yih
Hi
DNS working now and the port is free, but my problem is still there.
There must be something i do wrong, so here the requested log. I hope you can find my mistake.
regards
2005.06.20 11:19:42 Stopping server
2005.06.20 11:19:42 Logging off zombie@kub.kicks-ass.net/Psi on org.jivesoftware.messenger.net.SocketConnection@198e8b4 socket: Socket[addr=/80.138.111.171,port=1954,localport=5222] session: org.jivesoftware.messenger.ClientSession@1d5b89c status: -1 address: zombie@kub.kicks-ass.net/Psi id: c9a61d6e presence:
5
2005.06.20 11:19:53 Loading plugin admin
Hey Jonathan,
Looking at your log I don’'t see any s2s communication. After the server has been started could you try sending a message to and from amessage.de? FYI, I tried connecting from my local server to amessage.de and it worked fine both ways.
You should see something like this in your log when sending a message TO amessage.de:
2005.06.20 12:28:04 OS - Trying to connect to amessage.de:5269
2005.06.20 12:28:05 OS - Connection to amessage.de:5269 successfull
2005.06.20 12:28:06 OS - Sent dialback key to host: amessage.de id: 050b95ca5f08b9df860006feaea87f9f8898c566 from domain: gato.dyndns.org
2005.06.20 12:28:07 Connect Socket[addr=/212.112.238.55,port=46627,localport=5269]
2005.06.20 12:28:07 AS - Verifying key for host: amessage.de id: 050b95ca5f08b9df860006feaea87f9f8898c566
2005.06.20 12:28:07 AS - Key was: VALID for host: amessage.de id: 050b95ca5f08b9df860006feaea87f9f8898c566
2005.06.20 12:28:07 AS - Connection closed for host: amessage.de id: 050b95ca5f08b9df860006feaea87f9f8898c566
2005.06.20 12:28:08 OS - Validation GRANTED from: amessage.de id: 050b95ca5f08b9df860006feaea87f9f8898c566 for domain: gato.dyndns.org
and something like this when receiving FROM amessage.de:
2005.06.20 12:29:43 Connect Socket[addr=/212.112.238.55,port=46690,localport=5269]
2005.06.20 12:29:43 RS - Received dialback key from host: amessage.de to: gato.dyndns.org
2005.06.20 12:29:43 RS - Trying to connect to Authoritative Server: amessage.de:5264
2005.06.20 12:29:43 RS - Connection to AS: amessage.de:5264 successfull
2005.06.20 12:29:43 RS - Asking AS to verify dialback key for idd9551065
2005.06.20 12:29:44 RS - Key was VERIFIED by the Authoritative Server for: amessage.de
2005.06.20 12:29:44 RS - Closing connection to Authoritative Server: amessage.de
2005.06.20 12:29:44 RS - Sending key verification result to OS: amessage.de
Let me know how it goes.
Regards,
– Gato
Hello
-
Thx for your help!!!
-
Sorry, i missed something.
So here the log again after i tried some messages and actions from my jive messenger to the amessage.de server and backwards.
I pasted everything i found in ‘‘debug’’ with activated logging.
Maybe i am too stupid for all this …
best regards
2005.06.20 11:19:42 Stopping server
2005.06.20 11:19:42 Logging off zombie@kub.kicks-ass.net/Psi on org.jivesoftware.messenger.net.SocketConnection@198e8b4 socket: Socket[addr=/80.138.111.171,port=1954,localport=5222] session: org.jivesoftware.messenger.ClientSession@1d5b89c status: -1 address: zombie@kub.kicks-ass.net/Psi id: c9a61d6e presence:
5
2005.06.20 11:19:53 Loading plugin admin
2005.06.20 11:29:39 Connect Socket[addr=/80.138.111.171,port=1989,localport=5222]
2005.06.20 11:38:22 Connect Socket[addr=/80.138.111.171,port=1995,localport=5222]
2005.06.20 11:39:39 Logging off dfg@kub.kicks-ass.net/Exodus on org.jivesoftware.messenger.net.SocketConnection@4b0bbb socket: Socket[addr=/80.138.111.171,port=1995,localport=5222] session: org.jivesoftware.messenger.ClientSession@ef4504 status: 3 address: dfg@kub.kicks-ass.net/Exodus id: f6196c90 presence:
2005.06.20 11:39:41 Logging off zombie@kub.kicks-ass.net/Psi on org.jivesoftware.messenger.net.SocketConnection@9c176c socket: Socket[addr=p508A6FAB.dip.t-dialin.net/80.138.111.171,port=1989,localport=5222] session: org.jivesoftware.messenger.ClientSession@1c5ddd3 status: 3 address: zombie@kub.kicks-ass.net/Psi id: a9d7d53c presence:
5
2005.06.20 11:39:48 Stopping server
2005.06.20 19:20:21 Loading plugin admin
2005.06.20 19:23:35 Stopping server
2005.06.20 19:23:43 Loading plugin admin
2005.06.20 19:23:58 Stopping server
2005.06.20 19:24:50 Loading plugin admin
2005.06.20 19:25:13 Connect Socket[addr=/80.138.66.102,port=2054,localport=5222]
2005.06.20 19:25:48 Logging off zombie@kub.kicks-ass.net/Exodus on org.jivesoftware.messenger.net.SocketConnection@106df95 socket: Socket[addr=/80.138.66.102,port=2054,localport=5222] session: org.jivesoftware.messenger.ClientSession@40afb9 status: 3 address: zombie@kub.kicks-ass.net/Exodus id: e224b09 presence:
2005.06.20 19:26:03 Connect Socket[addr=/80.138.66.102,port=2061,localport=5222]
2005.06.20 19:33:58 Logging off zombie@kub.kicks-ass.net/Psi on org.jivesoftware.messenger.net.SocketConnection@6de609 socket: Socket[addr=/80.138.66.102,port=2061,localport=5222] session: org.jivesoftware.messenger.ClientSession@1195c2b status: 3 address: zombie@kub.kicks-ass.net/Psi id: fba66078 presence:
Logged out
2005.06.20 19:34:05 Connect Socket[addr=/80.138.66.102,port=2078,localport=5222]
Jonathan,
This is weird. I don’'t see any server-to-server trace in your debug log.
-
Could you check that you are in fact using the latest nightly build? You can check the info logged in the info file which shows the version you are using or you can go to the Admin Console and check if you have Sessions > Server Sessions.
-
How are you testing the server-to-server communication? Using a client connected to your JM local server try sending a message to "aaaa@amessage.de". That should generate some new entries in your debug.log.
Let me know how it goes.
Regards,
– Gato
ok, it is shown it is 2.1.5. Right/ontop admin screen.
I messaged aaaa@amessage.de and absolutely nothing changed in any of those logfiles. I only get changes when i send messages internal of my local server,
(client to client inside same server).
In case of any mistakes i reinstall now and will test again.
best regards
Hey Jonathan,
Now your log makes more sense. Server-to-server is not supported in JM 2.1.5. You will need to install the latest nightly build to take advantage of s2s. After you have installed the latest nightly build you should see that the version 2.2.0 Beta 1 is being used.
Regards,
– Gato
S2S is working now.
THANK YOU VERY VERY MUCH!!!
best regards
J. Yih
You are very welcome. Enjoy s2s
Regards,
– Gato
My msg was repeated below and this one was deleted to keep forum sorted
Message was edited by:
Jonathan Yih
Could you be a little more specific? BTW, try updating to the latest nightly build.
Regards,
– Gato
Sorry i was too slow in typing/editing
Problems continue in different form.
Actualy the jive messenger is invisible to some other servers and messages work only one-way. Means jive messenger can send to other servers, but can not receive messages from other servers.
This is the message the guy from amessage got from his server:
Failed to deliver stanza to other server while sent out dialback request: 83.243.42.79: Connected (tried to send data before stream has been authed)
This is the log out of jive-messengers debug-log:
2005.06.24 19:32:26 Connect Socket[addr=/80.138.86.79,port=2789,localport=5222]
2005.06.24 19:32:27 Connect Socket[addr=/212.112.238.55,port=40073,localport=5269]
2005.06.24 19:32:27 RS - Received dialback key from host: amessage.de to: kub.kicks-ass.net
2005.06.24 19:32:27 RS - Error, incoming connection already exists from: amessage.de
2005.06.24 19:32:56 Connect Socket[addr=/212.112.238.55,port=40098,localport=5269]
2005.06.24 19:32:56 RS - Received dialback key from host: amessage.de to: kub.kicks-ass.net
2005.06.24 19:32:56 RS - Error, incoming connection already exists from: amessage.de
2005.06.24 19:33:50 Connect Socket[addr=/212.112.238.55,port=40126,localport=5269]
2005.06.24 19:33:50 RS - Received dialback key from host: amessage.de to: kub.kicks-ass.net
2005.06.24 19:33:50 RS - Error, incoming connection already exists from: amessage.de
2005.06.24 19:33:57 Connect Socket[addr=/212.112.238.55,port=40130,localport=5269]
2005.06.24 19:33:57 RS - Received dialback key from host: amessage.de to: kub.kicks-ass.net
2005.06.24 19:33:57 RS - Error, incoming connection already exists from: amessage.de
Anyone can help?
btw: the newest nightly build i can get from download area is named:
jive_messenger_2005-06-13.zip
So i need a url were to find newer things.
best regards
Could you find out which software the servers you are having problems with are using? From the logs I see that the remote server is trying to establish an incoming connection to kub.kicks-ass.net but since there is an existing connection then the new connection is being rejected. I don’‘t know why the remote server is creating a new connection if one already exists, unless the existing connection was closed and JM assumes that it’'s still active.
Could you update to the latest nightly build and try again? If the problem persists can you verify (using netstat or some other tool) if the remote server has another connection to your server? A possibility could be that the remote server closed the previous socket connection but didn’'t send a element and due to network configuration Java is not getting that the connection was closed. If that is the case and the remote server cannot be modified to send the element then you will have to decrease the idle timeout for closing connections.
Regards,
– Gato
thx for superfast reply.
I will try this all and keep you up to date.
regards
Message was edited by:
Jonathan Yih
Nightly build are located here: http://www.jivesoftware.org/nightly.jsp. Press F5 to force a refresh if you are seeing old builds. Latest is as of today.
Regards,
– Gato
thx
I updated like i was told.
Same Problems.
I use another client now for jive and my mate is still using psi.
Maybe depends on that clients.
Looks like the problem is gone in this lineup.
I will test later on more exactly.
Will keep you informed.
best regards
Hello
The problem did not appear since we do not use Psi anymore.
The main server we test with, is the jabberd 1.4, amessage.de.
I’'ll keep you informed.
regards
Hmm, s2s wouldn’'t be different depending on the client you are using. I guess there should be another reason.
Regards,
– Gato