Troubleshooting Course Content Rough Drafts-Zimbra Logs: Difference between revisions
(Created page with "=Introduction= {{Article_Footer|Zimbra Collaboration Suite 8.6|01/22/2015}} Category:Troubleshooting_Course_Content_Rough_Drafts") |
No edit summary |
||
Line 4: | Line 4: | ||
{{Article_Footer|Zimbra Collaboration Suite 8.6|01/22/2015}} | {{Article_Footer|Zimbra Collaboration Suite 8.6|01/22/2015}} | ||
[[Category:Troubleshooting_Course_Content_Rough_Drafts]] | [[Category:Troubleshooting_Course_Content_Rough_Drafts]] | ||
== Log File == | |||
Brief list of the major log files in Zimbra and what they contain | |||
* /opt/zimbra/log/mailbox.log - Zimbra Mailboxd (jetty) writes all mailbox activity to this log file. This activity can be anything from moving a message to deletion of an account. | |||
* /opt/zimbra/log/zmmailboxd.out – Mailboxd(jetty) logs to this file during startup. | |||
* /opt/zimbra/log/audit.log – Logs authentication activity. | |||
* /opt/zimbra/log/sync.log – Mobile sync operations get logged to this log file. | |||
* /opt/zimbra/log/clamd.log – Clamd (Antivirus daemon) logs all antivirus activity to this file. | |||
* /opt/zimbra/log/freshclam.log – Antivirus definition update. | |||
* /opt/zimbra/log/mysql_error.log – Mysql errors and startup messages. This log should be looked up to determine if innodb corruption has occurred. | |||
* /opt/zimbra/log/myslow.log – Consists sql statements which took more than long_query_time seconds (zimbra default – 1second) to execute and required atleast min_examined_row_limit (zimbra default - 0) rows to be examined. | |||
* /opt/zimbra/log/nginx.access.log - NGINX writes information about client requests after the request is processed. | |||
* /opt/zimbra/log/nginx.log – Nginx error log which defaults to “info” in Zimbra. | |||
* /opt/zimbra/log/spamtrain.log – Spam training log. | |||
* /opt/zimbra/log/ews.log – EWS server side activity. | |||
* /var/log/zimbra.log – All MTA (Postfix, amavisd, antispam, antivirus,cyrus-sasl)/Ldap logs go to this file. | |||
* /var/log/zimbra-stats.log – Logger data gets logged to this file. | |||
== Log Rotation == | |||
Two different log rotation daemons handle log rotation of the zimbra log files. | |||
* Log4j | |||
** Log4j is responsible for logging to mailbox.log, audit.log, sync.log, synctrace.log,webxml.log and ews.log. For config : /opt/zimbra/conf/log4j.properties | |||
Example, below the are the config options for the rotation of /opt/zimbra/log/mailbox.log | |||
log4j.appender.LOGFILE=org.apache.log4j.rolling.RollingFileAppender | |||
log4j.appender.LOGFILE.RollingPolicy=org.apache.log4j.rolling.TimeBasedRollingPolicy | |||
log4j.appender.LOGFILE.RollingPolicy.FileNamePattern=/opt/zimbra/log/mailbox.log.%d{yyyy-MM-dd} | |||
log4j.appender.LOGFILE.File=/opt/zimbra/log/mailbox.log | |||
log4j.appender.LOGFILE.layout=com.zimbra.common.util.ZimbraPatternLayout | |||
log4j.appender.LOGFILE.layout.ConversionPattern=%d %-5p [%t] [%z] %c{1} - %m%n | |||
== Debug Logging == | |||
=== Mailbox === | |||
=== Ldap === | |||
=== Postfix === | |||
=== Amavis === | |||
=== Proxy === | |||
== ZCO Logs == |
Revision as of 11:57, 27 February 2015
Introduction
Log File
Brief list of the major log files in Zimbra and what they contain
- /opt/zimbra/log/mailbox.log - Zimbra Mailboxd (jetty) writes all mailbox activity to this log file. This activity can be anything from moving a message to deletion of an account.
- /opt/zimbra/log/zmmailboxd.out – Mailboxd(jetty) logs to this file during startup.
- /opt/zimbra/log/audit.log – Logs authentication activity.
- /opt/zimbra/log/sync.log – Mobile sync operations get logged to this log file.
- /opt/zimbra/log/clamd.log – Clamd (Antivirus daemon) logs all antivirus activity to this file.
- /opt/zimbra/log/freshclam.log – Antivirus definition update.
- /opt/zimbra/log/mysql_error.log – Mysql errors and startup messages. This log should be looked up to determine if innodb corruption has occurred.
- /opt/zimbra/log/myslow.log – Consists sql statements which took more than long_query_time seconds (zimbra default – 1second) to execute and required atleast min_examined_row_limit (zimbra default - 0) rows to be examined.
- /opt/zimbra/log/nginx.access.log - NGINX writes information about client requests after the request is processed.
- /opt/zimbra/log/nginx.log – Nginx error log which defaults to “info” in Zimbra.
- /opt/zimbra/log/spamtrain.log – Spam training log.
- /opt/zimbra/log/ews.log – EWS server side activity.
- /var/log/zimbra.log – All MTA (Postfix, amavisd, antispam, antivirus,cyrus-sasl)/Ldap logs go to this file.
- /var/log/zimbra-stats.log – Logger data gets logged to this file.
Log Rotation
Two different log rotation daemons handle log rotation of the zimbra log files.
- Log4j
- Log4j is responsible for logging to mailbox.log, audit.log, sync.log, synctrace.log,webxml.log and ews.log. For config : /opt/zimbra/conf/log4j.properties
Example, below the are the config options for the rotation of /opt/zimbra/log/mailbox.log
log4j.appender.LOGFILE=org.apache.log4j.rolling.RollingFileAppender log4j.appender.LOGFILE.RollingPolicy=org.apache.log4j.rolling.TimeBasedRollingPolicy log4j.appender.LOGFILE.RollingPolicy.FileNamePattern=/opt/zimbra/log/mailbox.log.%d{yyyy-MM-dd} log4j.appender.LOGFILE.File=/opt/zimbra/log/mailbox.log log4j.appender.LOGFILE.layout=com.zimbra.common.util.ZimbraPatternLayout log4j.appender.LOGFILE.layout.ConversionPattern=%d %-5p [%t] [%z] %c{1} - %m%n