Coin, Quoting Sergei Golovan <sgolo...@nes.ru>:
Please, check if ejabberd 2.1.4-1 from sid works with erlang 1:14.a-dfsg-2.
I forgot to say i tested 2.1.4-1, and i'm now using it with erlang 1:13.b.4-dfsg-6 successfully.
erlang-abi-13.a means that binary interface to C programs is compatible with Erlang R13A, which is true. So, it isn'r the bug source.
That was to check if the provides field was correctly reflecting reality.I suppose the code in question is related to X509 certificates used for SSL, but i see no other error message in the log except for an unrelated minor pubsub problem and all SSL connections work well (c2s, s2s, ejabberd web-interface with SSL).
It may also be related to LDAP, but authentication works perfectly.I was using ejabberd 2.1.3-2 with 1:13.b.4-dfsg-5 on another node and saw no such problems. I upgraded to 2.1.4-1 with the same erlang version and it's ok. I may try to upgrade erlang on this node at night to try to reproduce the problem.
If you think this is not a widespread problem, feel free to downgrade severity. I just don't know what would be the next step to debug, so please help me if you can.
Regards. -- Marc Dequènes (Duck)
pgpw4Qj3QNHqG.pgp
Description: PGP Digital Signature
