Free space in /opt/zimbra/logs while huge trace log is enabled: Difference between revisions
(Created page with "{{WIP}}{{Article Infobox|{{admin}}|{{ZCS 8.6}}|{{ZCS 8.5}}|{{ZCS 8.0}}}} =Free space in /opt/zimbra/logs while huge trace log is enabled= ==Purpose== If you enable a deep trac...") |
No edit summary |
||
Line 1: | Line 1: | ||
{{ | {{BC|Certified}} | ||
__FORCETOC__ | |||
<div class="col-md-12 ibox-content"> | |||
=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|{{ZC}}|{{ZCS 8.6}}|{{ZCS 8.5}}|{{ZCS 8.0}}|}} | |||
{{WIP}} | |||
==Purpose== | ==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. | 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. |
Revision as of 18:36, 11 July 2015
Free space in /opt/zimbra/logs while huge trace log is enabled
- This article is a Work in Progress, and may be unfinished or missing sections.
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
- Link to a Bugzilla 63661