Hi,

I'm running 5.0.2 Open Source edition on Debian. Since last night, my mailbox keeps dying, and looking from the logs, it's always due to some MySQL error, pertaining to one mailbox.

How do I find out which account points to which mailbox number, and also, how do I fix something like this?

Code:
2008-03-03 08:47:54,182 INFO  [ImapServer-21] [] imap - [192.168.50.90] connected
2008-03-03 08:48:02,246 INFO  [ImapServer-21] [ip=192.168.50.90;] MailboxIndex - Initialized Index for mailbox 18 directory: LuceneIndex at org.apa
che.lucene.store.FSDirectory@/opt/zimbra/index/0/18/index/0 Analyzer=com.zimbra.cs.index.ZimbraAnalyzer@21447f
2008-03-03 08:48:02,246 INFO  [ImapServer-21] [ip=192.168.50.90;] cache - Initializing folder and tag caches for mailbox 18
2008-03-03 08:48:02,548 FATAL [ImapServer-21] [ip=192.168.50.90;] mailbox - Unable to commit database transaction.  Forcing server to abort.
com.zimbra.common.service.ServiceException: system failure: committing database transaction
Code:service.FAILURE
        at com.zimbra.common.service.ServiceException.FAILURE(ServiceException.java:183)
        at com.zimbra.cs.db.DbPool$Connection.commit(DbPool.java:144)
        at com.zimbra.cs.mailbox.Mailbox.endTransaction(Mailbox.java:5734)
        at com.zimbra.cs.mailbox.Mailbox.getConfig(Mailbox.java:1125)
        at com.zimbra.cs.mailbox.Mailbox.finishInitialization(Mailbox.java:460)
        at com.zimbra.cs.mailbox.MailboxManager.getMailboxById(MailboxManager.java:406)
        at com.zimbra.cs.mailbox.MailboxManager.getMailboxByAccountId(MailboxManager.java:265)
        at com.zimbra.cs.mailbox.MailboxManager.getMailboxByAccountId(MailboxManager.java:218)
        at com.zimbra.cs.imap.ImapCredentials.getMailbox(ImapCredentials.java:99)
        at com.zimbra.cs.imap.ImapHandler.startSession(ImapHandler.java:1054)
        at com.zimbra.cs.imap.ImapHandler.authenticate(ImapHandler.java:1019)
        at com.zimbra.cs.imap.ImapAuthenticatorUser.authenticate(ImapAuthenticatorUser.java:62)
        at com.zimbra.cs.security.sasl.Authenticator.authenticate(Authenticator.java:104)
        at com.zimbra.cs.security.sasl.PlainAuthenticator.handle(PlainAuthenticator.java:63)
        at com.zimbra.cs.imap.ImapHandler.continueAuthentication(ImapHandler.java:204)
        at com.zimbra.cs.imap.ImapHandler.continueAuthentication(ImapHandler.java:195)
        at com.zimbra.cs.imap.TcpImapHandler.processCommand(TcpImapHandler.java:149)
        at com.zimbra.cs.tcpserver.ProtocolHandler.processConnection(ProtocolHandler.java:160)
        at com.zimbra.cs.tcpserver.ProtocolHandler.run(ProtocolHandler.java:128)
        at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(Unknown Source)
        at java.lang.Thread.run(Thread.java:619)
Caused by: com.mysql.jdbc.exceptions.MySQLNonTransientConnectionException: Communications link failure during commit(). Transaction resolution unkn
own.
        at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:888)
        at com.mysql.jdbc.Connection.commit(Connection.java:2246)
        at org.apache.commons.dbcp.DelegatingConnection.commit(DelegatingConnection.java:248)
        at org.apache.commons.dbcp.PoolingDataSource$PoolGuardConnectionWrapper.commit(PoolingDataSource.java:244)
        at com.zimbra.cs.db.DbPool$Connection.commit(DbPool.java:142)
        ... 19 more