Results 1 to 5 of 5

Thread: ZCS: mysql.server will NOT start

  1. #1
    jstlouis is offline Intermediate Member
    Join Date
    May 2008
    Posts
    18
    Rep Power
    6

    Default ZCS: mysql.server will NOT start

    Hi All,

    I'm having some major problems with Zimbra, that began this morning!

    I was originally running ZCS 5.0.10, when I started having "mysql.server" problems.
    mailbox Stopped
    mysql.server is not running.
    It seems as if mysql.server keeps coming up, then crashes. One minute it shows OK, the other minute is shows it as failed.

    I restored a backup, and still NO luck. The same thing keeps happing.

    I then upgraded from ZCS 5.0.10 to 5.0.14 this morning, and the same thing keeps happening. Everything seemed to be OK for the last 6 months or so, since my last upgrade.

    One minute it's showing

    mailbox Stopped
    mysql.server is not running.
    The other minute is shows:

    mailbox Running
    And occasionally shows:
    mailbox Stopped
    zmmailboxdctl is not running.
    I'm at a loss here. Any help is very much appreciated!

    Here is some other log information I found! Hope it helps!

    090406 13:00:32 InnoDB: Page checksum 3631515826, prior-to-4.0.14-form checksum 2099044682
    InnoDB: stored checksum 3631515826, prior-to-4.0.14-form stored checksum 3814194543
    InnoDB: Page lsn 0 1669218206, low 4 bytes of lsn at page end 1669225611
    InnoDB: Page number (if stored to page already) 0,
    InnoDB: space id (if created with >= MySQL-4.1.1 and stored already) 270
    InnoDB: Page may be an index page where index id is 0 49676288
    InnoDB: Database page corruption on disk or a failed
    InnoDB: file read of page 0.
    InnoDB: You may have to recover from a backup.
    InnoDB: It is also possible that your operating
    InnoDB: system has corrupted its own file cache
    InnoDB: and rebooting your computer removes the
    InnoDB: error.
    InnoDB: If the corrupt page is an index page
    InnoDB: you can also try to fix the corruption
    InnoDB: by dumping, dropping, and reimporting
    InnoDB: the corrupt table. You can use CHECK
    InnoDB: TABLE to scan your table for corruption.
    InnoDB: TABLE to scan your table for corruption.
    InnoDB: See also InnoDB: MySQL :: MySQL 5.0 Reference Manual :: 13.2.6.1 Forcing InnoDB Recovery
    InnoDB: about forcing recovery.
    InnoDB: Ending processing because of a corrupt database page.
    Number of processes running now: 0
    090406 13:00:32 mysqld restarted
    090406 13:00:32 [Warning] option 'max_join_size': unsigned value 18446744073709551615 adjusted to 4294967295
    090406 13:00:32 [Warning] option 'max_join_size': unsigned value 18446744073709551615 adjusted to 4294967295
    InnoDB: Log scan progressed past the checkpoint lsn 0 1671753863
    090406 13:00:32 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...
    InnoDB: Doing recovery: scanned up to log sequence number 0 1671791744
    090406 13:00:32 InnoDB: Starting an apply batch of log records to the database...
    InnoDB: Progress in percents: 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99

  2. #2
    phoenix is offline Zimbra Consultant & Moderator
    Join Date
    Sep 2005
    Location
    Vannes, France
    Posts
    23,201
    Rep Power
    56

    Default

    Have a look at this thread and see if it helps.
    Regards


    Bill


    Acompli: A new adventure for Co-Founder KevinH.

  3. #3
    jstlouis is offline Intermediate Member
    Join Date
    May 2008
    Posts
    18
    Rep Power
    6

    Default

    I don't know if this is much help or not, however it seems like the mysql.server (mailboxd) process keeps going up and down on it's own.

    I can't seem to figure out what's causing this, let alone how to fix it.

    Again, any help or pointers you may have would be very much appreciated.

    TIA

    Jeff

  4. #4
    jstlouis is offline Intermediate Member
    Join Date
    May 2008
    Posts
    18
    Rep Power
    6

    Default

    OK, that did NOT go well.

    I've now "un-installed zimbra" and re-installed the same version.

    I'm currently extracting a backup (from a couple days ago), we'll see what happens.

    I've also setup a 2nd server, with a fresh install of ZCS 5.0.10, and just waiting on the backup to be extracted.

    I went back a few days for a backup, with hopes that the database was still OK then.

    I got errors in the 2nd stage of the Database repair, and completely killed my existing install!


    I'll the results of these test shortly!


    Thanks for the help!

  5. #5
    jstlouis is offline Intermediate Member
    Join Date
    May 2008
    Posts
    18
    Rep Power
    6

    Default

    Hi All,

    It looks like everything went OK after I restored Friday's backup.

    I haven't seen any database errors yet.

    Is there something I should keep an eye out for? How can I prevent this from happening in the future? Is that even possible?

    Thanks for the help!

    Jeff

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Similar Threads

  1. Errors installing Outlook Connector
    By Tim G in forum Zimbra Connector for Outlook
    Replies: 57
    Last Post: 05-05-2011, 02:27 PM
  2. Trouble Sending mail - All Messages deferred!
    By SiteDiscovery in forum Administrators
    Replies: 7
    Last Post: 09-03-2009, 04:52 AM
  3. Mail is being queued, not delivered!
    By icepick94 in forum Administrators
    Replies: 12
    Last Post: 01-22-2009, 07:03 AM
  4. Error Installing Outlook Connector
    By DanO in forum Zimbra Connector for Outlook
    Replies: 17
    Last Post: 08-28-2007, 09:35 AM
  5. Is it started or not
    By kwelipatton in forum Installation
    Replies: 10
    Last Post: 03-28-2006, 11:11 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
  •