Mysql innoDB crash

Ma base de données (mysql) serveur crash /redémarrage et je suis à une perte de quoi faire. Je reçois le suivant dans mon dbname.org.tre fichier:

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

Le serveur "accidents" et redémarre en apparence aléatoire intervalles, bien qu'il ne se passe autour de 7:30 am (+/- 30 minutes) pour en savoir plus, puis d'autres fois, il me semble.

Il n'y a pas des tâches cron exécute n'importe où près de ce temps.

Toute aide serait appréciée!

ss

  • Dans un de vos commentaires ci-dessous, vous dit que vous "fini la suppression et la restauration à partir d'une ancienne sauvegarde". Fait que l'arrêt de votre serveur mysql à partir de la plante de nouveau? Avez-vous une idée de ce qui pourrait avoir été à l'origine de la plante?
  • Peut-être liées, systemd pas arrêter MariaDB correctement? ce sont les raisons pour lesquelles la question devrait être posée sur le bon site. Cette réponse ne dispose pas d'une analyse du potentiel de la racine les causes du problème. Tout ce que vous obtenez sont les anecdotes qu'un développeur a trouvé qui fonctionne pour eux.
InformationsquelleAutor brokenspoke | 2013-12-10