MySQL服务器崩溃

时间:2014-05-11 19:58:21

标签: mysql linux

我遇到常规的MySQL服务器崩溃(在Linux上)。运行后

sudo /etc/init.d/mysql restart

问题消失了,但是暂时的。这可能是一天或几天,但无论如何都会发生崩溃。这是崩溃之后和守护程序重启之前的错误日志文件的摘录。我不确定它是否反映了任何有用的信息。

140511  0:11:06 [Note] Plugin 'FEDERATED' is disabled.
140511  0:11:37  InnoDB: Initializing buffer pool, size = 8.0M
140511  0:11:38  InnoDB: Completed initialization of buffer pool
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
140511  0:11:52  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...
140511  0:14:26  InnoDB: Started; log sequence number 1 3968482280
140511  0:16:46 [Note] Event Scheduler: Loaded 0 events
140511  0:16:46 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.1.69-0ubuntu0.11.10.1'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  (Ubuntu)
140511  0:22:00 [Note] Plugin 'FEDERATED' is disabled.
140511  0:22:46  InnoDB: Initializing buffer pool, size = 8.0M
140511  0:22:46  InnoDB: Completed initialization of buffer pool
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
140511  0:22:52  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...
140511  0:24:41  InnoDB: Started; log sequence number 1 3968482290
140511  0:26:55 [Note] Event Scheduler: Loaded 0 events
140511  0:26:56 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.1.69-0ubuntu0.11.10.1'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  (Ubuntu)

重新安装服务器后问题没有消失。

或许现在是时候在干净的OS安装上安装数据库了,并将我的所有数据库都带到那里,但在这个耗时的解决方案之前,我想尝试一些不那么简单的解决方案,如果有的话任何

0 个答案:

没有答案