Unresponsive Server Troubleshooting
When you contact the Zimbra Support team regarding an unresponsive server, you may be requested to run several troubleshooting utilities and provide the output of those utilities to the support team. Additionally, you may be requested to submit stack traces and log files for the unresponsive server.
This article provides instructions for running troubleshooting utilities, and also provides the locations of the stack trace and logging files. For each utility that you run, you will need to save the output in order to send it to Zimbra Support.
Overview of Utilities, Stacktrace Files, and Log Files
Log Files and Stack Trace Files
These are useful logs for beginning to troubleshoot an unresponsive mail server. Logs are generally rotated daily, so logs from previous days will have a time stamp appended to the filename, such as 5-6-2008. Any stacktrace files will have the process id of the JVM appended to the filename.
In all releases 5.0.x and 4.5.x, this is the main mailbox application log:
- /opt/zimbra/log/mailbox.log
In ZCS 5.0.x, the JVM output log and stacktrace files will be in /opt/zimbra/log/:
- /opt/zimbra/log/zmmailboxd.out (jvm output log)
- /opt/zimbra/log/stacktrace.<pid>
In ZCS 4.5.x, the JVM output log and stacktrace files will be in /opt/zimbra/tomcat/logs/:
- /opt/zimbra/tomcat/logs/catalina.out (tomcat jvm output log)
- /opt/zimbra/tomcat/logs/stacktrace.<pid>
Utilities
Some C application debugging tools are useful for examining the state of current running processes. If you are experiencing issues with an unresponsive server, Zimbra Support may request that you run some or all of these utilities.
Note: Running these utilities may interfere with normal functioning of the ZCS applications involved.
- gdb
- gcore
- pstack
There are also utilities to examine the state of the operating system and specific applications.
To list open files on the system:
- lsof
To display statistics about currently running bdb databases (used by openldap, amavisd-new):
- db_stat
