[SOLVED] Empty admin report

[ghanedan]

Hi,

Version 4.5.5

I am receiving empty daily admin reports since last month.


Generating report
From 2007-11-27 00:00:00 to 2007-11-28 00:00:00

No messages found

what may be causing this ?

[mcesari]

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

[ghanedan]

This is what I have in /tmp/logprocess.out

DBD::mysql::st execute failed: Table './zimbra_logger/raw_logs' is marked as crashed and should be repaired at /opt/zimbra/libexec/zmlogprocess line 1040.
Can't call method "fetchall_arrayref" on an undefined value at /opt/zimbra/libexec/zmlogprocess line 780.
Pruning service/server entries older then 2007-12-05 16:20:03
mail maps to <mymailserver>
Processing mta entries from 16506438
Error executing select distinct(postfix_qid) from raw_logs where postfix_qid is not null and app like 'postfix%' and id > '16506438' with
Table './zimbra_logger/raw_logs' is marked as crashed and should be repaired
Table './zimbra_logger/raw_logs' is marked as crashed and should be repaired at /opt/zimbra/libexec/zmlogprocess line 1041.

[mcesari]

yup you need to repair the table.

there is probably a way to do this in one line but I do this as zimbra.
$ logmysql zimbra_logger
mysql> repair table raw_logs;

after it is repaired you can run '/opt/zimbra/libexec/zmdailyreport' to see if it will generate a log.
It may take some times to build some info after the repair

[ghanedan]

logger seems ok now with the following logs in /tmp/logprocess.out

...
Aggregating day amavis from 2007-12-04 00:00:00 to 2007-12-05 00:00:00
Aggregating hour disk from 2007-12-05 16:00:00 to 2007-12-05 17:00:00
Aggregating day disk from 2007-12-04 00:00:00 to 2007-12-05 00:00:00
Retaining 31 days worth of raw logs based on zimbraLogRawLifetime config.
Retaining 730 days worth of summary logs based on zimbraLogSummaryLifetime config.
Pruning raw mta logs from 2007-11-04 00:00:00
Pruning raw amavis logs from 2007-11-04 00:00:00
Pruning raw disk logs from 2007-11-04 00:00:00
Pruning summary mta logs from 2005-12-05 00:00:00
Pruning summary amavis logs from 2005-12-05 00:00:00
Pruning summary disk logs from 2005-12-05 00:00:00
Pruning other raw logs from 2007-11-04 00:00:00

but I still have no messages in admin report. Waited about 30 mins.

[mcesari]

that looks good so you will probably get a report now.

you could try running zmdailyreport -t and a date like 20070101, but since your raw_logs were messed up it might not have any data.

[ghanedan]

Ok I will wit until next morning,

I think it is probably solved, thanks for the great help.

[Nextasy]

Originally Posted by mcesari

that looks good so you will probably get a report now.

you could try running zmdailyreport -t and a date like 20070101, but since your raw_logs were messed up it might not have any data.

Hi

i also have every day an empty daily mail report. Tried it with repairing the database with no effect.

It seems, that he didnt create /tmp/logprocess.out. Logger ist running. System is 5.0.0.GA. Tried it with zmdailyreport, zmdailyreport -t and zmdailyreport -m

Table raw_logs seems to be ok. select * from raw_logs looks good

//Edit
Hmm....after a while, he created the logprocess file with these error

DBD::mysql::st execute failed: Table './zimbra_logger/service_status' is marked as crashed and should be repaired at /opt/zimbra/lib
exec/zmlogprocess line 1132.
DBD::mysql::st execute failed: Table './zimbra_logger/service_status' is marked as crashed and should be repaired at /opt/zimbra/lib
exec/zmlogprocess line 1132.
Can't call method "fetchall_arrayref" on an undefined value at /opt/zimbra/libexec/zmlogprocess line 82.
Pruning service/server entries older then 2008-01-03 11:40:03
Error executing delete from service_status where time <= '2008-01-03 11:40:03' with
Table './zimbra_logger/service_status' is marked as crashed and should be repaired
Table './zimbra_logger/service_status' is marked as crashed and should be repaired at /opt/zimbra/libexec/zmlogprocess line 1133.

Error executing select distinct loghostname, server from service_status with
Table './zimbra_logger/service_status' is marked as crashed and should be repaired
Table './zimbra_logger/service_status' is marked as crashed and should be repaired at /opt/zimbra/libexec/zmlogprocess line 1133.

i repaired the table with no effect

mysql> repair table service_status;
+------------------------------+--------+----------+-------------------------------------------------------+
| Table | Op | Msg_type | Msg_text |
+------------------------------+--------+----------+-------------------------------------------------------+
| zimbra_logger.service_status | repair | warning | Duplicate key for record at 292 against record at 144 |
| zimbra_logger.service_status | repair | warning | Number of rows changed from 1484 to 7 |
| zimbra_logger.service_status | repair | status | OK |
+------------------------------+--------+----------+-------------------------------------------------------+
3 rows in set (0.00 sec)

mysql> exit
Bye
zimbra@server:~$ /opt/zimbra/libexec/zmdailyreport
Generating report
From 2008-01-02 00:00:00 to 2008-01-03 00:00:00

No messages found
zimbra@server:~$ /opt/zimbra/libexec/zmdailyreport -t 20070101,20070201
Generating report
From 2007-01-01 00:00:00 to 2007-02-01 00:00:00

[Nextasy]

i am sorry. The daily report is working right now - it takes a long time to complete ;-(

[sine]

Hello. I have also this problem,

$ /opt/zimbra/libexec/zmdailyreport
Generating report
From 2008-02-24 00:00:00 to 2008-02-25 00:00:00

No messages found

But when I tryied all from above solutions (3 days ago), nothing changed.

logmysql zimbra_logger
repair table service_status;
repair table raw_logs;

In /tmp/logprocess.out I have nothing about corrupted database. Do you have any ideas?