OK, after digging around, it looks like tomcat is quitting when it attempts to read or write from the mysql database mboxgroup5/mail_item (the error message from MySQL InnoDB is below). I'm guessing that this table may have been corrupted during the power outage. Any ideas as to how I would go about restoring this table?
Code:
070622 11:52:03 InnoDB: Started; log sequence number 0 92293929
070622 11:52:03 [Note] /opt/zimbra/mysql/libexec/mysqld: ready for connections.
Version: '5.0.33-log' socket: '/opt/zimbra/db/mysql.sock' port: 7306 Source distribution
InnoDB: Database page corruption on disk or a failed
InnoDB: file read of page 55.
InnoDB: You may have to recover from a backup.
070622 11:52:18 InnoDB: Page dump in ascii and hex (16384 bytes):
len 16384; hex 6b679bfb00000037ffffffff0000035400000000057fc48745bf000000 [snip]
070622 11:52:18 InnoDB: Page checksum 1801952251, prior-to-4.0.14-form checksum 2219588811
InnoDB: stored checksum 1801952251, prior-to-4.0.14-form stored checksum 44941139
InnoDB: Page lsn 0 92259463, low 4 bytes of lsn at page end 92292521
InnoDB: Page number (if stored to page already) 55,
InnoDB: space id (if created with >= MySQL-4.1.1 and stored already) 36
InnoDB: Page may be an index page where index id is 0 130
InnoDB: (index i_folder_id_date of table mboxgroup5/mail_item)
InnoDB: Database page corruption on disk or a failed
InnoDB: file read of page 55.
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: See also InnoDB: http://dev.mysql.com/doc/refman/5.0/en/forcing-recovery.html
InnoDB: about forcing recovery.
InnoDB: Ending processing because of a corrupt database page.
Number of processes running now: 0
070622 11:52:18 mysqld restarted
070622 11:52:18 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...
070622 11:52:18 InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 0 92293939.
InnoDB: Doing recovery: scanned up to log sequence number 0 92293949
070622 11:52:19 InnoDB: Started; log sequence number 0 92293949
070622 11:52:19 [Note] /opt/zimbra/mysql/libexec/mysqld: ready for connections.
Version: '5.0.33-log' socket: '/opt/zimbra/db/mysql.sock' port: 7306 Source distribution