LDAP failed after i changed my server

[crowley]

Hi, yesterday I had i total failure with my mail server and had to use another one for my Zimbra installation, it's under Red Hat 5.01 (64 bits) and ZCS OpenSource 4.5.10 (the same version in both servers). First, I installed Zimbra and worked without a problem, then I stop the service and copy this directories from my backup:

db
conf
log
logger
openldap-data
store

When I tried to restart, showed this error:

sudo -u zimbra zmcontrol start
Host mail1.aspel.com.mx
Starting ldap...Done.
FAILED
cp: accessing `/opt/zimbra/openldap-data/DB_CONFIG': Permission denied
Failed to start slapd. Attempting debug start to determine error.
backend_startup_one: bi_db_open failed! (-1)

I checked the permisions and ownership of the files and directories and looked fine, so i runned this command to find whats wrong with OpenLDAP:

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

@(#) $OpenLDAP: slapd 2.3.39 (Nov 11 2007 11:52:20) $
build@build11:/home/build/p4/FRANK/ThirdParty/openldap/openldap-2.3.39.5z/servers/slapd
daemon_init: ldap://mail1.aspel.com.mx:389
daemon_init: listen on ldap://mail1.aspel.com.mx:389
daemon_init: 1 listeners to open...
ldap_url_parse_ext(ldap://mail1.aspel.com.mx:389)
daemon: listener initialized ldap://mail1.aspel.com.mx:389
daemon_init: 1 listeners opened
slapd init: initiated server.
slap_sasl_init: initialized!
bdb_back_initialize: initialize BDB backend
bdb_back_initialize: Sleepycat Software: Berkeley DB 4.2.52: (December 3, 2003)
hdb_back_initialize: initialize HDB backend
hdb_back_initialize: Sleepycat Software: Berkeley DB 4.2.52: (December 3, 2003)
....
backend_startup_one: starting ""
bdb_db_open:
bdb_db_open: alock package is unstable
backend_startup_one: bi_db_open failed! (-1)
slapd shutdown: initiated
====> bdb_cache_release_all
slapd destroy: freeing system resources.
slapd stopped.
connections_destroy: nothing to destroy.

When it started, send a lot of lines, but at the end showed this error about the alock file. Even if I delete it and re-run the startup, fails the same way.

So, I runed db_recover to try to recover the DB but it failed.

sudo -u zimbra /opt/zimbra/sleepycat/bin/db_recover -h /opt/zimbra/openldap-data/

db_recover: unlink: /opt/zimbra/openldap-data/__db.005: Permission denied
db_recover: unlink: /opt/zimbra/openldap-data/__db.004: Permission denied
db_recover: unlink: /opt/zimbra/openldap-data/__db.002: Permission denied
db_recover: unlink: /opt/zimbra/openldap-data/__db.003: Permission denied
db_recover: unlink: /opt/zimbra/openldap-data/__db.001: Permission denied
db_recover: Invalid log file: log.0000000006: Permission denied
db_recover: PANIC: Permission denied
db_recover: PANIC: DB_RUNRECOVERY: Fatal error, run database recovery
db_recover: unlink: /opt/zimbra/openldap-data/__db.005: Permission denied
db_recover: unlink: /opt/zimbra/openldap-data/__db.004: Permission denied
db_recover: unlink: /opt/zimbra/openldap-data/__db.002: Permission denied
db_recover: unlink: /opt/zimbra/openldap-data/__db.003: Permission denied
db_recover: unlink: /opt/zimbra/openldap-data/__db.001: Permission denied
db_recover: DB_ENV->open: DB_RUNRECOVERY: Fatal error, run database recovery

Again, the files and directory belongs to the zimbra user and the zimbra.log doesn't have nothing related.

I don't know what else to do. Any idea?

Best Regards.

[jholder]

run the zmfixperms directory located in /opt/zimbra/libexec

[quanah]

Originally Posted by crowley

I don't know what else to do. Any idea?

Please show the output of ls -ld /opt/zimbra/openldap-data and ls -l /opt/zimbra/openldap-data

[tomparker.net]

Originally Posted by jholder

run the zmfixperms directory located in /opt/zimbra/libexec

I had this problem when moving from Ubuntu Dapper 32-bit to Hardy 64-bit. The above command worked great. Don't forget to run it as root.

I followed this guide on the wiki:
Network Edition: Moving from 32-bit to 64-bit Server - Zimbra :: Wiki

I hope this helps the next person who was up all night trying to get email operational before dawn.