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-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
