| Welcome to the Zimbra :: Forums! | |
Welcome, if you would like to post a comment please register.
We also encourage you to explore all things Zimbra with our team and members of the community.
|  | | 
04-16-2008, 01:56 PM
| | | I have the same issue as everyone else here. Everything in this thread seems fine, and the only thing in the zmstat.out file is the "Warning: Not possible to monitor process stats" error over and over.
I am missing the same files everyone else is missing.
logmysql connects with no problem and I have also manually verified the MySQL password. All the tables seem clean.
I have tried restarting the zmlogger and zmstats services and I just get a new instance of the above warning message. I can't find any other logging related errors.
Please let me know if I can post any additional output or data.
Thanks,
-Scott | 
04-16-2008, 02:58 PM
| | | I have a similar issue with the stats not appearing in the Admin Console. I looked in /tmp/logprocess.out and found this error (repeated many times), please advise: Code: Table './zimbra_logger/mta' is marked as crashed and last (automatic?) repair failed
Table './zimbra_logger/mta' is marked as crashed and last (automatic?) repair failed at /opt/zimbra/libexec/zmlogprocess line 1133. | 
04-16-2008, 11:11 PM
| | | yes, maybe this is related to our problem: Code: # cat /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 1132.
Can't call method "fetchall_arrayref" on an undefined value at /opt/zimbra/libexec/zmlogprocess line 768.
Pruning service/server entries older then 2008-04-17 06:50:01
server maps to server.example.com
Processing mta entries from 1947272
Error executing select distinct(postfix_qid) from raw_logs where postfix_qid is not null and app like 'postfix%' and id > '1947272' 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 1133. | 
04-17-2008, 01:16 AM
| | Zimbra Consultant & Moderator | |
Posts: 19,655
| | Have any of you tried the following: Code: su - zimbra
/opt/zimbra/libexec/zmlogprocess
/opt/zimbra/libexec/zmgengraphs Are there any errors in /opt/zimbra/logger/db/data/<hostname>.err? You could also try some of the tips in the Troubleshooting Section of the wiki and see if the tables are OK.
__________________
Regards
Bill
| 
04-17-2008, 01:36 AM
| | | Quote:
Originally Posted by phoenix Have any of you tried the following: Code: su - zimbra
/opt/zimbra/libexec/zmlogprocess
/opt/zimbra/libexec/zmgengraphs Are there any errors in /opt/zimbra/logger/db/data/<hostname>.err? You could also try some of the tips in the Troubleshooting Section of the wiki and see if the tables are OK. |
Bingo! I found in .err file this: Code: /opt/zimbra/logger/mysql/libexec/mysqld: Table './zimbra_logger/raw_logs' is marked as crashed and should be repaired
-> Repairing the tables in the logger database Code: $ logmysql zimbra_logger
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 | 1 client is using or hasn't closed the table properly |
| zimbra_logger.raw_logs | check | error | Record at pos: 11932 is not remove-marked |
| zimbra_logger.raw_logs | check | error | record delete-link-chain corrupted |
| zimbra_logger.raw_logs | check | error | Corrupt |
+------------------------+-------+----------+-------------------------------------------------------+
5 rows in set (0.02 sec)
mysql> repair table raw_logs;
+------------------------+--------+----------+---------------------------------------------+
| Table | Op | Msg_type | Msg_text |
+------------------------+--------+----------+---------------------------------------------+
| zimbra_logger.raw_logs | repair | info | Delete link points outside datafile at 4080 |
| zimbra_logger.raw_logs | repair | warning | Number of rows changed from 215 to 263 |
| zimbra_logger.raw_logs | repair | status | OK |
+------------------------+--------+----------+---------------------------------------------+
3 rows in set (0.07 sec)
mysql> check table raw_logs;
+------------------------+-------+----------+----------+
| Table | Op | Msg_type | Msg_text |
+------------------------+-------+----------+----------+
| zimbra_logger.raw_logs | check | status | OK |
+------------------------+-------+----------+----------+
1 row in set (0.00 sec) But when i run zmlogprocess manualy i get new errors: Code: $ /opt/zimbra/libexec/zmlogprocess
Pruning service/server entries older then 2008-04-17 09:24:20
server maps to server.example.com
Processing mta entries from 1947272
Found 16 messages
DBD::mysql::st execute failed: Incorrect key file for table './zimbra_logger/mta.MYI'; try to repair it at /opt/zimbra/libexec/zmlogprocess line 1132.
Error executing insert into mta (arrive_time, leave_time, host, msgid, sender, recipient, amavis_pid, bytes, from_host, from_IP, to_host, to_IP, qid, status, statusmsg) values (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?) with 2008-03-25 10:55:02 2008-03-25 10:55:03 dog 20080325095457.063445CAE4@server.example.com nagios@ucetnictvi-on-line.cz archive@ucetnictvi-on-line.cz 1110 localhost 127.0.0.1 server.example.com 82.113.47.156]:7025 C014A5C097 sent (250 2.1.5 OK)
Incorrect key file for table './zimbra_logger/mta.MYI'; try to repair it
Incorrect key file for table './zimbra_logger/mta.MYI'; try to repair it at /opt/zimbra/libexec/zmlogprocess line 1133. | 
04-17-2008, 01:46 AM
| | | I found other tables also corrupted, so i did recover them.
Zmlogprocess and zmgengraphs doesn't generate errors now, so i think it helps.
Now i will wait for graphs  | 
04-17-2008, 01:52 AM
| | | Quote:
Originally Posted by boblin I found other tables also corrupted, so i did recover them.
Zmlogprocess and zmgengraphs doesn't generate errors now, so i think it helps.
Now i will wait for graphs  | Which tables did you found corrupt ?
Can you give us/me the commands ? 
Thanks. | 
04-17-2008, 01:56 AM
| | | from wiki: Code: $ logmysql zimbra_logger
mysql> show tables;
+-------------------------+
| Tables_in_zimbra_logger |
+-------------------------+
| amavis |
| amavis_aggregate |
| config |
| disk_aggregate |
| disk_status |
| mta |
| mta_aggregate |
| processing_history |
| raw_logs |
| service_status |
+-------------------------+ So i check all the tables, one by one like in my previous post, and repair corrupted table. | 
04-17-2008, 02:02 AM
| | | Quote:
Originally Posted by boblin from wiki: Code: $ logmysql zimbra_logger
mysql> show tables;
+-------------------------+
| Tables_in_zimbra_logger |
+-------------------------+
| amavis |
| amavis_aggregate |
| config |
| disk_aggregate |
| disk_status |
| mta |
| mta_aggregate |
| processing_history |
| raw_logs |
| service_status |
+-------------------------+ So i check all the tables, one by one like in my previous post, and repair corrupted table. | Ah great  Thanks, I will do the same then  | 
04-17-2008, 03:47 AM
| | | Stats are working again!
Thank you! | | Thread Tools | Search this Thread | | | | | Display Modes | Linear Mode | | Why Join? Registering let's you ask questions, makes it easier to search, displays any files attached to posts, and notifies you about replies.  |