Mysql table error

Discuss your pilot or production implementation with other Zimbra admins or our engineers.
eranga
Posts: 22
Joined: Sat Sep 13, 2014 3:20 am

Mysql table error

Postby eranga » Mon Dec 21, 2015 1:47 am

One of our servers has an issue delivering emails to certain users. There is an error in the mysql_error.log.



Ubuntu 12.04 


Release 8.0.7.GA.6021.UBUNTU12.64 UBUNTU12_64 FOSS edition


[ERROR] Got error 179 when reading table './mboxgroup17/open_conversation'


Also there are other errors in the mailbox.log as well.


2015-12-21 00:04:42,214 WARN [LmtpServer-99969] [name=starg2@star.lk;mid=17;ip=172.17.0.34;] filter - An error occurred while processing filter rules. Filing message to /Inbox.
com.zimbra.cs.filter.ZimbraSieveException
at com.zimbra.cs.filter.ZimbraMailAdapter.executeActions(ZimbraMailAdapter.java:279)
at org.apache.jsieve.SieveFactory.evaluate(SieveFactory.java:173)
at com.zimbra.cs.filter.RuleManager.applyRulesToIncomingMessage(RuleManager.java:360)
at com.zimbra.cs.filter.RuleManager.applyRulesToIncomingMessage(RuleManager.java:322)
at com.zimbra.cs.lmtpserver.ZimbraLmtpBackend.deliverMessageToLocalMailboxes(ZimbraLmtpBackend.java:612)
at com.zimbra.cs.lmtpserver.ZimbraLmtpBackend.deliver(ZimbraLmtpBackend.java:382)
at com.zimbra.cs.lmtpserver.LmtpHandler.processMessageData(LmtpHandler.java:376)
at com.zimbra.cs.lmtpserver.TcpLmtpHandler.continueDATA(TcpLmtpHandler.java:73)
at com.zimbra.cs.lmtpserver.LmtpHandler.doDATA(LmtpHandler.java:365)
at com.zimbra.cs.lmtpserver.LmtpHandler.processCommand(LmtpHandler.java:181)
at com.zimbra.cs.lmtpserver.TcpLmtpHandler.processCommand(TcpLmtpHandler.java:66)
at com.zimbra.cs.server.ProtocolHandler.processConnection(ProtocolHandler.java:188)
at com.zimbra.cs.server.ProtocolHandler.run(ProtocolHandler.java:127)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:744)
Caused by: com.zimbra.common.service.ServiceException: system failure: switching open conversation association for item 1461257
ExceptionId:LmtpServer-99969:1450636482209:f2ac11245238e364
Code:service.FAILURE
at com.zimbra.common.service.ServiceException.FAILURE(ServiceException.java:258)
at com.zimbra.cs.db.DbMailItem.changeOpenTargets(DbMailItem.java:1207)
at com.zimbra.cs.mailbox.Threader.changeThreadingTargets(Threader.java:437)
at com.zimbra.cs.mailbox.Mailbox.addMessageInternal(Mailbox.java:5589)


at com.zimbra.cs.mailbox.Mailbox.addMessage(Mailbox.java:5342)
at com.zimbra.cs.mailbox.Mailbox.addMessage(Mailbox.java:5276)
at com.zimbra.cs.mailbox.Mailbox.addMessage(Mailbox.java:5271)
at com.zimbra.cs.filter.IncomingMessageHandler.addMessage(IncomingMessageHandler.java:131)
at com.zimbra.cs.filter.IncomingMessageHandler.implicitKeep(IncomingMessageHandler.java:123)
at com.zimbra.cs.filter.ZimbraMailAdapter.doDefaultFiling(ZimbraMailAdapter.java:344)
at com.zimbra.cs.filter.ZimbraMailAdapter.executeActions(ZimbraMailAdapter.java:219)
... 15 more
Caused by: java.sql.SQLException: Index open_conversation is corrupted


Query being executed when exception was thrown:
UPDATE mboxgroup17.open_conversation SET conv_id = 1466546 WHERE mailbox_id = 17 AND conv_id = 1461257



at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1073)
at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3609)
at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3541)
at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:2002)
at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2163)
at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2624)
at com.mysql.jdbc.PreparedStatement.executeInternal(PreparedStatement.java:2127)
at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:2427)
at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:2345)
at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:2330)
at com.zimbra.cs.db.DebugPreparedStatement.executeUpdate(DebugPreparedStatement.java:177)
at org.apache.commons.dbcp.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:105)
at org.apache.commons.dbcp.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:105)
at com.zimbra.cs.db.DbMailItem.changeOpenTargets(DbMailItem.java:1205)
... 24 more



