[SOLVED] Zimbra 6.0.7 doesn't Automatically Start on SLES 11 SP1

[vavai]

Hi,

I have a problem regarding new Zimbra 6.0.7 64 bit installation on SLES 11 SP1 64 bit. The installation process went smooth and everything works without problem. The problem hit me after rebooting the system. Zimbra won't start automatically on boot. Manually start after boot system make Zimbra running OK.

Look a bit closer, it seems that Zimbra trying to start before it's dependent services, e.g : network services, so Zimbra failed to bind to it's IP because network service has not been successfully executed.

On old thread regarding installation on openSUSE, I found some solution by remove the Zimbra services :

chkconfig --del zimbra

and then edit the /etc/init.d/zimbra, add the following code on top of file (after it's comment) :

### BEGIN INIT INFO
# Provides: zimbra
# Required-Start: $network $syslog
# Required-Stop:
# Default-Start: 3 5
# Default-Stop: 0 1 2 6
# Description: Zimbra mail service
### END INIT INFO

and then activating the services :

chkconfig --add zimbra ; chkconfig zimbra on

But the problem still exist. The same problem didn't hit me on SLES 11 (without SP) with Zimbra 6.X.X.

Any help greatly appreciated.

[vavai]

Solved by follows the resolution on bugzilla suggestion : Bug 48373 – Zimbra does not start on boot (64-bit SLES 11). My fault, I search in bugzilla with wrong search term (and found nothing) before submit this thread.

On previous attempt, I didn't run insserv zimbra command and it make big different because Zimbra service not updated correctly.

Resolution :

Modify /etc/init.d/zimbra, adding the following lines on top of file (below the comment)

### BEGIN INIT INFO
# Provides: zimbra
# Required-Start: $network $remote_fs $syslog $time nscd cron
# Required-Stop: $network $remote_fs $syslog $time
# Default-Start: 3 5
# Description: Zimbra mail service
### END INIT INFO

Then executed
# insserv zimbra

The above lines will tell Zimbra service to start afrer network, remote_fs, syslog, time, nscd and cron services.

Now it should works and loads on startup properly.

Marks the thread as solved.