Results 1 to 3 of 3

Thread: mysql.server and zmmailboxctl fail

  1. #1
    Join Date
    Jun 2007
    Location
    Porto Alegre, RS, Brazil
    Posts
    96
    Rep Power
    8

    Default mysql.server and zmmailboxctl fail

    Hi

    After a power outage i lost zimbra functionality and both mysql.server and zmmailboxctl fail to start.

    Im afraid some database got corrupted.

    Output from mailbox.log

    <snip>
    2008-04-11 13:48:00,094 INFO [main] [] system - Setting mysql connector property: maxActive=100
    2008-04-11 13:48:00,094 INFO [main] [] system - Setting mysql connector property: maxActive=100
    2008-04-11 13:48:04,222 FATAL [main] [] system - Config initialization failed
    com.zimbra.common.service.ServiceException: system failure: getting database connection
    Code:service.FAILURE
    at com.zimbra.common.service.ServiceException.FAILURE (ServiceException.java:183)
    at com.zimbra.cs.db.DbPool.getConnection(DbPool.java: 231)
    at com.zimbra.cs.util.Config.init(Config.java:62)
    at com.zimbra.cs.util.Config.initConfig(Config.java:8 9)
    at com.zimbra.cs.util.Config.getString(Config.java:10 1)
    at com.zimbra.cs.db.Versions.checkDBVersion(Versions. java:77)
    at com.zimbra.cs.db.Versions.checkVersions(Versions.j ava:73)
    at com.zimbra.cs.util.Zimbra.startup(Zimbra.java:88)
    at com.zimbra.soap.SoapServlet.init(SoapServlet.java: 114)
    <snip>

    And heres mailserver.err (/opt/zimbra/db/data/)

    <snip>
    080411 13:43:45 mysqld started
    080411 13:43:45 InnoDB: Database was not shut down normally!
    InnoDB: Starting crash recovery.
    InnoDB: Reading tablespace information from the .ibd files...
    InnoDB: Restoring possible half-written data pages from the doublewrite
    InnoDB: buffer...
    080411 13:43:45 InnoDB: Starting log scan based on checkpoint at
    InnoDB: log sequence number 0 235238341.
    InnoDB: Doing recovery: scanned up to log sequence number 0 235240017
    080411 13:43:45 InnoDB: Starting an apply batch of log records to the database...
    InnoDB: Progress in percents: 33 080411 13:43:45 - mysqld got signal 11;
    This could be because you hit a bug. It is also possible that this binary
    or one of the libraries it was linked against is corrupt, improperly built,
    or misconfigured. This error can also be caused by malfunctioning hardware.
    We will try our best to scrape up some info that will hopefully help diagnose
    the problem, but since we have already crashed, something is definitely wrong
    and this may fail.

    key_buffer_size=0
    read_buffer_size=1044480
    max_used_connections=0
    max_connections=110
    threads_connected=0
    It is possible that mysqld could use up to
    key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 224839 K
    bytes of memory
    Hope that's ok; if not, decrease some variables in the equation.
    <snip>

    Already tried upgrade. Didnt work.

    Any help would be GREATLY appreciated.

  2. #2
    Join Date
    Nov 2006
    Location
    UK
    Posts
    8,017
    Rep Power
    24

    Default

    What ZCS version are you running ? Do you have a recent backup ?

    Also, http://www.zimbra.com/forums/announc...r-profile.html please

  3. #3
    Join Date
    Jun 2007
    Location
    Porto Alegre, RS, Brazil
    Posts
    96
    Rep Power
    8

    Default

    Hi

    Thanks for your replay. I apologize for not posting about it, but weve been able to fix the corruption by deleting the ib_log1 and ib_log2 files at /opt/zimbra/db/data. After that the system started flawlessly.

    About my profile, ill take the time to update it. Thanks for the heads up.

    Best regards

Similar Threads

  1. zmmailboxctl status
    By shawnlhood in forum Administrators
    Replies: 1
    Last Post: 10-12-2007, 10:39 AM

Posting Permissions

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