Mysql的InnoDB的不断崩溃

Question

我的数据库（MySQL的）服务器经常当机/重启和我在做什么损失。我不断收到在我dbname.org.err文件中的以下内容：

131205 18:49:05 mysqld_safe mysqld from pid file /var/lib/mysql/les.lesplan.org.pid ended 
131205 18:50:12 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql 
131205 18:50:12 [Note] Plugin 'FEDERATED' is disabled. 
131205 18:50:12 InnoDB: The InnoDB memory heap is disabled 
131205 18:50:12 InnoDB: Mutexes and rw_locks use GCC atomic builtins 
131205 18:50:12 InnoDB: Compressed tables use zlib 1.2.3 
131205 18:50:12 InnoDB: Using Linux native AIO 
131205 18:50:12 InnoDB: Initializing buffer pool, size = 128.0M 
131205 18:50:12 InnoDB: Completed initialization of buffer pool 
131205 18:50:12 InnoDB: highest supported file format is Barracuda. 
131205 18:50:12 InnoDB: Waiting for the background threads to start 
131205 18:50:13 InnoDB: 5.5.32 started; log sequence number 94296300 
131205 18:50:13 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306 
131205 18:50:13 [Note] - '0.0.0.0' resolves to '0.0.0.0'; 
131205 18:50:13 [Note] Server socket created on IP: '0.0.0.0'. 
131205 18:50:14 [Note] Event Scheduler: Loaded 0 events 
131205 18:50:14 [Note] /usr/sbin/mysqld: ready for connections. 
Version: '5.5.32-cll' socket: '/var/lib/mysql/mysql.sock' port: 3306 MySQL Community Server (GPL) 
131206 07:32:53 mysqld_safe Number of processes running now: 0 
131206 07:32:53 mysqld_safe mysqld restarted 
131206 7:32:54 [Note] Plugin 'FEDERATED' is disabled. 
131206 7:32:54 InnoDB: The InnoDB memory heap is disabled 
131206 7:32:54 InnoDB: Mutexes and rw_locks use GCC atomic builtins 
131206 7:32:54 InnoDB: Compressed tables use zlib 1.2.3 
131206 7:32:54 InnoDB: Using Linux native AIO 
131206 7:32:54 InnoDB: Initializing buffer pool, size = 128.0M 
131206 7:32:54 InnoDB: Completed initialization of buffer pool 
131206 7:32:54 InnoDB: highest supported file format is Barracuda. 
InnoDB: The log sequence number in ibdata files does not match 
InnoDB: the log sequence number in the ib_logfiles! 
131206 7:32:54 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... 
131206 7:32:54 InnoDB: Waiting for the background threads to start 
131206 7:32:55 InnoDB: 5.5.32 started; log sequence number 94790638 
131206 7:32:55 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306 
131206 7:32:55 [Note] - '0.0.0.0' resolves to '0.0.0.0'; 
131206 7:32:55 [Note] Server socket created on IP: '0.0.0.0'. 
131206 7:32:55 [Note] Event Scheduler: Loaded 0 events 
131206 7:32:55 [Note] /usr/sbin/mysqld: ready for connections. 
Version: '5.5.32-cll' socket: '/var/lib/mysql/mysql.sock' port: 3306 MySQL Community Server (GPL) 
131206 07:33:07 mysqld_safe Number of processes running now: 0 
131206 07:33:07 mysqld_safe mysqld restarted 
131206 7:33:07 [Note] Plugin 'FEDERATED' is disabled. 
131206 7:33:07 InnoDB: The InnoDB memory heap is disabled 
131206 7:33:07 InnoDB: Mutexes and rw_locks use GCC atomic builtins 
131206 7:33:07 InnoDB: Compressed tables use zlib 1.2.3 
131206 7:33:07 InnoDB: Using Linux native AIO 
131206 7:33:07 InnoDB: Initializing buffer pool, size = 128.0M 
131206 7:33:07 InnoDB: Completed initialization of buffer pool 
131206 7:33:07 InnoDB: highest supported file format is Barracuda. 
InnoDB: The log sequence number in ibdata files does not match 
InnoDB: the log sequence number in the ib_logfiles! 
131206 7:33:07 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... 
131206 7:33:08 InnoDB: Waiting for the background threads to start 
131206 7:33:09 InnoDB: 5.5.32 started; log sequence number 94790648 
131206 7:33:09 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306 
131206 7:33:09 [Note] - '0.0.0.0' resolves to '0.0.0.0'; 
131206 7:33:09 [Note] Server socket created on IP: '0.0.0.0'. 
131206 7:33:09 [Note] Event Scheduler: Loaded 0 events 
131206 7:33:09 [Note] /usr/sbin/mysqld: ready for connections. 
Version: '5.5.32-cll' socket: '/var/lib/mysql/mysql.sock' port: 3306 MySQL Community Server (GPL) 
131206 07:38:38 mysqld_safe Number of processes running now: 0 
131206 07:38:38 mysqld_safe mysqld restarted 
131206 7:38:38 [Note] Plugin 'FEDERATED' is disabled. 
131206 7:38:38 InnoDB: The InnoDB memory heap is disabled 
131206 7:38:38 InnoDB: Mutexes and rw_locks use GCC atomic builtins 
131206 7:38:38 InnoDB: Compressed tables use zlib 1.2.3 
131206 7:38:38 InnoDB: Using Linux native AIO 
131206 7:38:38 InnoDB: Initializing buffer pool, size = 128.0M 
131206 7:38:38 InnoDB: Completed initialization of buffer pool 
131206 7:38:38 InnoDB: highest supported file format is Barracuda. 
InnoDB: The log sequence number in ibdata files does not match 
InnoDB: the log sequence number in the ib_logfiles! 
131206 7:38:38 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... 
131206 7:38:38 InnoDB: Waiting for the background threads to start 
131206 7:38:39 InnoDB: 5.5.32 started; log sequence number 94790674 
131206 7:38:39 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306 
131206 7:38:39 [Note] - '0.0.0.0' resolves to '0.0.0.0'; 
131206 7:38:39 [Note] Server socket created on IP: '0.0.0.0'. 
131206 7:38:39 [Note] Event Scheduler: Loaded 0 events 
131206 7:38:39 [Note] /usr/sbin/mysqld: ready for connections. 
Version: '5.5.32-cll' socket: '/var/lib/mysql/mysql.sock' port: 3306 MySQL Community Server (GPL) 
[email protected] [/var/lib/mysql]# 

服务器“崩溃”，并在看似随机时间间隔重启虽然它上午7:30左右发生（+/- 30分钟）以上，然后其他时间似乎。

有接近这个时间，任何地点没有运行cron作业。

任何帮助，将不胜感激！

SS

Answer 1

放下你的ib_log文件，并把innodb_force_recovery = 6的配置文件，然后重新启动你的mysql就解决

Answer 2

原来，不时，内存使用量就会猛增（我猜这是因为apache子进程中的戏剧性高峰），这会造成内存压力。内存不足的杀手会选择关闭mysql，因为它通常是系统中最大的内存用户。

所以解决，我

• 得到了更多的内存
• 微调阿帕奇来控制下旋转起来的子进程的数目。