Hello,

My zimbra server has just been hacked, and has been rebooted not very cleanly... by luck, data are not lost, but now, zimbra doesn't start anymore.

zmcontrol start

Host myhost.com
Starting ldap...Done.
FAILED
bdb_db_close: txn_checkpoint failed: Invalid argument (22)
backend_startup_one: bi_db_open failed! (38)
bdb_db_close: alock_close failed
ERROR - failed to start slapd


As told on this forum, I've tried to understand why ldap doesn't start :

sudo /opt/zimbra/openldap/libexec/slapd -l LOCAL0 -4 -u zimbra -h ldap://myhost.com:389 -f /opt/zimbra/conf/slapd.conf -d 7

bdb_db_open:
bdb_db_open: dbenv_open(/opt/zimbra/openldap-data)
bdb(): unable to initialize mutex: Function not implemented
bdb_db_open: Database cannot be opened, err 38. Restore from backup!
====> bdb_cache_release_all
bdb(): DB_ENV->lock_id_free interface requires an environment configured for the locking subsystem
bdb(): txn_checkpoint interface requires an environment configured for the transaction subsystem
bdb_db_close: txn_checkpoint failed: Invalid argument (22)
backend_startup_one: bi_db_open failed! (38)


OK. it looks like what is described here : http://www.zimbra.com/forums/adminis...not-start.html

So, I've tried to launch the given script, to clean ldap databases.
But then, another error occurs :


/opt/zimbra/sleepycat/bin/db_dump -r -f test.txt displayName.bdb

db_dump: unable to initialize mutex: Function not implemented
db_dump: displayName.bdb: Function not implemented


Is there anything to do now ? Any help is welcome.

Thanks,

Olivier.