com.zimbra.common.service.ServiceException: system failure: switching open conversation association for item 1461257
ExceptionId:LmtpServer-99969:1450636482218:f2ac11245238e364
Code:service.FAILURE
at com.zimbra.common.service.ServiceException.FAILURE(ServiceException.java:258)
at com.zimbra.cs.db.DbMailItem.changeOpenTargets(DbMailItem.java:1207)
at com.zimbra.cs.mailbox.Threader.changeThreadingTargets(Threader.java:437)
at com.zimbra.cs.mailbox.Mailbox.addMessageInternal(Mailbox.java:5589)
at com.zimbra.cs.mailbox.Mailbox.addMessage(Mailbox.java:5342)
at com.zimbra.cs.mailbox.Mailbox.addMessage(Mailbox.java:5276)
at com.zimbra.cs.mailbox.Mailbox.addMessage(Mailbox.java:5271)
at com.zimbra.cs.filter.IncomingMessageHandler.addMessage(IncomingMessageHandler.java:131)
at com.zimbra.cs.filter.IncomingMessageHandler.implicitKeep(IncomingMessageHandler.java:123)
at com.zimbra.cs.filter.ZimbraMailAdapter.doDefaultFiling(ZimbraMailAdapter.java:344)
at com.zimbra.cs.filter.RuleManager.applyRulesToIncomingMessage(RuleManager.java:375)
at com.zimbra.cs.filter.RuleManager.applyRulesToIncomingMessage(RuleManager.java:322)
at com.zimbra.cs.lmtpserver.ZimbraLmtpBackend.deliverMessageToLocalMailboxes(ZimbraLmtpBackend.java:612)
at com.zimbra.cs.lmtpserver.ZimbraLmtpBackend.deliver(ZimbraLmtpBackend.java:382)
at com.zimbra.cs.lmtpserver.LmtpHandler.processMessageData(LmtpHandler.java:376)
at com.zimbra.cs.lmtpserver.TcpLmtpHandler.continueDATA(TcpLmtpHandler.java:73)
at com.zimbra.cs.lmtpserver.LmtpHandler.doDATA(LmtpHandler.java:365)
at com.zimbra.cs.lmtpserver.LmtpHandler.processCommand(LmtpHandler.java:181)
at com.zimbra.cs.lmtpserver.TcpLmtpHandler.processCommand(TcpLmtpHandler.java:66)
at com.zimbra.cs.server.ProtocolHandler.processConnection(ProtocolHandler.java:188)
at com.zimbra.cs.server.ProtocolHandler.run(ProtocolHandler.java:127)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:744)
Caused by: java.sql.SQLException: Index open_conversation is corrupted


Query being executed when exception was thrown:
UPDATE mboxgroup17.open_conversation SET conv_id = 1466546 WHERE mailbox_id = 17 AND conv_id = 1461257



at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1073)
at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3609)
at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3541)
at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:2002)
at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2163)
at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2624)
at com.mysql.jdbc.PreparedStatement.executeInternal(PreparedStatement.java:2127)
at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:2427)
at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:2345)
at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:2330)
at com.zimbra.cs.db.DebugPreparedStatement.executeUpdate(DebugPreparedStatement.java:177)
at org.apache.commons.dbcp.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:105)
at org.apache.commons.dbcp.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:105)
at com.zimbra.cs.db.DbMailItem.changeOpenTargets(DbMailItem.java:1205)
... 22 more
2015-12-21 00:04:42,220 INFO [LmtpServer-99987] [name=starg2@star.lk;mid=17;ip=172.17.0.34;] cache - initializing folder and tag caches for mailbox 17
2015-12-21 00:04:42,220 INFO [LmtpServer-99969] [name=starg2@star.lk;mid=17;ip=172.17.0.34;] lmtp - S: 451 4.0.0 Temporary message delivery failure try again (DATA)




Fabio S. Schmidt
Advanced member
Advanced member
Posts: 183
Joined: Fri Apr 25, 2014 12:42 pm

Mysql table error

Postby Fabio S. Schmidt » Mon Dec 21, 2015 11:07 am

Hi Erange,



I would export the mailbox and import it with the reset option to delete all data before importing.

Return to “Administrators”

Who is online

Users browsing this forum: No registered users and 9 guests