Repair Logger Data Corruption
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 in 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;
If this repair step succeeds, you do not need to perform the next step.
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;
MySQL 5.0 Reference Manual http://dev.mysql.com/doc/refman/5.0/en/repair-table.html
Keywords: logger, database, mysql, error, raw_logs, corrupt, index