Free space in /opt/zimbra/logs while huge trace log is enabled

Free space in /opt/zimbra/logs while huge trace log is enabled

   KB 21751        Last updated on 09/19/2016  




0.00
(0 votes)

Purpose

If you enable a deep trace_log, the /opt/zimbra/log partition could be filled quickly, turning into a huge problem for the performance of the system.

Resolution

To deal with huge trace_log files eating up your /opt/zimbra partition, add the next into the Zimbra Crontab. As Zimbra user

crontab -e
# Cleanup stack trace 
33 10 * * * find /opt/zimbra/log/ -name \*.trace.log -mtime +2 -exec rm -f {} \; > /dev/null 2>&1 
# Cleanup access logs 
36 10 * * * find /opt/zimbra/log/ -name access_log.\* -mtime +2 -exec rm -f {} \; > /dev/null 2>&1

Do not forget to delete these lines if you turn on the regular log level again.

Additional Content


Verified Against: Zimbra Collaboration 8.6, 8.5, 8.0 Date Created: 03/10/2015
Article ID: https://wiki.zimbra.com/index.php?title=Free_space_in_/opt/zimbra/logs_while_huge_trace_log_is_enabled Date Modified: 09/19/2016



Try Zimbra

Try Zimbra Collaboration with a 60-day free trial.
Get it now »

Want to get involved?

You can contribute in the Community, Wiki, Code, or development of Zimlets.
Find out more. »

Looking for a Video?

Visit our YouTube channel to get the latest webinars, technology news, product overviews, and so much more.
Go to the YouTube channel »


Wiki/KB reviewed by Gayle B Jorge Jenny Last edit by Shanxt
Jump to: navigation, search