[SOLVED] Empty admin report

[dljordaneku]

check out /tmp/logprocess.out
Probably have a corrupt database

I have been getting empty daily reports since my server crashed about a month ago. I have upgraded to 5.0.8 since then hoping that would fix it but it hasn't. I tried to run the logprocess.out but I get permission denied.

dj

[mcesari]

dont run it just 'cat /tmp/logprocess.out'

[dljordaneku]

dont run it just 'cat /tmp/logprocess.out'

yea just realized that I ran it and then repaired the mta table. we will see what happens now.

can I run a repair on the tables that was listed as having errors in my database check? I listed the errors here


dj

[dljordaneku]

Ok. due to some fileserver issues our Zimbra crashed the other day and now my daily report is blank again I checked the tmp/logprocessout and this is what I have.

DBD::mysql::st execute failed: Table './zimbra_logger/mta' is marked as crashed and last (automatic?) repair failed at /opt/zimbra/libexec/zmlogprocess line 1134.
DBD::mysql::st execute failed: Table './zimbra_logger/mta' is marked as crashed and last (automatic?) repair failed at /opt/zimbra/libexec/zmlogprocess line 1134.
DBD::mysql::st execute failed: Table './zimbra_logger/mta' is marked as crashed and last (automatic?) repair failed at /opt/zimbra/libexec/zmlogprocess line 1134.
DBD::mysql::st execute failed: Table './zimbra_logger/mta' is marked as crashed and last (automatic?) repair failed at /opt/zimbra/libexec/zmlogprocess line 1134.
DBD::mysql::st execute failed: Table './zimbra_logger/mta' is marked as crashed and last (automatic?) repair failed at /opt/zimbra/libexec/zmlogprocess line 1134.
DBD::mysql::st execute failed: Table './zimbra_logger/mta' is marked as crashed and last (automatic?) repair failed at /opt/zimbra/libexec/zmlogprocess line 1134.
Pruning service/server entries older then 2008-10-21 08:30:05

dj

[mmorse]

su - zimbra
logmysql zimbra_logger
repair table mta;
check table mta;

Still bad then you might:
repair table mta USE_FRM;

If still nothing let us know and we'll provide directions to recreate the mta table or re-init the entire db, though you'd loose any existing logger data if you do so.