Troubleshooting server startup

When something fails to start, or is not running, there are several things you can check:

[zimbra@myhost ~]$ zmcontrol status

Host myhost.example.com
antispam Running
antivirus Running
ldap Running
logger Running
mailbox Running
mta Stopped
snmp Running
spell Running

In the above example, the mta is not running.

All of the Zimbra services consist of one or more applications. When a service is not running, the first step is to determine which of the component applications is in error.

In our example, the mta is not running. To check the status of the component applications, we'll run the mta status script:


[zimbra@myhost ~]$ sh -x bin/zmmtactl status

BASE=/opt/zimbra
SCRIPTS='zmmtaconfigctl postfix zmsaslauthdctl'
case "$1" in
STATUS=0
for i in '$SCRIPTS'
/opt/zimbra/bin/zmmtaconfigctl status
R=0
'[' 0 -ne 0 ']'
for i in '$SCRIPTS'
/opt/zimbra/bin/postfix status
R=0
'[' 0 -ne 0 ']'
for i in '$SCRIPTS'
/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 ']'
STATUS=1
exit 1

Where we see 1 -ne 0 is a control script returning with a non-zero (failure) status. In this case, it's the saslauthd application.