Take the 2-minute tour ×
Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

My server running zimbra crashed hard and now the zimbra server won't start. Here is what I get in the logs:

Nov 24 21:04:14 zimbra1 slapd[21258]: @(#) $OpenLDAP: slapd 2.4.21 (Mar 24 2010 18:25:37) $     build@build10.lab.zimbra.com:/home/build/p4/main/ThirdParty/openldap/openldap-2.4.21.7z/servers/slapd 
Nov 24 21:04:15 zimbra1 slapd[21265]: bdb(): file id2entry.bdb has LSN 7/8194631, past end of log at 7/6485128 
Nov 24 21:04:15 zimbra1 slapd[21265]: bdb(): Commonly caused by moving a database from one database environment 
Nov 24 21:04:15 zimbra1 slapd[21265]: bdb(): to another without clearing the database LSNs, or by removing all of 
Nov 24 21:04:15 zimbra1 slapd[21265]: bdb(): the log files from a database environment 
Nov 24 21:04:15 zimbra1 slapd[21265]: bdb(): /opt/zimbra/data/ldap/hdb/db/id2entry.bdb: unexpected file type or format 
Nov 24 21:04:15 zimbra1 slapd[21265]: hdb_db_open: database "": db_open(/opt/zimbra/data/ldap/hdb/db/id2entry.bdb) failed: Invalid argument (22). 
Nov 24 21:04:16 zimbra1 slapd[21265]: backend_startup_one (type=hdb, suffix=""): bi_db_open failed! (22) 
Nov 24 21:04:16 zimbra1 slapd[21265]: bdb_db_close: database "": alock_close failed

zmcontrol -v:

Release 6.0.6_GA_2324.RHEL5_20100406144520 CentOS5 FOSS edition.

Perl version 5.8.8

db_recover -V:

Berkeley DB 4.7.25: (May 15, 2008)
share|improve this question

1 Answer 1

up vote 1 down vote accepted

From the errors you've posted it looks as if the databased used by slapd, the LDAP server, has become corrupt. There are a number of things you can try. First, make a backup of your data even though its corrupt! Some of the suggestions here may modify the database files and preclude alternate recovery suggestions.

NB: I know nothing about Zimbra, but I've worked with OpenLDAP quite a bit. There may be Zimbra-specific things you should be doing that I know nothing about.

The easiest would be to simply restore your database from backups. I'm not familiar with Zimbra in particular, but most applications that integrate tightly with an LDAP backend include some form of periodic dump of the database to LDIF records. If you have such a backup, you can probably remove everything in your /opt/zimbra/data/ldap/hdb/db/ (SAVE IT FIRST!) and re-import from your backups. This procedure is probably described somewhere in the documentation.

If the db_recover tool is available on your system (this is a BerkeleyDB maintenance tool), you can see if the database is recoverable. Change to /opt/zimbra/data/ldap/hdb/db/, and then run db_recover -v -h .. This may or may solve anything. If Zimbra uses OpenLDAP more recent than 2.2 (e.g., 2.3.x or later), this should happen automatically.

share|improve this answer
    
Indeed. Although, in order to resolve this I had to db_dump -r and re-load a couple databases that zimbra was unable to read. TY for the response. –  frogstarr78 Nov 26 '10 at 17:49

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.