[redbaron]

Originally Posted by jholder

If you get a cannot determine services, then ldap isn't starting. It's little deceptive

try
ldap start

what do you get?

OK, this is the scary/wired part...
ldap works, or at least appear to work...

ldap status
slapd running pid: 20155

 ps -ef | grep ldap
zimbra   20155     1  0 Jul27 ?        00:00:00 /opt/zimbra/openldap/libexec/slapd -l LOCAL0 -4 -u zimbra -h ldap://slinkilin.yyy.xx.xx:389 -f /opt/zimbra/conf/slapd.conf
ldap stop
Killing slapd with pid 20155
/opt/zimbra/bin/ldap: line 150: kill: (20155) - No such process
 done.
ps -ef | grep ldap
zimbra   22346 12719  0 00:18 pts/3    00:00:00 grep ldap
-----
zmcontrol  start
Host slinkilin.yyy.xx.xx
        Starting ldap...Done.
[zimbra@slinkilin ~]$ ps -ef | grep ldap
zimbra   22495     1  0 00:18 ?        00:00:00 /opt/zimbra/openldap/libexec/slapd -l LOCAL0 -4 -u zimbra -h ldap://slinkilin.yyy.xx.xx:389 -f /opt/zimbra/conf/slapd.conf
zimbra   22573 12719  0 00:19 pts/3    00:00:00 grep ldap

sestatus
SELinux status:                 disabled
iptables -L
Chain INPUT (policy ACCEPT)
target     prot opt source               destination

Chain FORWARD (policy ACCEPT)
target     prot opt source               destination

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination

If I use netcat on port 389 I get a connection....
Gili