导致mysql崩溃

一个cron作业自动重启我的mysql数据库。 崩溃的原因是什么,或者你能build议如何解决或监视。

我真的很感激你的意见。

120715 14:38:58 mysqld started 120715 14:38:58 InnoDB: Started; log sequence number 0 411137570 120715 14:38:58 [Note] /usr/libexec/mysqld: ready for connections. Version: '5.0.95' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution 120715 15:14:21 [Note] /usr/libexec/mysqld: Normal shutdown 120715 15:14:23 InnoDB: Starting shutdown... 120715 15:14:25 InnoDB: Shutdown completed; log sequence number 0 411166467 120715 15:14:25 [Note] /usr/libexec/mysqld: Shutdown complete 120715 08:14:25 mysqld ended 120715 08:14:26 mysqld started 120715 8:14:26 InnoDB: Started; log sequence number 0 411166467 120715 8:14:26 [Note] /usr/libexec/mysqld: ready for connections. Version: '5.0.95' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution 121212 09:15:32 mysqld started InnoDB: The log sequence number in ibdata files does not match InnoDB: the log sequence number in the ib_logfiles! 121212 9:15:58 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... 121212 9:17:28 InnoDB: Started; log sequence number 0 554145193 121212 9:17:57 [Note] /usr/libexec/mysqld: ready for connections. Version: '5.0.95' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution 

根据该日志,120715,121212实际上是服务器date。

在2012年12月12日09:15:32服务器时间

 121212 09:15:32 mysqld started 

Mysql启动并自动恢复。

我怀疑你有一个服务器崩溃。 检查你的盒子服务器日志,甚至给Rackspace一个电话或电子邮件确认服务器重新启动发生在2012年12月12日上午9点左右,服务器时间。

如果你想要上下提供各种服务的日常报告,常见的select如下

  1. logwatch通常configuration为每日报告在系统上运行的服务。
  2. Nagios + nrpe更多地涉及到configuration,但可以提供接近服务/守护程序中断的即时警报。