LDAP won't start
Hope someone can help!
I've got a problem with ldap. Server was running fine until I tried to add an alias and got errors. Figured they were ldap errors. Stopped the server, ran zmfixperms --extended to see if that would help.
Tried to restart the server and get the following error:
I've searched the forums and found some similar issues with older versions...
Failed to start slapd. Attempting debug start to determine error.
hdb_db_open: database "": db_open(/opt/zimbra/data/ldap/hdb/db/id2entry.bdb) failed: Invalid argument (22).
backend_startup_one: bi_db_open failed! (22)
bdb_db_close: database "": alock_close failed
My backups appear to be corrupted so I'm stuck.
Release 6.0.1_GA_1816.RHEL5_64_20090911174852 CentOS5_64 FOSS edition
I've read the following post: [SOLVED] LDAP / slapd - Database environment corrupt (Issue & Solution)
but can't seem to figure out what steps to take for 6.x version of ldap.
Thank you so much!
Anybody know what data is contained in the id2entry.bdb database?
Is there any possibility of recreating the data?
This is for a small Zimbra server - only 5 users.
I've gone ahead and created a new Zimbra instance running the same version as the one that won't start. I created the users, spam accounts etc in the same order they were created in the original. So the directories in the store/0 directory match up with the users mail stores in the original. All passwords and user accounts match.
My question is...
Is there a way to modify and use the ldap.bak file I can successfully create in the new instance of Zimbra to replace the corrupted ldap in the old instance of Zimbra?
I see a lot of UUIDs in there. Wondering if these will cause a problem if they don't match to old Zimbra?
ANY help or suggestions will be greatly appreciated. Just tell me where to ship a case of your favorite beer!
OK, gave up and restored emails with zmlmtpinject.