status not updating properly

[lithorus]

We were having the excact same issue but found out that the cron daemon wasn't running. Backups were not done either

[hodd]

I did some reading on Logger - Zimbra :: Wiki
And took the advice of checking the mysql tables.

Here's the output:

mysql> check table raw_logs;
+------------------------+-------+----------+-------------------------------------------------------------------------------+
| Table                  | Op    | Msg_type | Msg_text                                                                      |
+------------------------+-------+----------+-------------------------------------------------------------------------------+
| zimbra_logger.raw_logs | check | warning  | Table is marked as crashed                                                    |
| zimbra_logger.raw_logs | check | warning  | 3 clients are using or haven't closed the table properly                      |
| zimbra_logger.raw_logs | check | error    | Can't read key from filepos: 3407872                                          |
| zimbra_logger.raw_logs | check | Error    | Incorrect key file for table './zimbra_logger/raw_logs.MYI'; try to repair it |
| zimbra_logger.raw_logs | check | error    | Corrupt                                                                       |
+------------------------+-------+----------+-------------------------------------------------------------------------------+
5 rows in set (0.36 sec)

I then did a

repair table raw_logs;

And it's been running that for almost 30 minutes now...was that a bad idea?

[hodd]

So after 2 hours I got this

mysql> repair table raw_logs;

+------------------------+--------+----------+--------------------------------------------------+
| Table                  | Op     | Msg_type | Msg_text                                         |
+------------------------+--------+----------+--------------------------------------------------+
| zimbra_logger.raw_logs | repair | warning  | Number of rows changed from 21425438 to 18347072 |
| zimbra_logger.raw_logs | repair | status   | OK                                               |
+------------------------+--------+----------+--------------------------------------------------+
2 rows in set (1 hour 58 min 54.17 sec)

[hodd]

I thought maybe upgrading from 5.0.13 to 5.0.15 might fix up my issues, but from the output below it looks like I have a deeper problem. Has anyone else experienced the logger errors I'm having and the association to no stats being displayed?

Do you want to verify logger database integrity? [Y]
Verifying integrity of logger database.  This may take a while.
mysqld is alive
Generating report
Logger Database errors found.
/opt/zimbra/logger/mysql/bin/mysqlcheck --defaults-file=/opt/zimbra/conf/my.logger.cnf -S /opt/zimbra/logger/db/mysql.sock -A -C -s -u root --password=.***omited** --auto-repair
zimbra_logger.mta
 warning  : 2 clients are using or haven't closed the table properly
 zimbra_logger.processing_history
 warning  : 3 clients are using or haven't closed the table properly
 zimbra_logger.service_status
 warning  : 6 clients are using or haven't closed the table properly

[uxbod]

su - zimbra
logmysql
use zimbra_logger;
repair table mta;
repair table processing_history;
repair table service_status;
exit

[hodd]

uxbod thanks for the quick reply, I performed those commands on the database, and restarted the services. I still however do not see any stats on the Mesage Count, Message Volume, or AS/AV tabs. I've read else where that it does take some time for them to refresh.

[uxbod]

Yep it can take 24 hours.

[lithorus]

uxbod thanks for the quick reply, I performed those commands on the database, and restarted the services. I still however do not see any stats on the Mesage Count, Message Volume, or AS/AV tabs. I've read else where that it does take some time for them to refresh.

Did you check if cron was running on the server? As said earlier we had the same issue when cron didn't run on the server. All stats are basically updated through a cron script.