After backup and restore "Starting ldap...failed with exit code 256"

[deuscapturus]

I followed a wiki article on how to backup and restore zimbra open source edition.

I backed up my /opt/zimbra directory installed my new system with all of the same network information. installed a "dummy version" of the same zimbra edition as I had before. And then removed that dummy version and replaced it with my zimbra directory that I had backed up.

Below is the resulting output from the end of the upgrade procedure.

Please help. My company isn't functioning while this is down.

zmsetup.07092009-004527.log >>

Thu Jul 9 00:45:27 2009 Operations logged to /tmp/zmsetup.07092009-004527.log
Thu Jul 9 00:45:27 2009 Getting installed packages
Thu Jul 9 00:45:29 2009 Getting local config zimbra_server_hostname
Thu Jul 9 00:45:29 2009 Getting local config ldap_url
Thu Jul 9 00:45:30 2009 zimbra_server_hostname contained in ldap_url checking ldap status
Thu Jul 9 00:45:30 2009 Checking ldap status.
Thu Jul 9 00:45:30 2009 *** Running as zimbra user: /opt/zimbra/bin/ldap status
/opt/zimbra/bin/ldap: line 59: kill: (7958) - No such process
Thu Jul 9 00:45:30 2009 Starting ldap...
Thu Jul 9 00:45:30 2009 *** Running as zimbra user: /opt/zimbra/sleepycat/bin/db_recover -h /opt/zimbra/openldap-data
Thu Jul 9 00:45:30 2009 *** Running as zimbra user: /opt/zimbra/libexec/zmldapapplyldif
/opt/zimbra/bin/ldap: line 59: kill: (7958) - No such process
sudo: sorry, you must have a tty to run sudo
/opt/zimbra/bin/ldap: line 59: kill: (7958) - No such process
sudo: sorry, you must have a tty to run sudo
/opt/zimbra/bin/ldap: line 59: kill: (7958) - No such process
sudo: sorry, you must have a tty to run sudo
/opt/zimbra/bin/ldap: line 59: kill: (7958) - No such process
sudo: sorry, you must have a tty to run sudo
/opt/zimbra/bin/ldap: line 59: kill: (7958) - No such process
sudo: sorry, you must have a tty to run sudo
/opt/zimbra/bin/ldap: line 59: kill: (7958) - No such process
sudo: sorry, you must have a tty to run sudo
/opt/zimbra/bin/ldap: line 59: kill: (7958) - No such process
sudo: sorry, you must have a tty to run sudo
IO::Socket::INET: connect: Connection refused at /opt/zimbra/libexec/zmldapapplyldif line 145.
Thu Jul 9 00:46:12 2009 *** Running as zimbra user: /opt/zimbra/bin/ldap status
/opt/zimbra/bin/ldap: line 59: kill: (7958) - No such process
Thu Jul 9 00:46:13 2009 *** Running as zimbra user: /opt/zimbra/bin/ldap start
/opt/zimbra/bin/ldap: line 59: kill: (7958) - No such process
sudo: sorry, you must have a tty to run sudo
/opt/zimbra/bin/ldap: line 59: kill: (7958) - No such process
sudo: sorry, you must have a tty to run sudo
/opt/zimbra/bin/ldap: line 59: kill: (7958) - No such process
sudo: sorry, you must have a tty to run sudo
/opt/zimbra/bin/ldap: line 59: kill: (7958) - No such process
sudo: sorry, you must have a tty to run sudo
/opt/zimbra/bin/ldap: line 59: kill: (7958) - No such process
sudo: sorry, you must have a tty to run sudo
/opt/zimbra/bin/ldap: line 59: kill: (7958) - No such process
sudo: sorry, you must have a tty to run sudo
/opt/zimbra/bin/ldap: line 59: kill: (7958) - No such process
sudo: sorry, you must have a tty to run sudo
Failed to start slapd. Attempting debug start to determine error.

