s2s connection with ejabberd failed with "connection timeout" first time, than second time it established ok.
Steps to reproduce:
1. Make sure that we do not have existing s2s connection with testing ejabberd server.
2. Try to send some request, e.g. disco query from client, served by ejabberd, to our prosody server.
3. After some period of time (10-20 seconds) client receives error "remote-server-not-found" (but in debug log we see that servers are doing authentication, tls handshake, dialback, etc).
4. Try to send request second time and everything goes ok - client received correct reply and all works well.
Reproduced well with any prosody from 0.7 to prosody-hg:29d7eb6ff62c (self-compiled, prosody from debian squeeze package, and also with public servers such as prosody.im) and any ejabberd 2.1.x (ejabberd 2.1.5 from debian package, ejabberd on public servers such as jabber.ru/xmpp.ru).
See full debug log of two s2s attempts attached. (May 22 15:15:29 - first, May 22 15:16:36 - second)
Thanks for the report - looking into this, the log is helpful. I suspect I know what is happening, but I need to check with the code to see if I'm right.
Changes
owner MattJ
pztrn@pztrn.ru
on
Confirm that and for prosody-ejabberd s2s (bot on prosody joining ejabberd conference). After some time (couple of hours usually) bot leaving conference with "remote-server-not-found" message. Prosody from hg, ejabberd server - jabber.ru
Sorry, can't attach log atm, my ssh unavailable >.<
MattJ
on
Hi vitalyster,
I've had more time to sit down and read your logs again. I'm not sure they show any problem. For example, from your first s2s attempt:
May 22 15:15:29 s2sin24e6810 info incoming s2s connection xmpp.ru->bggg.net.ru complete
and
May 22 15:15:29 s2sout24ddd00 info outgoing s2s connection bggg.net.ru->xmpp.ru complete
For your second attempt:
May 22 15:16:36 s2sin24b1c40 info incoming s2s connection xmpp.ru->bggg.net.ru complete
(the same outgoing s2s connection was used to reply because it was never closed)
In addition I just registered an account on xmpp.ru. I logged in and sent a message to my Prosody account. It worked fine, first time.
pztrn - I think your issue is different, as you say you have an s2s connection which is fine but closes after some hours. If you can still reproduce the issue, please file a new report with logs.
Thanks both.
MattJ
on
Ok, managed to reproduce this issue today with the account I registered on xmpp.ru. I don't know exactly what is triggering this (in particular why it sometimes works and sometimes does not), or why other ejabberd instances seem to work just fine.
Candidate patch at http://prosody.im/patches/prosody-multi-dialback.patch
Changes
title s2s with xmpp.ru (ejabberd) sometimes fails
tags Milestone-0.8 Status-Accepted
vitalyster
on
Great work :) Seems like now all is ok. (At least now I can't reproduce it so quick)
s2s connection with ejabberd failed with "connection timeout" first time, than second time it established ok. Steps to reproduce: 1. Make sure that we do not have existing s2s connection with testing ejabberd server. 2. Try to send some request, e.g. disco query from client, served by ejabberd, to our prosody server. 3. After some period of time (10-20 seconds) client receives error "remote-server-not-found" (but in debug log we see that servers are doing authentication, tls handshake, dialback, etc). 4. Try to send request second time and everything goes ok - client received correct reply and all works well. Reproduced well with any prosody from 0.7 to prosody-hg:29d7eb6ff62c (self-compiled, prosody from debian squeeze package, and also with public servers such as prosody.im) and any ejabberd 2.1.x (ejabberd 2.1.5 from debian package, ejabberd on public servers such as jabber.ru/xmpp.ru). See full debug log of two s2s attempts attached. (May 22 15:15:29 - first, May 22 15:16:36 - second)
AttachmentsThanks for the report - looking into this, the log is helpful. I suspect I know what is happening, but I need to check with the code to see if I'm right.
ChangesConfirm that and for prosody-ejabberd s2s (bot on prosody joining ejabberd conference). After some time (couple of hours usually) bot leaving conference with "remote-server-not-found" message. Prosody from hg, ejabberd server - jabber.ru Sorry, can't attach log atm, my ssh unavailable >.<
Hi vitalyster, I've had more time to sit down and read your logs again. I'm not sure they show any problem. For example, from your first s2s attempt: May 22 15:15:29 s2sin24e6810 info incoming s2s connection xmpp.ru->bggg.net.ru complete and May 22 15:15:29 s2sout24ddd00 info outgoing s2s connection bggg.net.ru->xmpp.ru complete For your second attempt: May 22 15:16:36 s2sin24b1c40 info incoming s2s connection xmpp.ru->bggg.net.ru complete (the same outgoing s2s connection was used to reply because it was never closed) In addition I just registered an account on xmpp.ru. I logged in and sent a message to my Prosody account. It worked fine, first time. pztrn - I think your issue is different, as you say you have an s2s connection which is fine but closes after some hours. If you can still reproduce the issue, please file a new report with logs. Thanks both.
Ok, managed to reproduce this issue today with the account I registered on xmpp.ru. I don't know exactly what is triggering this (in particular why it sometimes works and sometimes does not), or why other ejabberd instances seem to work just fine. Candidate patch at http://prosody.im/patches/prosody-multi-dialback.patch
ChangesGreat work :) Seems like now all is ok. (At least now I can't reproduce it so quick)
Thanks for the confirmation, pushed to 0.8, shall be in 0.8.2: http://hg.prosody.im/0.8/rev/1e1110840965
ChangesPatch can be applied to 0.8.1, it works fine after patching. Just a note for people who can't wait for the next release.