From Zimbra :: Wiki

Server Status

For most of these issues, zmcontrol is your friend

Unless otherwise specified - run all these commands as the zimbra user

su - zimbra

How to see what's running

zmcontrol status

[zimbra@myhost ~]$ zmcontrol status

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

zmcontrol will set the shell exit value based on the status - if everything is running, it will exit with a 0 status.

This is useful if you're wrapping it in a shell script.

Starting and Stopping servers

Server startup overview

To determine which Zimbra services are to be started on a given host, zmcontrol follows this sequence:

1. Determine the logical hostname via the zmhostname command.
2. Determine if this host is the LDAP master host by querying the ldap_is_master item in the host's local configuration.
3. If ldap_is_master is determined to be true, start the LDAP service on this host.
4. Determine the LDAP host to query for configuration information from the setting of the LDAP URL in the host's local configuration.
5. Fetch the host data from LDAP for this host and examines the zimbraServiceEnabled attribute.
6. Start the Zimbra services indicated by the zimbraServiceEnabled attribute.

Starting Servers

zmcontrol start

[zimbra@myhost ~]$ zmcontrol start

Host myhost.example.com
       Starting ldap...Done.
       Starting antispam...Done.
       Starting antivirus...Done.
       Starting logger...Done.
       Starting mailbox...Done.
       Starting mta...Done.
       Starting snmp...Done.
       Starting spell...Done.

Stopping Servers

zmcontrol stop

[zimbra@myhost ~]$ zmcontrol stop

Host myhost.example.com
       Stopping antispam...Done
       Stopping antivirus...Done
       Stopping ldap...Done
       Stopping logger...Done
       Stopping mailbox...Done
       Stopping mta...Done
       Stopping snmp...Done
       Stopping spell...Done

You may see zmcontrol stopping services that were not running, or not listed in the status output. This is normal, and should not be considered an error. We do this to facilitate stopping services when the LDAP server is not accessible.

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.

Individual Zimbra services and Application troubleshooting

Check the page for the corresponding Zimbra servicesfor specific troubleshooting steps.