Archived community.zenoss.org | full text search
Skip navigation
Currently Being Moderated

14.6 Maintenance and Performance Tuning

VERSION 1 
Created on: Aug 5, 2010 7:51 AM by Zenoss API - Last Modified:  Aug 5, 2010 7:51 AM by Zenoss API

 6. Maintenance and Performance Tuning

Read the following sections for maintenance and tuning suggestions.

 6.1. Packing the ZEO Database

The ZEO database should be packed periodically to reclaim space. To do this you should set up a cron job that runs the following command weekly:

$ZENHOME/bin/zeopack.py -p 8100

 6.2. Log Rotate Script

The logrotate script must be present and running to rotate the Zope log (event.log), ZEO log (zeo.log), and access log (Z2.log).

 6.2.1. Zenoss 2.4.x

At installation, the system adds the following script to the /etc/logrotate.d/zenoss file (where ZENHOME varies depending on your installation platform):

**ZENHOME**/log/event.log **ZENHOME**/log/Z2.log **ZENHOME**/log/zeo.log{
    missingok
    weekly
    rotate 2
    copytruncate
    }

In version 2.4.x, each daemon performs its own log rotation. You can customize rotation parameters by inserting the following directives in each daemon's configuration file, located in the $ZENHOME/etc file:

Directive Description
--maxlogsize=MAXLOGKILOBYTESSpecifies the maximum size of the log file, in kilobytes. By default, the maximum is 10240 KB.
--maxbackuplogs=MAXBACKUPLOGSSpecifies the maximum number of backup log files. By default, the maximum is 3.

If you do not specify a directive, then the system uses the default values.

 6.2.2. Zenoss 2.3.3 and Earlier

The logrotate script should be present in your installation, in the /etc/logrorate.d/zenoss file. For example, for a CentOS/RHEL, RPM-based installation, the following script should be present:

/opt/zenoss/log/*.log /opt/zenoss/log/*/*.log {
missingok
weekly
rotate 2
copytruncate
}
Comments (0)