external auth

[sasha]

It just says ERROR : Failed to start slapd .

Only other thing I could find is in zimbra.log :

May 29 19:10:03 localhost zimbramon[3603]: 3603:info: 2006-05-29 19:10:02, DISK: localhost.localdomain: dev: /dev/hda7, mp: /, tot: 7251, avail: 3738
May 29 19:10:03 localhost zimbramon[3603]: 3603:info: 2006-05-29 19:10:02, DISK: localhost.localdomain: dev: /dev/hda6, mp: /boot, tot: 99, avail: 83
May 29 19:10:03 localhost zimbramon[3600]: 3600:info: 2006-05-29 19:10:02, QUEUE: 0 0
May 29 19:10:03 localhost sendmail[3656]: k4U2A2Ff003656: from=zimbra, size=313, class=0, nrcpts=1, msgid=<200605300210.k4U2A2Ff003656@localhost.local domain>, relay=zimbra@localhost
May 29 19:10:03 localhost sendmail[3656]: k4U2A2Ff003656: to=zimbra, ctladdr=zimbra (500/500), delay=00:00:01, xdelay=00:00:00, mailer=relay, pri=30313, relay=[127.0.0.1] [127.0.0.1], dsn=4.0.0, stat=Deferred: Connection refused by [127.0.0.1]
May 29 19:10:05 localhost zimbramon[3604]: 3604:info: 2006-05-29 19:10:02, STATUS: : Cannot: determine
May 29 19:12:02 localhost zimbramon[3706]: 3706:info: 2006-05-29 19:12:01, STATUS: : Cannot: determine

[KevinH]

How about if you start ldap like:

sh -x /opt/zimbra/bin/ldap start

[sasha]

zimbra.log then shows 'Address already in use ' :

May 30 19:22:06 localhost zimbramon[3507]: 3507:info: 2006-05-30 19:22:02, STATUS: : Cannot: determine
May 30 19:22:14 localhost slapd[3563]: @(#) $OpenLDAP: slapd 2.3.21 (May 3 2006 10:18:43) $ root@build-fc3.liquidsys.com:/home/build/p4/CRAY/ThirdParty/openldap/openldap-2.3.21/servers/slapd
May 30 19:22:14 localhost slapd[3563]: daemon: bind(7) failed errno=98 (Address already in use)
May 30 19:22:14 localhost slapd[3563]: slapd stopped.
May 30 19:22:14 localhost slapd[3563]: connections_destroy: nothing to destroy.
May 30 19:24:03 localhost zimbramon[3645]: 3645:info: 2006-05-30 19:24:01, STATUS: : Cannot: determine

-----------------------------------------------------------------------------------------------
The command itself ( sh -x /opt/zimbra/bin/ldap start ) has output :

+ PID=
+ PIDFILE=/opt/zimbra/openldap/var/run/slapd.pid
+ mkdir -p /opt/zimbra/openldap/var/run/
+ case "$1" in
+ start
+ checkrunning
+ getpid
+ '[' -f /opt/zimbra/openldap/var/run/slapd.pid ']'
+ '[' x = x ']'
+ RUNNING=0
+ '[' 0 = 0 ']'
+ '[' '!' -f /opt/zimbra/openldap-data/DB_CONFIG ']'
+ /opt/zimbra/libexec/zmconfigure /opt/zimbra/conf/slapd.conf.in /opt/zimbra/conf/slapd.conf
+ sudo /opt/zimbra/openldap-2.3.21/libexec/slapd -l LOCAL0 -4 -u zimbra -h ldap://:389/ -f /opt/zimbra/conf/slapd.conf
+ sleep 2
+ getpid
+ '[' -f /opt/zimbra/openldap/var/run/slapd.pid ']'
+ '[' x = x ']'
+ echo 'ERROR - failed to start slapd'
ERROR - failed to start slapd
+ echo ''

+ exit 1

-------------------------------------

[KevinH]

That means your LDAP server really is still running on the ports Zimbra's LDAP needs (637, 389) are the two I think we use.

[sasha]

I think I have my sldap fixed now to run on port 390 ... zimbra starts without error .

Still in admin console I get
Authentication failed. Invalid Credentials ( bad dn/password )
javax.naming.AuthenticationException : empty search .

[sasha]

Do I need the zimbra schema in my ldap ? Do I need TLS , SSL etc. ? Is this maybe what I am missing ? Looks like this is a nut I won't be able to crack ...

[KevinH]

No your LDAP doesn't need the Zimbra schema. The only time zimbra will use your LDAP is when we are doing auth. No other times.

[sasha]

Well , how does it do authorization ? ... it must be expecting a certain type of schema I would think . Maybe the schema I have now is not compatible ?

If that's all there is to it then I don't know what else could be the problem .
The stuff I put into the authorization configuration looks OK to you then ?

[KevinH]

It does an LDAP bind and then runs the LDAP filter you provide. So assuming you have cn=[user id] it should work.