Can't connect to openldap

Distro: Gentoo 2006.1
ejabberd 1.1.3
openldap 2.3.30

After successfully connecting and authentificating to LDAP server ejabberd closes connection without telling anything. Also tried versions 1.1.1 and 0.7.5.

Here is openldap's log:

Mar 29 07:53:20 services slapd[20354]: conn=1832 fd=12 ACCEPT from IP=192.168.xx.xxx:43871 (IP=0.0.0.0:389)
Mar 29 07:53:20 services slapd[20354]: conn=1833 fd=13 ACCEPT from IP=192.168.xx.xxx:51833 (IP=0.0.0.0:389)
Mar 29 07:53:20 services slapd[20354]: conn=1833 op=0 BIND dn="cn=Manager,dc=xxxxxxxx,dc=com" method=128
Mar 29 07:53:20 services slapd[20354]: conn=1833 op=0 BIND dn="cn=Manager,dc=xxxxxxxx,dc=com" mech=SIMPLE ssf=0
Mar 29 07:53:20 services slapd[20354]: conn=1833 op=0 RESULT tag=97 err=0 text=
Mar 29 07:53:20 services slapd[20354]: conn=1832 op=0 BIND dn="cn=Manager,dc=xxxxxxxx,dc=com" method=128
Mar 29 07:53:20 services slapd[20354]: conn=1832 op=0 BIND dn="cn=Manager,dc=xxxxxxxx,dc=com" mech=SIMPLE ssf=0
Mar 29 07:53:20 services slapd[20354]: conn=1832 op=0 RESULT tag=97 err=0 text=
Mar 29 07:53:20 services slapd[20354]: conn=1832 fd=12 closed (connection lost)
Mar 29 07:53:20 services slapd[20354]: conn=1833 fd=13 closed (connection lost)

Note: openldap server works fine, without timeouts, accessible through mail clients and ldap browsers.

I'm not sure, perhaps I've forgot to tune something, I'll try to do everything from scratch again, but...
Please, anybody, who has working openldap + ejabberd, drop me a line about your configuration - what schemas, ldap servers, ejabberd versions and other components do you use?

I've just found the

I've just found the reason.

LDAP support seems to be broken with the most recent erlang distribution, avaliable as a gentoo package. I have no time for testing with self-build erlang and other versions, but in works with erlang-11.2.1 (R11B?) and doesn't work with 11.2.3-r1.

my FC6 works

maybe you want to check this out:

http://www.ejabberd.im/node/1364

i was having similiar problem with 1.1.3, while 1.1.2 works fine, i'm not a erlang guru, so i dont know if the problem came from erlang or ejabberd, but follow the instructions in the URL above (patch ejabberd-1.1.3) solved the problem.

Syndicate content