Hi Konstantin. On Wed, 2012-08-22 at 16:00 +0400, Konstantin Khomoutov wrote: > Uh, sorry but I'm now somewhat lost now. Sorry ;)
> First, we don't have a bug in our BTS about this upstream issue, so > definitely uploading of 2.1.10-3 wasn't supposed to fix it (as I did > not even know this issue exists). Yeah of course,... I just think parts of it are similar (s2s problems)... so anyone who faces the problems I have, and who read about the this Debian bug, can see that there are still things wrong, which may, though similar, be unrelated to this issue :) > Second, the bug is still open, so upstream's 2.1.11 (which we > failed to push into Debian in time before the freeze) wasn't expected to > fix it either. Yes, I guess so. > Third, the s2s issue has (supposedly) nothing to do with clustered > setup: s2s is about different XMPP servers (I mean, controlled by > different authorities) speak (XMPP) to each other to allow their users > communicate. Of course,... It's just one effect that I have,.. that s2s (controlled by different authorities) become completely broken.... and I get these "temporarily_blocked" thingy... > Now that I have shed some light onto this issue (I hope), I have the > next question: do you observe any crash reports, like the one cited > above, in your logs? I grepped through my logs for "undef", but there were no occurances... So I guess that issue is solved. I you need, I can send you my logs,... I guess they contain no confidential infos (apart from the JIDs perhaps). > 1) You seem to be affected by that EJAB-1565 issue; if so, please file > a bug in the Debian BTS against 2.1.10 with the "upstream" tag, so > we know the issue exists that affects at least one of our users. #685606. > 2) We have 2.1.11 package ready and could possibly upload it into > experimental if you feel like experimenting with it and seeing if it > can resolve some of your problems. So if you feel like such an > upload could be handy, let us know. I guess that may make sense... although I feel that at least some of the problems I describe there are deeper problems and not simple bugs. Especially that the nodes apparently never try to reconnect to each other, once the connection got lost. Have you already had a look at 3.x versions? Cheers, Chris.
smime.p7s
Description: S/MIME cryptographic signature
