unable to restart zimbra after reboot

[droefs]

Don't worry, I never ran any of the zm* commands as root. They're only supposed to work if /opt/zimbra/bin is in your path anyway, and it's not in my root user's path.
(# zmfixperms.sh doesn't work; # find / -name zmfixperms.sh returns nothing.)

[bobby]

try /opt/zimbra/bin/zmfixperms.sh

(which is one of the few zm commands that must be run as root)

[droefs]

zmfixperms does not exist.

krab:/# ls /opt/zimbra/bin/zmfixperm*
ls: /opt/zimbra/bin/zmfixperm*: No such file or directory

I don't believe running zimbra-commands as root user is the root of my problem; if I look in my history, I find I only ran # zmcontrol status once, and this was after the problematic reboot.

krab:/# history | cut -c 8-30 | grep ^zm
zmcontrol status
zmfixperms.sh

Could it be that the sudden power-outage made me loose some files? At the moment of the outage, the machine was running but virtually inactive (it's a test set-up). There is nothing in /lost+found nore in /tmp/lost+found.

[droefs]

Look what we've got here!

# find / -name zmfixperm*
/opt/zimbra/libexec/zmfixperms
# /opt/zimbra/libexec/zmfixperms
chown: cannot access `/opt/zimbra/perdition-1.17': No such file or directory

But, alas, even after this the problem remains: no Postfix.

$ sh -x ./bin/postfix start
...
postfix/postfix-script: starting the Postfix mail system
$ ps -ef | grep -i postfix
<nothing>

[KevinH]

What version is this? How did you get there? New install or an upgrade?

[droefs]

# dpkg -l | grep zimbra-core
ii zimbra-core 3.0.1_GA_197.D Best email money can buy

On Debian machines using 2.6 kernels. All three systems (OS + Zimbra) were freshly installed a few days before.

[KevinH]

Try to telnet to port 25. Do you have sendmail running? Or another mail server that it already taking port 25?

[droefs]

I've made a total fresh install of all three servers. They now have a Debian 2.6 kernel, regular postfix removed and zimbra installed from the latest zcs-3.1.0_GA_328.DEBIAN3.1.tgz

Right after the installation, everything works fine, testmails arrive and everything.

Strangely the MTA tells me it's not working, while in fact it is:

zimbra@krab:~$ zmcontrol status
 Host krab.ugent.be
      antispam                Running
      antivirus               Running
      mta                     Stopped
              postfix is not running
              zmsaslauthdctl is not running
 zimbra@krab:~$ zmcontrol start
 Host krab.ugent.be
      Starting antispam...Done.
      Starting antivirus...Done.
      Starting mta...FAILED
 ... (lots of stuff) ...
 postfix failed to start
 saslauthd[8472] :set_auth_mech   : failed to initialize mechanism zimbra
 zmsaslauthdctl failed to start
 zimbra@krab:~$ which postfix
 /opt/zimbra/bin/postfix
# ps -ef | grep postfix
root      2562     1  0 16:47 ?        00:00:00 /opt/zimbra/postfix-2.2.9/libexec/master
postfix   2570  2562  0 16:47 ?        00:00:00 pickup -l -t fifo -u
postfix   2571  2562  0 16:47 ?        00:00:00 qmgr -l -t fifo -u

Also, the MX records in my DNS are set to use this machine (krab) as MTA.

After I bring all the machines down and bring them back up one by one (LDAP, MTA, Store, in this order), the zimbra services don't come up automatically on any of them.

I can start the LDAP through $ zmcontrol start
Starting the MTA with $ zmcontrol start gives the same output as above
Starting the Mail Store manually gives me this:

$ zmcontrol start
 Host langoest.ugent.be
      Starting logger...Done.
      Starting mailbox...Done.
      Starting spell...Done.
 zimbra@langoest:~$ zmcontrol status
 Host langoest.ugent.be
      logger                  Running
      mailbox                 Stopped
              tomcat is not running
      spell                   Running

So most things do come up manually, but without the tomcat, the webinterface remains unavailable which renders zimbra unusable.

As an answer to your question:
- The Store and the MTA can both telnet the LDAP server on 389
- The Store and the LDAP can both telnet the MTA on 25
- Not other telnetting on ports 25 or 389 is possible

/opt/zimbra/postfix-2.2.9 is running on the MTA, no other mail services are running on any of the hosts.

Thanks a lot for your help so far. I really hope we can sort this out (the only alternative to Zimbra suggested by my superiors is using MS Exchange )

[KevinH]

For the MTA problem try:

sh -x zmmtactl status

To get zimbra to start at boot check /etc/init.d/zimbra and make sure it is links ito the right rcX.d dir.

For tomcat check /opt/zimbra/tomcat/logs/catalina.out

[droefs]

This is what I get:

1. on the MTA

krab:~# su - zimbra
zimbra@krab:~$ sh -x zmmtactl status
+ BASE=/opt/zimbra
+ SCRIPTS=zmmtaconfigctl postfix zmsaslauthdctl
+ STATUS=0
+ /opt/zimbra/bin/zmmtaconfigctl status
+ R=0
+ '[' 0 -ne 0 ']'
+ /opt/zimbra/bin/postfix status
+ R=1
+ '[' 1 -ne 0 ']'
+ echo 'postfix is not running'
postfix is not running
+ STATUS=1
+ /opt/zimbra/bin/zmsaslauthdctl status
cat: /opt/zimbra/cyrus-sasl-2.1.21.ZIMBRA/state/saslauthd.pid: No such file or directory
+ R=1
+ '[' 1 -ne 0 ']'
+ echo 'zmsaslauthdctl is not running'
zmsaslauthdctl is not running
+ STATUS=1
+ exit 1

2. For the init-scripts, this is what I get on all three servers:

# ls -l /etc/rc* | grep zimbra
lrwxrwxrwx  1 root root 18 Apr 14 15:14 K01zimbra -> /etc/init.d/zimbra
lrwxrwxrwx  1 root root 18 Apr 14 15:14 S99zimbra -> /etc/init.d/zimbra
lrwxrwxrwx  1 root root 18 Apr 14 15:14 K01zimbra -> /etc/init.d/zimbra
lrwxrwxrwx  1 root root 18 Apr 14 15:14 S99zimbra -> /etc/init.d/zimbra
lrwxrwxrwx  1 root root 18 Apr 14 15:14 K01zimbra -> /etc/init.d/zimbra
lrwxrwxrwx  1 root root 18 Apr 14 15:14 S99zimbra -> /etc/init.d/zimbra
lrwxrwxrwx  1 root root 18 Apr 14 15:14 K01zimbra -> /etc/init.d/zimbra
lrwxrwxrwx  1 root root 18 Apr 14 15:14 S99zimbra -> /etc/init.d/zimbra
lrwxrwxrwx  1 root root 18 Apr 14 15:14 K01zimbra -> /etc/init.d/zimbra
# ls /etc/init.d/zimbra
ls: /etc/init.d/zimbra: No such file or directory

3. Analysing Tomcat on the Mail Store:

langoest:~# cat /opt/zimbra/tomcat/logs/catalina.out
zmtomcatstart: info: stale pid 2070 in pid file: No such process
Apr 14, 2006 4:58:46 PM org.apache.coyote.http11.Http11BaseProtocol init
INFO: Initializing Coyote HTTP/1.1 on http-80
Apr 14, 2006 4:58:47 PM org.apache.coyote.http11.Http11BaseProtocol init
INFO: Initializing Coyote HTTP/1.1 on http-7071
Apr 14, 2006 4:58:47 PM org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 1538 ms
Apr 14, 2006 4:58:47 PM org.apache.catalina.core.StandardService start
INFO: Starting service Catalina
Apr 14, 2006 4:58:47 PM org.apache.catalina.core.StandardEngine start
INFO: Starting Servlet Engine: Apache Tomcat/5.5.15
Apr 14, 2006 4:58:47 PM org.apache.catalina.core.StandardHost start
INFO: XML validation disabled
Apr 14, 2006 4:58:48 PM org.apache.catalina.startup.HostConfig deployDescriptor
WARNING: A docBase /opt/zimbra/apache-tomcat-5.5.15/webapps/zimbra inside the host appBase has been specified, and will be ignored
log4j:WARN No appenders could be found for logger (org.apache.catalina.session.ManagerBase).
log4j:WARN Please initialize the log4j system properly.
Zimbra server reserving server socket port=110 bindaddr=null ssl=false
Zimbra server reserving server socket port=995 bindaddr=null ssl=true
Zimbra server reserving server socket port=143 bindaddr=null ssl=false
Zimbra server reserving server socket port=993 bindaddr=null ssl=true
Zimbra server process is running as root, changing to user=zimbra uid=1000 gid=106
Zimbra server process, after change, is running with uid=1000 euid=1000 gid=106 egid=106