After upgrading zimbra LDAP is not starting

[posde]

"Sort of..."

It fully works afaict

Thanks again to the very helpful folks on freenode's Zimbra IRC channel. Without them I wouldn't have been able to make it work.

The original main issue seems to have been an issue with LDAP not being able to come back up. No idea if it was just because of the PID issue, or because my setup was on a chroot'd instance with other LDAP server running on another interface.

I do not know if there already is a safety check at the beginning to stop the upgrade process in case the LDAP server is not reachable.

[Bashar]

i was getting something like this when starting zimbra:

Code: Select all

57f00df9 daemon: bind(7) failed errno=99 (Cannot assign requested address)
57f00df9 slap_open_listener: failed on ldap://example.com:389

i managed to resolve it because my server is on NAT with the public IP of example.com isn't aliased on the server, thus i had to alias it using ifconfig eth1:0 123.123.123.123 netmask 255.255.255.0 up so ldap see it on the main NIC (as it was 192.168.x.x IP on eth1) and LDAP started successfully

Just wanted to post this here in case someone else falls into the same situation and spends hours (like i did) without finding the solution

[NLewan]

Hi @all,

i have the same issue the ldap doesn't start anymore

zimbra@zimbra:~$ zmcontrol start
Host zimbra.otrs.com
Starting ldap...Done.
Failed.
Failed to start slapd. Attempting debug start to determine error.
58bb08e0 daemon: listen(ldap://62.146.52.73:389, 5) failed errno=98 (Address already in use)

root@zimbra /opt # lsof -nPi tcp -s tcp:listen
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
rpcbind 653 root 8u IPv4 8003 0t0 TCP *:111 (LISTEN)
rpcbind 653 root 11u IPv6 8006 0t0 TCP *:111 (LISTEN)
sshd 986 root 3u IPv4 8139 0t0 TCP *:22 (LISTEN)
sshd 986 root 4u IPv6 8141 0t0 TCP *:22 (LISTEN)
mysqld 1032 mysql 10u IPv4 17688 0t0 TCP 127.0.0.1:3306 (LISTEN)

root@zimbra /opt # netstat -antpl | grep LISTEN | grep 389
root@zimbra /opt #


Thanks in advance.

[teds-it]

Check your hosts file for duplicate entries. That did the trick for me.

Regards,

Ted