2013-12-10 29 views
6

私のデータベース(MySQLの)サーバは/クラッシュ再起動し続け、私が何をすべきかの損失で午前クラッシュし。その後、午前7時30分(+/- 30分)以上の周りにそれが起こるんが、「クラッシュ」サーバーMySQLのInnoDBは

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]# 

と一見ランダムな間隔で再起動:私は私のdbname.org.errファイルに次のように得続けますそれ以外の時はそうです。

どこでも今回の近くに実行中のcronジョブはありません。

助けていただけたら幸いです!

SS

答えて

7

それは

+1

これらは、ここに直面している具体的な問題についての現在入手可能な情報の量に基づいて、すべての正当化は非常に劇的なステップとはありません。 –

+0

ありがとうございました! – brokenspoke

+0

@brokenspokeこのサイトでは、うまくいけば、この回答のチェックマークをクリックして「受け入れられた」(「解決済み」と同等)とマークするのが適切な「editique」です。 :) –

0

その時点からの時間が判明し解決しますあなたのib_logファイルを削除して、configファイルでinnodb_force_recovery = 6を入れて、あなたのMySQLを再起動し、メモリ使用量は、(私がいることを推測しているスパイクうこれはApacheの子プロセスで劇的なスパイクが発生したためです)、これによりメモリが圧迫されます。メモリ不足のキラーは、通常はシステム内で最大のメモリユーザであったため、閉じるためにmysqlを選択します。だから、修正する

は、I

  • はスピンアップされた子プロセスの数を制御するようにApacheを調整され、より多くのメモリ
  • 罰金を得ました。
+1

さらに、 '/ proc/$(pidof mysqld)/ oom_adj'を-17に設定すると、oom-killerはmysqldを強制終了しません。 mysqldよりもApacheをkillするほうが良いでしょう。 https://twindb.com/oom-killer-or-how-to-fail-at-start/ – akuzminsky

+0

ありがとうございます。 –

関連する問題