I've installed Zimbra 5.0.13 on CentOS 5.2.
After following a how-to on the installation, everything worked fine right out of the box. I had setup a user and successfully sent email. It ran without problems for about two days.
Then I rebooted. Doh!
After reboot, Zimbra will not start. I've poked around in the log files and found that LDAP is not starting. The first LDAP failures looked like this...
-----------------------------------------------------------
Host zimbra.mydomain.com
Starting ldap...Done.
FAILED
/opt/zimbra/bin/ldap: line 59: kill: (14023) - No such process
/opt/zimbra/bin/ldap: line 59: kill: (14023) - No such process
/opt/zimbra/bin/ldap: line 59: kill: (14023) - No such process
/opt/zimbra/bin/ldap: line 59: kill: (14023) - No such process
/opt/zimbra/bin/ldap: line 59: kill: (14023) - No such process
/opt/zimbra/bin/ldap: line 59: kill: (14023) - No such process
/opt/zimbra/bin/ldap: line 59: kill: (14023) - No such process
Failed to start slapd. Attempting debug start to determine error.
daemon: getaddrinfo() failed: Name or service not known
-----------------------------------------------------------
I tracked down /opt/zimbra/openldap-2.3.43.7z/var/run/slapd.pid, deleted it, and then saw this error as LDAP started...
-----------------------------------------------------------
Host zimbra.mydomain.com
Starting ldap...Done.
FAILED
Failed to start slapd. Attempting debug start to determine error.
daemon: getaddrinfo() failed: Name or service not known
-----------------------------------------------------------
(Note: The domain name has been changed to protect... well, me.)
I'm still poking around the log files and google trying to find an answer, but I'm hoping you may already be familiar with this problem.
Any ideas?
Thanks,
Lane Beneke


LinkBack URL
About LinkBacks

