Difference between revisions of "Logger (ZCS 5.0.x and earlier)"

m
Line 2: Line 2:
  
 
=Setup=
 
=Setup=
 +
During installation, the zmsetup.pl script runs the zmloggerinit script, which A. creates the '''zimbra_logger''' database and the tables shown in the output below, and B. generates the zimbra and root mysql user passwords, and stores them in '''[[CLI_zmlocalconfig_%28Local_Configuration|zmlocalconfig]]'''.
 +
 
=Configuration=
 
=Configuration=
 +
==Multi-node Installations==
 +
In order to allow the log host to accept log messages from the other nodes, add the "-r" option to the SYSLOGD_OPTIONS line in /etc/sysconfig/syslog; for example:
 +
 +
SYSLOGD_OPTIONS="-r -m 0"
  
 
=Troubleshooting=
 
=Troubleshooting=

Revision as of 16:42, 16 March 2007

Although the logger is not essential for Zimbra to operate, this article will describe setup, configuration, and troubleshooting of the logger service.

Setup

During installation, the zmsetup.pl script runs the zmloggerinit script, which A. creates the zimbra_logger database and the tables shown in the output below, and B. generates the zimbra and root mysql user passwords, and stores them in zmlocalconfig.

Configuration

Multi-node Installations

In order to allow the log host to accept log messages from the other nodes, add the "-r" option to the SYSLOGD_OPTIONS line in /etc/sysconfig/syslog; for example:

SYSLOGD_OPTIONS="-r -m 0"

Troubleshooting

Accessing the logger MySQL database manually

$ logmysql zimbra_logger
mysql> show tables;
+-------------------------+
| Tables_in_zimbra_logger |
+-------------------------+
| amavis                  |
| amavis_aggregate        |
| config                  |
| disk_aggregate          |
| disk_status             |
| mta                     |
| mta_aggregate           |
| processing_history      |
| raw_logs                |
| service_status          |
+-------------------------+

Overview of logger pipeline

1. The mta components (postfix, amavis) and system status scripts (zmstatuslog, zmdisklog, zmqueuelog) log to /var/log/zimbra.log.

2. The logswatch script monitors /var/log/zimbra.log and sends new lines to the zmlogger script.

3. The zmlogger script inserts the log lines into the raw_logs table, and updates the service_status table, in the zimbra_logger database.

4. The zmlogprocess script breaks down the lines from the raw_logs table and inserts the data into the mta, mta_aggregate, amavis, amavis_aggregate, disk_status, disk_aggregate, and processing_history tables of the zimbra_logger db.

What queries the logger database

1. The zmdailyreport script processes data from the mta and amavis tables, and emails the results to root, which is normally an alias to the original zimbra admin account.

[zimbra@mail ~]$ crontab -l | grep zmdailyreport
10 1 * * * /opt/zimbra/libexec/zmdailyreport | /opt/zimbra/postfix/sbin/sendmail root
[zimbra@mail ~]$ zmprov getAccount admin | grep Alias
zimbraMailAlias: root@mail.domain.com
zimbraMailAlias: postmaster@mail.domain.com

2. The zmmsgtrace tool queries the mta and amavis tables and outputs basic info about matching messages.

3. The zmgengraphs script queries the disk_aggregate, mta_aggregate, and amavis_aggregate tables and creates images that will be displayed in the admin console.

4. Loading the admin console queries the service_status table, and viewing server statistics will display the graphs created by zmgengraphs.

[screenshot]
Jump to: navigation, search