ZCS: mysql.server will NOT start

[jstlouis]

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

[phoenix]

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

[jstlouis]

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

[jstlouis]

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!

[jstlouis]

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