I am upgrading from 0.9.8 (with LDAP authentication) to 1.1.2 (with LDAP authentication)
The ejabberd server starts happily, but I can't authenticate. This is what I see in the configuration of the LDAP server:
Feb 17 22:43:08 ldap2 slapd[11213]: conn=74265 fd=12 ACCEPT from IP=202.83.178.90:63303 (IP=0.0.0.0:389)
Feb 17 22:43:08 ldap2 slapd[11213]: conn=74266 fd=13 ACCEPT from IP=202.83.178.90:49558 (IP=0.0.0.0:389)
Feb 17 22:43:08 ldap2 slapd[11213]: conn=74265 op=0 BIND dn="uid=root,ou=BarNet Internal,o=BarNet,c=AU" method=128
Feb 17 22:43:08 ldap2 slapd[11213]: conn=74265 op=0 BIND dn="uid=root,ou=BarNet Internal,o=BarNet,c=AU" mech=SIMPLE ssf=0
Feb 17 22:43:08 ldap2 slapd[11213]: conn=74265 op=0 RESULT tag=97 err=0 text=
Feb 17 22:43:08 ldap2 slapd[11213]: conn=74267 fd=14 ACCEPT from IP=202.83.178.90:59782 (IP=0.0.0.0:389)
Feb 17 22:43:08 ldap2 slapd[11213]: conn=74266 op=0 BIND dn="uid=root,ou=BarNet Internal,o=BarNet,c=AU" method=128
Feb 17 22:43:08 ldap2 slapd[11213]: conn=74266 op=0 BIND dn="uid=root,ou=BarNet Internal,o=BarNet,c=AU" mech=SIMPLE ssf=0
Feb 17 22:43:08 ldap2 slapd[11213]: conn=74266 op=0 RESULT tag=97 err=0 text=
Feb 17 22:43:08 ldap2 slapd[11213]: conn=74268 fd=16 ACCEPT from IP=202.83.178.90:61577 (IP=0.0.0.0:389)
Feb 17 22:43:08 ldap2 slapd[11213]: conn=74267 op=0 BIND dn="uid=root,ou=BarNet Internal,o=BarNet,c=AU" method=128
Feb 17 22:43:08 ldap2 slapd[11213]: conn=74267 op=0 BIND dn="uid=root,ou=BarNet Internal,o=BarNet,c=AU" mech=SIMPLE ssf=0
Feb 17 22:43:08 ldap2 slapd[11213]: conn=74267 op=0 RESULT tag=97 err=0 text=
Feb 17 22:43:08 ldap2 slapd[11213]: conn=74265 fd=12 closed (connection lost)
Feb 17 22:43:08 ldap2 slapd[11213]: conn=74266 fd=13 closed (connection lost)
Feb 17 22:43:08 ldap2 slapd[11213]: conn=74267 fd=14 closed (connection lost)
Feb 17 22:43:08 ldap2 slapd[11213]: conn=74268 op=0 BIND dn="uid=root,ou=BarNet Internal,o=BarNet,c=AU" method=128
Feb 17 22:43:08 ldap2 slapd[11213]: conn=74268 op=0 BIND dn="uid=root,ou=BarNet Internal,o=BarNet,c=AU" mech=SIMPLE ssf=0
Feb 17 22:43:08 ldap2 slapd[11213]: conn=74268 op=0 RESULT tag=97 err=0 text=
Feb 17 22:43:08 ldap2 slapd[11213]: conn=74268 fd=16 closed (connection lost)
So it happily sets up a TCP session towards the LDAP server, but it immediately disconnects after sending the authentication-towards-the-LDAP server. This disconnection behaviour doesn't show up with 0.9.8.
Any ideas?
Which erlang version did you
Which erlang version did you use with 0.9.8? Which erlang version are you using with 1.1.2?
Re: Which erlang version did you
The 0.9.8 was compiled with erlang version 5.4.9 (on i386), the 1.1.2 version was compiled with erlang version 5.5.3 (on AMD64)
Edwin
There's no released
There's no released ejabberd, which work with LDAP on erlang R11B-2 and R11B-3 (which has erts 5.5.3). You have to either downgrade erlang to R11B-1, or use patch for eldap.erl from SVN.
Re: There's no released
I have taken the patch from and it works like a charm!
Thanks for the fast replies!
Edwin
ps. I've informed the maintainer of net-im/ejabberd of the FreeBSD ports project about this issue too