MySQL的innoDB不断崩溃 [英] Mysql innoDB keeps crashing

查看：161
本文介绍了MySQL的innoDB不断崩溃的处理方法，对大家解决问题具有一定的参考价值，需要的朋友们下面随着小编来一起学习吧！

问题描述

我的数据库(mysql)服务器不断崩溃/重新启动，我不知所措.我的dbname.org.err文件中不断显示以下内容:

My database (mysql) server keeps crashing / restarting and I am at a loss of what to do. I keep getting the following in my dbname.org.err file:

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 am(+/- 30分钟).

The server 'crashes' and restarts at seemingly random intervals although it does happen around 7:30 am (+/- 30 minutes) more then other times it seems.

这次附近的任何地方都没有正在运行的cron作业.

There are no cron jobs running anywhere near this time.

任何帮助将不胜感激！

ss

推荐答案

将ib_log文件拖放到配置文件中，然后将innodb_force_recovery = 6放入配置文件中，然后重新启动mysql，它将解决

Drop your ib_log files and Put innodb_force_recovery=6 in config file and restart your mysql it will resolve

这篇关于MySQL的innoDB不断崩溃的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！

查看全文
相关文章
数据库最新文章
热门教程
热门工具
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