Possible db corruption

[Orangeruffy]

I woke up on Sunday to find that my installation of Zimbra was not running.

zmcontrol status showed that nothing was running and zmcontrol start failed at ldap with the following message:

[zimbra@zimbra ~]$ zmcontrol start
Host zimbra.solveitsimply.local
Starting ldap...Done.
Failed.
Failed to start slapd. Attempting debug start to determine error.
daemon: listen(ldap://zimbra.solveitsimply.local:389, 5) failed errno=98 (Address already in use)

From what I can see on the forums there seems to be an option to recover a corrupt db but the instrutions I have seen refer to a sleepycat directory which I don't appear to have on my installation:

[SOLVED] LDAP / slapd - Database environment corrupt (Issue & Solution)

"$ cd /opt/zimbra/openldap-data
$ /opt/zimbra/sleepycat/bin/db_recover"

Does anyone have any suggestions on how to recover the db on community edition v6.0.7_GA_2686?

Any help greatly appreciated. Let me know if you need more info.

The logs show that the Zimbra services had to randomly restart at about 4:40AM

[normal activity] Nov 20 04:40:11 zimbra postfix/qmgr[5497]: DBB3A652FB: removed

[restart occurs] Nov 20 04:45:34 zimbra zimbramon[1315]: 1315:info: Starting services initiated by zmcontrol
Nov 20 04:45:34 zimbra slapd[1362]: @(#) $OpenLDAP: slapd 2.4.22 (Jun 10 2010 14:08:22) $#012#011build@build29.lab.zimbra.com:/home/build/p4/main/ThirdParty/openldap/openldap-2.4.22.3z/servers/slapd
Nov 20 04:45:35 zimbra slapd[1363]: hdb_db_open: database "": unclean shutdown detected; attempting recovery.
Nov 20 04:45:37 zimbra slapd[1363]: slapd starting
Nov 20 04:45:37 zimbra slapd[1363]: daemon: listen(ldap://zimbra.solveitsimply.local:389, 5) failed errno=98 (Address already in use)
Nov 20 04:45:37 zimbra slapd[1363]: slapd stopped.
Nov 20 04:45:40 zimbra slapd[1367]: @(#) $OpenLDAP: slapd 2.4.22 (Jun 10 2010 14:08:22) $#012#011build@build29.lab.zimbra.com:/home/build/p4/main/ThirdParty/openldap/openldap-2.4.22.3z/servers/slapd
Nov 20 04:45:40 zimbra slapd[1368]: slapd starting
Nov 20 04:45:40 zimbra slapd[1368]: daemon: listen(ldap://zimbra.solveitsimply.local:389, 5) failed errno=98 (Address already in use)
Nov 20 04:45:40 zimbra slapd[1368]: slapd stopped.

[phoenix]

[restart occurs] Nov 20 04:45:34 zimbra zimbramon[1315]: 1315:info: Starting services initiated by zmcontrol
Nov 20 04:45:34 zimbra slapd[1362]: @(#) $OpenLDAP: slapd 2.4.22 (Jun 10 2010 14:08:22) $#012#011build@build29.lab.zimbra.com:/home/build/p4/main/ThirdParty/openldap/openldap-2.4.22.3z/servers/slapd
Nov 20 04:45:35 zimbra slapd[1363]: hdb_db_open: database "": unclean shutdown detected; attempting recovery.
Nov 20 04:45:37 zimbra slapd[1363]: slapd starting
Nov 20 04:45:37 zimbra slapd[1363]: daemon: listen(ldap://zimbra.solveitsimply.local:389, 5) failed errno=98 (Address already in use)
Nov 20 04:45:37 zimbra slapd[1363]: slapd stopped.
Nov 20 04:45:40 zimbra slapd[1367]: @(#) $OpenLDAP: slapd 2.4.22 (Jun 10 2010 14:08:22) $#012#011build@build29.lab.zimbra.com:/home/build/p4/main/ThirdParty/openldap/openldap-2.4.22.3z/servers/slapd
Nov 20 04:45:40 zimbra slapd[1368]: slapd starting
Nov 20 04:45:40 zimbra slapd[1368]: daemon: listen(ldap://zimbra.solveitsimply.local:389, 5) failed errno=98 (Address already in use)
Nov 20 04:45:40 zimbra slapd[1368]: slapd stopped.

According to that error there's already something listening on port 389, shutdown Zimbra then kill any remaining processes and restart Zimbra. Do you still get an error and if so, what is it?

If a problem still exists please post the output from all of the commands in the 'Verify...' section of the Split DNS article.