Mysql innoDB continua a bloccarsi

Il mio database (mysql) server continua a bloccarsi/riavviarsi e sono in perdita di cosa fare. Continuo a ricevere il seguente nel mio file dbname.org.err:Mysql innoDB continua a bloccarsi

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

Il server 'si blocca' e si riavvia a intervalli apparentemente casuali, anche se questo dovesse succedere intorno alle 7.30 (+/- 30 minuti) più di altre volte sembra.

Non ci sono cron jobs in esecuzione da nessuna parte vicino a quest'ora.

Qualsiasi aiuto sarebbe apprezzato!

fonte

2013-12-10 brokenspoke

rilasciare i file ib_log e mettere innodb_force_recovery = 6 nel file di configurazione e riavviare il mysql si risolverà

fonte

2013-12-10 04:24:16 user3048109

Questi sono passi molto drammatiche e non giustificata a tutti in base alla quantità di informazioni attualmente disponibili sul problema specifico che viene incontrato qui. –

Ha lavorato grazie! – brokenspoke

@brokenspoke Su questo sito, se ha funzionato, è corretto "editique" cliccare sul segno di spunta con questa risposta per contrassegnarlo come "accettato" (equivalente a "risolto"). :) –

scopre che di volta in volta, l'utilizzo della memoria sarebbe spike (sto cercando di indovinare che questo era a causa di un picco drammatico nei processi figli dell'apache) e questo avrebbe causato una pressione della memoria. Il killer out-of-memory avrebbe scelto mysql per chiudere, perché era (di solito) il più grande utente di memoria nel sistema.

Quindi, per fissare, ho

avuto più memoria
perfezionato Apache per controllare il numero di processi figli che erano filate in su.

fonte

2015-09-26 09:34:16

inoltre puoi impostare '/ proc/$ (pidof mysqld)/oom_adj' su -17 in modo che oom-killer non uccida mysqld. È meglio uccidere l'apache di mysqld. Vedi https://twindb.com/oom-killer-or-how-to-fail-at-start/ – akuzminsky

grazie mille! –

Mysql innoDB continua a bloccarsi

risposta

Problemi correlati