You can remove logs to make some space urgently to prevent your Zimbra from crash.
du -sh /var/log
Please pay special attention to the DOT after file names
rm -rf /var/log/zimbra.log.* rm -rf /var/log/messages.* rm -rf /var/log/maillog.* rm -rf /var/log/rpmpkgs.* rm -rf /var/log/boot.log.* rm -rf /var/log/cron.*
Null current logs.
cat /dev/null > /var/log/maillog cat /dev/null > /var/log/messages cat /dev/null > /var/log/zimbra.log cat /dev/null > /var/log/cbpolicyd.log
Remove zimbra other logs
rm -rf /opt/zimbra/log/zmswatch.out.* rm -rf /opt/zimbra/log/myslow.log.* rm -rf /opt/zimbra/log/zmmailboxd.out.* rm -rf /opt/zimbra/log/mailbox.log.* rm -rf /opt/zimbra/log/audit.log.* rm -rf /opt/zimbra/log/zmmtaconfig.log.* rm -rf /opt/zimbra/log/zmlogswatch.out.* du -sh /opt/zimbra/log
Remove zibra stats
du -sh /opt/zimbra/zmstat rm -rf /opt/zimbra/zmstat/2014-* rm -rf /opt/zimbra/zmstat/2015-* rm -rf /opt/zimbra/zmstat/2016-* du -sh /opt/zimbra/zmstat
Similar Posts:
- zmstat high cpu usage and huge file zmstat.out
- Zimbra reports “ Error: Queue report unavailable – mail system is down ”
- how to manage exim message queue
- How to block SASL login attacks in zimbra using csf
- How to clear Zimbra mailbox
11,014