Mysql innoDB不断崩溃

时间:2013-12-10 01:59:47

标签: mysql innodb

我的数据库(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)
root@les [/var/lib/mysql]#

服务器“崩溃”并以看似随机的间隔重新启动,尽管它确实发生在早上7:30左右(+/- 30分钟),而不是其他时间。

在这个时间附近没有任何cron作业可以运行。

任何帮助将不胜感激!

SS

2 个答案:

答案 0 :(得分:7)

删除你的ib_log文件并在配置文件中输入innodb_force_recovery = 6并重新启动它将解析的mysql

答案 1 :(得分:0)

事实证明,内存使用率会不时出现(我猜这是因为apache子进程出现了大幅增长),这会导致内存压力。内存不足的杀手会选择关闭mysql,因为它(通常)是系统中最大的内存用户。

所以要解决,我

  • 得到更多记忆
  • 微调Apache以控制旋转的子进程数。