CAS+Mysql无法启动

安装CVM的服务器在突然断电后，重新开机后Tomcat启动（但是错误信息提示连接数据库失败），但是MySQL无法启动，导致无法登录CAS。mysql的错误日志200714 14:42:47 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead. 200714 14:42:47 [Note] Plugin 'FEDERATED' is disabled. 200714 14:42:47 InnoDB: The InnoDB memory heap is disabled 200714 14:42:47 InnoDB: Mutexes and rw_locks use GCC atomic builtins 200714 14:42:47 InnoDB: Compressed tables use zlib 1.2.3.4 200714 14:42:47 InnoDB: Initializing buffer pool, size = 128.0M 200714 14:42:47 InnoDB: Completed initialization of buffer pool 200714 14:42:47 InnoDB: highest supported file format is Barracuda. InnoDB: Log scan progressed past the checkpoint lsn 16093843641 200714 14:42:47 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 16093848849 InnoDB: Error: trying to access page number 4294965631 in space 0, InnoDB: space name ./ibdata1, InnoDB: which is outside the tablespace bounds. InnoDB: Byte offset 0, len 16384, i/o type 10. InnoDB: If you get this error at mysqld startup, please check that InnoDB: your my.cnf matches the ibdata files that you have in the InnoDB: MySQL server. 200714 14:42:47 InnoDB: Assertion failure in thread 140154509461312 in file fil0fil.c line 4578 InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to ***.***. InnoDB: If you get repeated assertion failures or crashes, even InnoDB: immediately after the mysqld startup, there may be InnoDB: corruption in the InnoDB tablespace. Please refer to InnoDB: ***.***/doc/refman/5.5/en/forcing-innodb-recovery.html InnoDB: about forcing recovery. 06:42:47 UTC - mysqld got signal 6 ; 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.

CAS版本E0306