[SOLVED] running a version 4.5.6 or prior? Prevent Large Log File

[mmorse]

It's relatively ok to delete that log - When you have the time, I would get yourself on 4.5.10 at the minimum, even if your not ready for the 5.0 jump yet.

[padraig]

Originally Posted by alexc1103

Thanks for the tips with the zmmtaconfig.log, mine was 6.1G and making the nightly backup take forever! Backup times are down now and the zimbra directory down from 9.1G to 3G

Hi alexc1103,

What do you use for backups is it the default zmbackup if so does this backup log files?
as well as user data?

Thanks,
Padraig.

[fajarpri]

Thanks mmorse

@padraig:
Sorry for jumping in, since my /opt/zimbra resides on LVM, I use the LVM backup script. It's in the Forum. Search for 'backup lvm'
It will backup the whole zimbra directories including the logs.

[bjared]

I'm running 4.5.10, and I have two log files that have entries as early as February 2007:

[zimbra@zimbra1 log]$ ls -alh zmconvertd.log
-rw-rw-r-- 1 zimbra zimbra 372M Jan 9 15:07 zmconvertd.log
[zimbra@zimbra1 log]$ ls -alh zmmtaconfig.log
-rw-rw-r-- 1 zimbra zimbra 5.4G Jan 9 15:07 zmmtaconfig.log

They're still getting appended to, so I'm not sure what exactly 4.5.10 is supposed
to fix with these files? Zimbra seems to rotate the other logs. I think I'm going
to add my own entries into /etc/logrotate.d/zimbra for these files I guess:

/opt/zimbra/log/zmmtaconfig.log {
daily
missingok
copytruncate
notifempty
create 0644 zimbra zimbra
compress
size 5000k
rotate 7
}

/opt/zimbra/log/zmconvertd.log {
daily
missingok
copytruncate
notifempty
create 0644 zimbra zimbra
compress
size 5000k
rotate 7
}

That should take care of those. Was their omission from the logrotate config
file an oversight, or planned?

--Brian

[mmorse]

4.5.7+ lowered the log intensity level: Bug 18445 - zmmtaconfig default loglevel is set to high
5.0.0 (& minor change for 5.0.1) added log rotation: Bug 10398 - clean up logging for swatch, zmmtaconfig

[fajarpri]

Thanks bjared for the sharing.
I'll add it into mine.