mysql每个几分钟就自动重启，下面是报错信息：
071227 22:23:18mysqld restarted
071227 22:23:21InnoDB: Database was not shut down normally.
InnoDB: Starting recovery from log files...
InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 0 1269374539
InnoDB: Doing recovery: scanned up to log sequence number 0 1269374539
071227 22:23:21InnoDB: Flushing modified pages from the buffer pool...
071227 22:23:21InnoDB: Started
/usr/local/mysql/libexec/mysqld: ready for connections.
Version: '4.0.14'socket: '/tmp/mysql.sock'port: 3306
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=134217728
read_buffer_size=4190208
max_used_connections=14
max_connections=400
threads_connected=8
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 3406268 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
从你所给出的错误看,是InnoDB的数据库已经损坏了,然后InnoDB自动去修复,但是一直没有修复好.....所以一直重复这个动作...
This error can also be caused by malfunctioning hardware.
这句说,可能是你硬件存在问题....
这样的问题我还没有见过.........你检查下硬盘..以及使用 check table 命令去检查下表是否已经损坏..
先把innodb_flush_shutdown =1 .然后重新启动mysqld,再看看了....启动的时候不要带修复的命令
