Results 1 to 2 of 2

Thread: Server down: Can't get to zimbra via browser/IMAP

  1. #1
    Join Date
    Apr 2006
    Ridgefield, CT
    Rep Power

    Angry Server down: Can't get to zimbra via browser/IMAP

    Nice, stable environment has been running without incident for weeks.

    Today, about an hour ago, the log shows the following:

    2006-12-11 12:20:31,203 INFO [http-8080-Processor100] [ip=;;] cache - Initializing folder and tag caches for mailbox 9
    2006-12-11 12:20:31,326 FATAL [http-8080-Processor100] [ip=;;] mailbox - Unable to commit database transaction. Forcing server to abort.
    com.zimbra.cs.service.ServiceException: system failure: committing database transaction
    at com.zimbra.cs.service.ServiceException.FAILURE(Ser
    at com.zimbra.cs.db.DbPool$Connection.commit(DbPool.j ava:162)
    at com.zimbra.cs.mailbox.Mailbox.endTransaction(Mailb
    at com.zimbra.cs.mailbox.Mailbox.getConfig(Mailbox.ja va:847)
    at a:109)
    at com.zimbra.cs.session.Session.<init>( 77)
    at com.zimbra.cs.session.SoapSession.<init>(SoapSessi
    at com.zimbra.cs.session.SessionCache.getNewSession(S
    at com.zimbra.soap.ZimbraSoapContext.getSession(Zimbr
    at com.zimbra.soap.DocumentHandler.getSession(Documen
    at com.zimbra.soap.DocumentHandler.getSession(Documen
    at com.zimbra.soap.SoapEngine.dispatchRequest(SoapEng
    at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.jav a:162)
    at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.jav a:84)
    at com.zimbra.soap.SoapServlet.doPost(SoapServlet.jav a:223)
    at javax.servlet.http.HttpServlet.service(HttpServlet .java:709)
    at com.zimbra.cs.servlet.ZimbraServlet.service(Zimbra
    at javax.servlet.http.HttpServlet.service(HttpServlet .java:802)
    at ternalDoFilter(
    at Filter(
    at org.apache.catalina.core.StandardWrapperValve.invo ke(
    at org.apache.catalina.core.StandardContextValve.invo ke(
    at org.apache.catalina.core.StandardWrapperValve.invo ke(
    at org.apache.catalina.core.StandardContextValve.invo ke(
    at org.apache.catalina.core.StandardHostValve.invoke(
    at org.apache.catalina.valves.ErrorReportValve.invoke (
    at org.apache.catalina.core.StandardEngineValve.invok e(
    at org.apache.catalina.valves.AccessLogValve.invoke(A
    at org.apache.catalina.connector.CoyoteAdapter.servic e(
    at org.apache.coyote.http11.Http11Processor.process(H
    at org.apache.coyote.http11.Http11BaseProtocol$Http11 ConnectionHandler.processConnection(Http11BaseProt
    at Socket(
    at ead.runIt(
    at org.apache.tomcat.util.threads.ThreadPool$ControlR
    Caused by: java.sql.SQLException: Communications link failure during commit(). Transaction resolution unknown.
    at com.mysql.jdbc.Connection.commit( 169)
    at org.apache.commons.dbcp.DelegatingConnection.commi t(
    at com.zimbra.cs.db.DbPool$Connection.commit(DbPool.j ava:160)
    ... 31 more
    2006-12-11 12:20:32,345 INFO [Thread-264] [] StatsImageServlet - Servlet StatsImageServlet shutting down
    2006-12-11 12:20:32,346 INFO [Thread-264] [] soap - Servlet AdminServlet shutting down
    2006-12-11 12:20:32,346 INFO [Thread-264] [] TcpServer/7025 - LmtpServer initiating shutdown
    2006-12-11 12:20:32,348 INFO [LmtpServer] [] TcpServer/7025 - finished accept loop

    I can't get to zimbra via any browser interface...neither as user or admin.
    Loading stops at the Zimbra splash screen (browser claims 'done')
    IMAP functionality is also down.
    zmcontrol status shows all services running happily



    It appears that when I try to access this particular mailbox, it crashes the server.

    If I restart zimbra, clear all cookies from the machine trying to access the (fscked) mailbox, and login to a different mailbox, all is long as I don't try to access this one mailbox.

    As long as I continue to stay away from this mailbox, all seems fine. If I access it, the server falls down.

    Mailbox is large (~200MB), but not active (no mail gets delivered to's archive data only).

    Anyone have any ideas on how to 'reindex' the mailbox to make this mailbox usable again?

    Problem seems related to an earlier challenge I had here:
    Last edited by mcevoys; 12-11-2006 at 12:28 PM.

  2. #2
    Join Date
    Aug 2005
    Rep Power

    Default Filesystem corruption

    What you're seeing is that MySQL is throwing an exception every time we try to commit a change to that mailbox. When this happens, the Zimbra server has no idea whether the change actually got applied to the database, so it halts rather than risk going forward with an incorrect view of the mailbox (which could potentially snowball into really bad inconsistencies).

    This seems very related to the error you were seeing earlier, and I continue to believe that you were having some serious filesystem weirdness that didn't get completely fixed.
    Bugzilla - Wiki - Downloads - Before posting... Search!

Similar Threads

  1. QUE Failure
    By tbullock in forum Administrators
    Replies: 31
    Last Post: 07-30-2008, 12:17 PM
  2. Replies: 7
    Last Post: 01-24-2007, 10:03 PM
  3. Getting problems in FC4 while instalation
    By kitty_bhoo in forum Installation
    Replies: 13
    Last Post: 09-12-2006, 10:34 PM
  4. Services stopped working
    By lilwong in forum Administrators
    Replies: 4
    Last Post: 08-15-2006, 09:19 AM
  5. FC3 Install and no zimbra ?
    By aws in forum Installation
    Replies: 10
    Last Post: 10-09-2005, 04:19 PM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts