Bug#591431: erlang 14.a breaks ejabberd
tag 591431 -moreinfo +pending retitle 591431 Error reports in ejabberd.log regarding ASN.1 driver when using LDAP authentication severity 591431 normal thanks The fix for this bug is provided by upstream [1] and is integrated in the ejabberd 2.1.5 Debian package which is being cooked right now. Since you clearly experienced a problem unrelated to this bug, please open another bug if you will continue to experience the problem starting the server. Also if your issue is not pressing, you could wait for 2.1.5-1 to be uploaded in sid. 1. https://git.process-one.net/ejabberd/mainline/commit/c9ff37027805d1d72446b5bcbc1a60da0f2aaae4 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#591431: erlang 14.a breaks ejabberd
tag 591431 +moreinfo
thanks
At least two upstream devs did some LDAP related testing and concluded
that while the errors are indeed being logged, LDAP auth works OK.
Hence, the severity of this bug in the upstream tracker was decreased
to "minor".
I tested 2.1.5 with LDAP auth and it works for me as well:
=INFO REPORT 2010-08-04 03:13:54 ===
I(<0.250.0>:eldap:967) : LDAP connection on 192.168.2.10:3268
=INFO REPORT 2010-08-04 03:13:54 ===
I(<0.260.0>:eldap:967) : LDAP connection on 192.168.2.10:3268
=ERROR REPORT 2010-08-04 03:13:54 ===
Error in process <0.328.0> on node 'ejabb...@localhost' with exit value:
{badarg,[{erlang,register,[asn1_driver_owner,<0.328.0>]},{asn1rt_driver_handler,init,2}]}
=INFO REPORT 2010-08-04 03:13:54 ===
I(<0.37.0>:ejabberd_app:70) : ejabberd 2.1.5 is started in the node
ejabb...@localhost
=INFO REPORT 2010-08-04 03:14:40 ===
I(<0.355.0>:ejabberd_listener:232) : (#Port<0.4037>) Accepted connection
{{127,0,0,1},54482} -> {{127,0,0,1},5222}
=INFO REPORT 2010-08-04 03:14:41 ===
I(<0.359.0>:ejabberd_c2s:580) :
({socket_state,tls,{tlssock,#Port<0.4037>,#Port<0.4059>},<0.358.0>})
Accepted authentication for kostix by ejabberd_auth_ldap
=INFO REPORT 2010-08-04 03:14:41 ===
I(<0.359.0>:ejabberd_c2s:839) :
({socket_state,tls,{tlssock,#Port<0.4037>,#Port<0.4059>},<0.358.0>})
Opened session for kos...@localhost/Home
Some of the devs also tested the setup with LDAP serving two virtual
hosts and it also worked OK (giving more error reports being discussed).
In other words, it appears that the problem is elsewhere, and this error
is a false trail in your case.
So, please try to gather more info if the problem still persists.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#591431: erlang 14.a breaks ejabberd
This bug is now tracked upstream at https://support.process-one.net/browse/EJAB-1284 and at first appears to be a bug in Erlang. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#591431: erlang 14.a breaks ejabberd
tag 591431 +upstream thanks An upstream developer has just confirmed the bug manifests itself with Erlang/OTP R14 and ejabberd using LDAP. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#591431: erlang 14.a breaks ejabberd
reassign 591431 ejabberd thanks On Tue, Aug 3, 2010 at 1:46 PM, Marc Dequènes (Duck) wrote: > Coin, > > Quoting Sergei Golovan : > >> 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. OK. Bad to hear that. > >> 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 see. > > 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've conculted with one of ejabberd authors who says that these warnings are harmless, so the problem seems to be somewhere deeper. > > 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. ejabberd was known to break on erlang 14, and there was at least one patch applied to make it build on erlang 14, so may be it's another incompatibility. > > 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. I've contacted ejabberd maintainer who agreed that it's likely to be an ejabberd fault, so now I'm reassigning this bug to ejabberd. If it'll turn out that the bug in Erlang feel free to reassign it back. Cheers! -- Sergei Golovan -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#591431: erlang 14.a breaks ejabberd
Coin, Quoting Sergei Golovan : 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
Bug#591431: erlang 14.a breaks ejabberd
On Tue, Aug 3, 2010 at 4:07 AM, Marc Dequènes (Duck) wrote:
>
> I just installed ejabberd on Squeeze, and found the server initialization
> fail, leaving it unusuable. The message in the log was:
> =ERROR REPORT 2010-08-03 01:30:28 ===
> Error in process <0.258.0> on node 'ejabb...@thorfinn.duckcorp.org' with
> exit value:
> {badarg,[{erlang,register,[asn1_driver_owner,<0.258.0>]},{asn1rt_driver_handler,init,2}]}
> =ERROR REPORT 2010-08-03 01:30:28 ===
> Error in process <0.259.0> on node 'ejabb...@thorfinn.duckcorp.org' with
> exit value:
> {badarg,[{erlang,register,[asn1_driver_owner,<0.259.0>]},{asn1rt_driver_handler,init,2}]}
> =ERROR REPORT 2010-08-03 01:30:28 ===
> Error in process <0.260.0> on node 'ejabb...@thorfinn.duckcorp.org' with
> exit value:
> {badarg,[{erlang,register,[asn1_driver_owner,<0.260.0>]},{asn1rt_driver_handler,init,2}]}
Please, check if ejabberd 2.1.4-1 from sid works with erlang 1:14.a-dfsg-2.
>
> I downgraded to 1:13.b.4-dfsg-6 and it solved the problem. I then saw
> erlang-base still provides erlang-abi-13.a, but for sure something changed
> in the API/ABI, and it may be the cause of the problem.
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.
Cheers!
--
Sergei Golovan
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#591431: erlang 14.a breaks ejabberd
Package: erlang-base
Version: 1:14.a-dfsg-1
Severity: grave
Coin,
I just installed ejabberd on Squeeze, and found the server
initialization fail, leaving it unusuable. The message in the log was:
=ERROR REPORT 2010-08-03 01:30:28 ===
Error in process <0.258.0> on node 'ejabb...@thorfinn.duckcorp.org'
with exit value:
{badarg,[{erlang,register,[asn1_driver_owner,<0.258.0>]},{asn1rt_driver_handler,init,2}]}
=ERROR REPORT 2010-08-03 01:30:28 ===
Error in process <0.259.0> on node 'ejabb...@thorfinn.duckcorp.org'
with exit value:
{badarg,[{erlang,register,[asn1_driver_owner,<0.259.0>]},{asn1rt_driver_handler,init,2}]}
=ERROR REPORT 2010-08-03 01:30:28 ===
Error in process <0.260.0> on node 'ejabb...@thorfinn.duckcorp.org'
with exit value:
{badarg,[{erlang,register,[asn1_driver_owner,<0.260.0>]},{asn1rt_driver_handler,init,2}]}
I downgraded to 1:13.b.4-dfsg-6 and it solved the problem. I then saw
erlang-base still provides erlang-abi-13.a, but for sure something
changed in the API/ABI, and it may be the cause of the problem.
Regards.
--
Marc Dequènes (Duck)
pgp6LXhwzrbBT.pgp
Description: PGP Digital Signature
