Repair Logger Data Corruption

Revision as of 02:05, 26 November 2007 by Jason (talk | contribs)


Frequent write activity on the zimbra_logger.raw_logs table cause it to be subject index corruption certain conditions. Those conditions include but may not be limited to 100% disk utilization, abrupt end to the MySQL logger process, or other system failure. If the logger database is experiencing corruption, the raw_logs table is the likely culprit, however other tables can be affected as well. Trouble with the logger database is reported in /opt/zimbra/logger/db/data/hostname.err.


Any data or index corruption on the logger DB will result in inaccurate or missing statistics.


Diagnose problematic table hostname.err

070927 14:30:01 [ERROR] /opt/zimbra/logger/mysql/libexec/mysqld: Table './zimbra_logger/raw_logs' is marked as crashed and last (automatic?) repair failed

Attempt table repair

$ logmysql zimbra_logger
mysql> REPAIR TABLE raw_logs;

Repair table by writing a new index file

This repair method creates a new .MYI index file using the .frm file for the table. Use this option only as a last resort.

mysql> REPAIR TABLE raw_logs USE_FRM;

Related Articles

Mysql Crash Recovery


MySQL 5.0 Reference Manual

Keywords: logger, database, mysql, error, raw_logs, corrupt, index

Verified Against: Zimbra Collaboration Suite 4.5.9 Date Created: 11/25/2007
Article ID: Date Modified: 2007-11-26

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 »

Jump to: navigation, search