Thu Jul 9 00:46:52 2009 failed with exit code 256.
Thu Jul 9 00:48:30 2009 checking isEnabled zimbra-core
Thu Jul 9 00:48:30 2009 zimbra-core not in enabled cache
Thu Jul 9 00:48:30 2009 enabled packages
Thu Jul 9 00:48:30 2009 zimbra_server_hostname contained in ldap_url checking ldap status
Thu Jul 9 00:48:30 2009 Checking ldap status.
Thu Jul 9 00:48:30 2009 *** Running as zimbra user: /opt/zimbra/bin/ldap status
/opt/zimbra/bin/ldap: line 59: kill: (7958) - No such process
Thu Jul 9 00:48:31 2009 Starting ldap...
Thu Jul 9 00:48:31 2009 *** Running as zimbra user: /opt/zimbra/sleepycat/bin/db_recover -h /opt/zimbra/openldap-data
Thu Jul 9 00:48:31 2009 *** Running as zimbra user: /opt/zimbra/libexec/zmldapapplyldif
/opt/zimbra/bin/ldap: line 59: kill: (7958) - No such process
sudo: sorry, you must have a tty to run sudo
/opt/zimbra/bin/ldap: line 59: kill: (7958) - No such process
sudo: sorry, you must have a tty to run sudo
/opt/zimbra/bin/ldap: line 59: kill: (7958) - No such process
sudo: sorry, you must have a tty to run sudo
/opt/zimbra/bin/ldap: line 59: kill: (7958) - No such process
sudo: sorry, you must have a tty to run sudo
/opt/zimbra/bin/ldap: line 59: kill: (7958) - No such process
sudo: sorry, you must have a tty to run sudo
/opt/zimbra/bin/ldap: line 59: kill: (7958) - No such process
sudo: sorry, you must have a tty to run sudo
/opt/zimbra/bin/ldap: line 59: kill: (7958) - No such process
sudo: sorry, you must have a tty to run sudo
IO::Socket::INET: connect: Connection refused at /opt/zimbra/libexec/zmldapapplyldif line 145.
Thu Jul 9 00:49:13 2009 *** Running as zimbra user: /opt/zimbra/bin/ldap status
/opt/zimbra/bin/ldap: line 59: kill: (7958) - No such process
Thu Jul 9 00:49:14 2009 *** Running as zimbra user: /opt/zimbra/bin/ldap start
/opt/zimbra/bin/ldap: line 59: kill: (7958) - No such process
sudo: sorry, you must have a tty to run sudo
/opt/zimbra/bin/ldap: line 59: kill: (7958) - No such process
sudo: sorry, you must have a tty to run sudo
/opt/zimbra/bin/ldap: line 59: kill: (7958) - No such process
sudo: sorry, you must have a tty to run sudo
/opt/zimbra/bin/ldap: line 59: kill: (7958) - No such process
sudo: sorry, you must have a tty to run sudo
/opt/zimbra/bin/ldap: line 59: kill: (7958) - No such process
sudo: sorry, you must have a tty to run sudo
/opt/zimbra/bin/ldap: line 59: kill: (7958) - No such process
sudo: sorry, you must have a tty to run sudo
/opt/zimbra/bin/ldap: line 59: kill: (7958) - No such process
sudo: sorry, you must have a tty to run sudo
Failed to start slapd. Attempting debug start to determine error.

[deuscapturus]

I've been awake for the last 30 hours trying to fix my company email after a server crash reinstall and restore. I backed up and restored the entire /opt/zimbra directory using the method described in many different places.

Here are the lessons I have learned:

1. Zimbra for Fedora Core 7 will NOT run on Fedora 10 or 11! I did however get it to run on Fedora 8.
2. Install the dummy version of Zimbra first before replacing it with the backup
3. Kill the firewall.
4. Make sure sendmail isn't running.
5. Run /opt/zimbra/libexec/zmfixperms as root after restoring. But this IS NOT ENOUGH. Also run 'chown -R zimbra.zimbra /opt/zimbra/store'.
6. Make sure your domain is entered properly in /etc/hosts/
7. For unknown reasons I had to start ldap manually during the upgrade when I was getting error "failed with exit code 256.". Run 'ldap start' in a different terminal as the zimbra user when you get the error.

I hope this saves you from hours of pain and agony.

[phoenix]

If you're serious about running zimbra as the email server for your company you'd be far better running it on a stable enterprise distribution such as RHEL5 or SLES (if you want free then Zimbra on CentOS5 works fine), a bleeding edge consumer distribution is not a serious platform for company mail.

[deuscapturus]

Last Notes:

Also do a "chown -R zimbra.zimbra /opt/zimbra/index" or you won't be able to search.

[phoenix]

How about just doing it correctly with:

/opt/zimbra/libexec/zmfixperms -verbose -extended

/opt/zimbra/libexec/zmfixperms -help