Closed GoogleCodeExporter closed 9 years ago
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.
Original comment by MWild1
on 23 May 2011 at 9:46
[deleted comment]
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 >.<
Original comment by pztrn@pztrn.ru
on 24 May 2011 at 6:21
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.
Original comment by MWild1
on 5 Jun 2011 at 12:06
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
Original comment by MWild1
on 6 Jun 2011 at 1:11
Great work :) Seems like now all is ok. (At least now I can't reproduce it so
quick)
Original comment by vitalyster
on 6 Jun 2011 at 8:34
Thanks for the confirmation, pushed to 0.8, shall be in 0.8.2:
http://hg.prosody.im/0.8/rev/1e1110840965
Original comment by MWild1
on 6 Jun 2011 at 10:10
Patch 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.
Original comment by dmitriy.trt
on 18 Jun 2011 at 2:26
Original issue reported on code.google.com by
vitalyster
on 22 May 2011 at 3:42Attachments: