[SOLVED] zimbra mailbox corrupt

[kkimani]

Hi all,

Am currently running zimbra 5.0.8. My server had an issue and was forced to run a checkup on the hard disk. everything went back to normal and the users mail was ok except for one inbox. It appears to have corrupted data .... check the print screen https://docs.google.com/Doc?docid=0A...NXdkM2dw&hl=en.
I have tried to transfer the mail to another mailbox but been unable. Please anyone with an idea please offer assistance.

Regards

[phoenix]

Please update your forum profile with the output of the following command (do not post it in this thread):

zmcontrol -v

What did you do to transfer the mail to another mailbox and what errors did you see? Are there any errors in any of the log files for this 'corrupt' mailbox or any other errors? Do you have a backup?

[kkimani]

zmcontrol -v
Release 5.0.8_GA_2462.RHEL5_20080709170039 CentOS5 FOSS edition

Was not transferring mail but the server crashed and had to do a file system check.
I dont have a backup since want to upgrade to zimbra 6 and the user was using IMAP hence all mail is in the server.
The maillog.out file displays the following when i try to reindex the mailbox

[zimbra@letter root]$ zmprov rim xxx@xxxx.org start
status: started

zmprov rim xxx@xxxx.org status
ERROR: service.NOT_IN_PROGRESS (mbox d6b68b4b-faff-4819-a348-fa35820674ab is not currently running action ReIndex)

"[root@letter ~]# tail -f /opt/zimbra/log/zmmailboxd.out
at com.mysql.jdbc.SQLError.createSQLException(SQLErro r.java:936)
at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.ja va:2870)
at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:15 73)
at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java :1665)
at com.mysql.jdbc.Connection.execSQL(Connection.java: 3124)
at com.mysql.jdbc.PreparedStatement.executeInternal(P reparedStatement.java:1149)
at com.mysql.jdbc.PreparedStatement.executeQuery(Prep aredStatement.java:1262)
at org.apache.commons.dbcp.DelegatingPreparedStatemen t.executeQuery(DelegatingPreparedStatement.java:20 5)
at com.zimbra.cs.db.DbMailItem.getFoldersAndTags(DbMa ilItem.java:1498)
... 5 more

com.zimbra.common.service.ServiceException: system failure: fetching folder data for mailbox 127
ExceptionId:Thread-5112:1266590370323:f6a82fac2ac00a12
Code:service.FAILURE
at com.zimbra.common.service.ServiceException.FAILURE (ServiceException.java:253)
at com.zimbra.cs.db.DbMailItem.getFoldersAndTags(DbMa ilItem.java:1585)
at com.zimbra.cs.mailbox.Mailbox.loadFoldersAndTags(M ailbox.java:1467)
at com.zimbra.cs.mailbox.Mailbox.beginTransaction(Mai lbox.java:1192)
at com.zimbra.cs.mailbox.Mailbox.beginTransaction(Mai lbox.java:1144)
at com.zimbra.cs.mailbox.Mailbox.reIndex(Mailbox.java :1756)
at com.zimbra.cs.service.admin.ReIndex$ReIndexThread. run(ReIndex.java:157)
Caused by: com.mysql.jdbc.exceptions.MySQLSyntaxErrorExceptio n: Table 'mboxgroup27.mail_item' doesn't exist

Query being executed when exception was thrown:

SELECT mi.id, mi.type, mi.parent_id, mi.folder_id, mi.index_id, mi.imap_id, mi.date, mi.size, mi.volume_id, mi.blob_digest, mi.unread, mi.flags, mi.tags, mi.subject, mi.name, mi.metadata, mi.mod_metadata, mi.change_date, mi.mod_content FROM mboxgroup27.mail_item AS mi WHERE mailbox_id = 127 AND type IN (1,2,13,3)
at com.mysql.jdbc.SQLError.createSQLException(SQLErro r.java:936)
at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.ja va:2870)
at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:15 73)
at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java :1665)
at com.mysql.jdbc.Connection.execSQL(Connection.java: 3124)
at com.mysql.jdbc.PreparedStatement.executeInternal(P reparedStatement.java:1149)
at com.mysql.jdbc.PreparedStatement.executeQuery(Prep aredStatement.java:1262)
at org.apache.commons.dbcp.DelegatingPreparedStatemen t.executeQuery(DelegatingPreparedStatement.java:20 5)
at com.zimbra.cs.db.DbMailItem.getFoldersAndTags(DbMa ilItem.java:1498)
... 5 more "

[phoenix]

Originally Posted by kkimani

zmcontrol -v
Release 5.0.8_GA_2462.RHEL5_20080709170039 CentOS5 FOSS edition

I asked you to put that in your forum profile not in this thread, please follow the link I gave you earlier and update your profile.

Originally Posted by kkimani

Was not transferring mail but the server crashed and had to do a file system check.

You said in your first post that "I have tried to transfer the mail to another mailbox but been unable." - what does that mean?

Originally Posted by kkimani

I dont have a backup since want to upgrade to zimbra 6 and the user was using IMAP hence all mail is in the server.

That's rather risky not having a backup, isn't it.

Have a look in /opt/zimbra/logger/db/data/ for any files with .err on the end and see what's in those files, you've probably got a corrupt MySQL database.

[kkimani]

I have updated my prifile..oops sorry for misuderstanding..

What i meant when i said transfer mail to another mail box was want to change the mailbox and address for the user to something else i.e a different username and address thus want to transfer all his mail to that address since all the mail is in the server and he cant access it using his client from either end.

About the upgrade, will ensure i make a backup soon before i try the upgrade.

Currently cant check the server for .err files since the site is offline since its a weekend and am offsite but will check them up on Monday morning.

Regards

Kevin

[kkimani]

Morning,

I have checked the server and there are no .err files

[uxbod]

Also check /opt/zimbra/log/mysql_error.log.

[kkimani]

it seems thats were the error is at. Here is the snippet of the log file...
"100221 15:22:22 InnoDB: error: space object of table mboxgroup27/pop3_message,
InnoDB: space id 355 did not exist in memory. Retrying an open.
100221 15:22:22 InnoDB: Operating system error number 2 in a file operation.
InnoDB: The error means the system cannot find the path specified.
100221 15:22:22 InnoDB: Error: trying to open a table, but could not
InnoDB: open the tablespace file './mboxgroup27/pop3_message.ibd'!
InnoDB: Have you moved InnoDB .ibd files around without using the
InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE?
InnoDB: It is also possible that this is a temporary table #sql...,
InnoDB: and MySQL removed the .ibd file for this.
InnoDB: Please refer to
InnoDB: MySQL :: MySQL 5.0 Reference Manual :: 13.2.13.3 InnoDB General Troubleshooting
InnoDB: for how to resolve the issue.
100221 15:22:22 InnoDB: error: space object of table mboxgroup27/tombstone,
InnoDB: space id 353 did not exist in memory. Retrying an open.
100221 15:22:22 InnoDB: Operating system error number 2 in a file operation.
InnoDB: The error means the system cannot find the path specified.
100221 15:22:22 InnoDB: Error: trying to open a table, but could not
InnoDB: open the tablespace file './mboxgroup27/tombstone.ibd'!
InnoDB: Have you moved InnoDB .ibd files around without using the
InnoDB: commands DISCARD TABLESPACE and IMPORT TABLESPACE?
InnoDB: It is also possible that this is a temporary table #sql...,
InnoDB: and MySQL removed the .ibd file for this.
InnoDB: Please refer to
InnoDB: MySQL :: MySQL 5.0 Reference Manual :: 13.2.13.3 InnoDB General Troubleshooting
InnoDB: for how to resolve the issue."

[veronica]

> Caused by: com.mysql.jdbc.exceptions.MySQLSyntaxErrorExceptio n: Table 'mboxgroup27.mail_item' doesn't exist

You seem to have corrupted mboxgroup27.mail_item. Can you connect to the mboxgroup27 database and select * from mail_item ?

[uxbod]

What files exist under /opt/zimbra/db/data/mboxgroup27 ?