OVH Community, votre nouvel espace communautaire.

Plantage subit de mysql : Impossible de le redémarrer


captainadmin
12/04/2015, 14h48
Hello

En effet ya pas tellement mieux à faire.
Avant pense à réparer le disque de ton kimsufi

Bon courage

Nico
12/04/2015, 14h30
Non cela devrait être bon.
En fait chaque nuit, je lance un script qui fait un dump des bases Mysql et une archive contenant les fichiers "web" et qui les envoie immédiatement par ftp sur le "Backup Storage" fourni par OVH sur lequel je conserve les versions des 7 derniers jours.

janus57
12/04/2015, 13h51
Bonjour,

backup FTP ou dump MySQL ?

Car bon faire une copie des fichiers BDD quand MySQL tourne c'est pas du backup mais du suicide.

En tout cas là visiblement l’espace HDD touché par les erreurs et pile poil sur MySQL vu qu'il arrive pas à récupérer les tables InnoDB.

Cordialement, janus57

Nico
12/04/2015, 13h19
Merci de ta réponse, c'est bien ce que je craignais...
Pas de raid (serveur low cost kimsufi...) mais un backup ftp assez récent qui va permettre de limiter les pertes.

Kioob
12/04/2015, 12h59
Bonjour,

malheureusement, comme indiqué dans tes logs, ton disque sda est visiblement mort. N'as-tu pas de RAID ? Ni de backup ?

Nico
12/04/2015, 12h40
Bonjour,

Alors que je n'avais effectué aucun changement de configuration depuis plusieurs mois, Mysql a planté. Impossible de le redémarrer. J'ai rebooté le serveur au cas où. Cela n'a rien changé.

Les logs ci-dessous après un "/etc/init.d/mysql start" montrent une quantité de message que je ne sais pas interpréter... Problème de disque ? Données corrompues ?
Quelqu'un saurait-il décrypter ces logs et me conseiller une démarche pour rétablir la situation ?
(Je suis novice en gestion de serveur : la configuration de base quand tout va bien je m'en sors, mais quand le problème est un peu plus spécifique... je suis très vite limité !)

Merci.

Code:
Apr 12 13:17:50 monserveur mysqld_safe: Starting mysqld daemon with databases from /var/lib/mysql
Apr 12 13:17:50 monserveur mysqld: 150412 13:17:50 [Note] Plugin 'FEDERATED' is disabled.
Apr 12 13:17:50 monserveur mysqld: 150412 13:17:50  InnoDB: Initializing buffer pool, size = 8.0M
Apr 12 13:17:50 monserveur mysqld: 150412 13:17:50  InnoDB: Completed initialization of buffer pool
Apr 12 13:17:50 monserveur mysqld: InnoDB: Log scan progressed past the checkpoint lsn 0 297616925
Apr 12 13:17:50 monserveur mysqld: 150412 13:17:50  InnoDB: Database was not shut down normally!
Apr 12 13:17:50 monserveur mysqld: InnoDB: Starting crash recovery.
Apr 12 13:17:50 monserveur mysqld: InnoDB: Reading tablespace information from the .ibd files...
Apr 12 13:17:50 monserveur mysqld: InnoDB: Restoring possible half-written data pages from the doublewrite
Apr 12 13:17:50 monserveur mysqld: InnoDB: buffer...
Apr 12 13:17:51 monserveur kernel: ata1.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0
Apr 12 13:17:51 monserveur kernel: ata1.00: irq_stat 0x40000008
Apr 12 13:17:51 monserveur kernel: ata1.00: failed command: READ FPDMA QUEUED
Apr 12 13:17:51 monserveur kernel: ata1.00: cmd 60/00:00:31:a9:cc/02:00:9f:00:00/40 tag 0 ncq 262144 in
Apr 12 13:17:51 monserveur kernel:         res 41/40:00:91:a9:cc/00:02:9f:00:00/00 Emask 0x409 (media error) 
Apr 12 13:17:51 monserveur kernel: ata1.00: status: { DRDY ERR }
Apr 12 13:17:51 monserveur kernel: ata1.00: error: { UNC }
Apr 12 13:17:51 monserveur kernel: ata1.00: configured for UDMA/133
Apr 12 13:17:51 monserveur kernel: ata1: EH complete
Apr 12 13:17:51 monserveur kernel: ata1.00: exception Emask 0x0 SAct 0x7f SErr 0x0 action 0x0
Apr 12 13:17:51 monserveur kernel: ata1.00: irq_stat 0x40000008
Apr 12 13:17:51 monserveur kernel: ata1.00: failed command: READ FPDMA QUEUED
Apr 12 13:17:51 monserveur kernel: ata1.00: cmd 60/00:00:31:a9:cc/02:00:9f:00:00/40 tag 0 ncq 262144 in
Apr 12 13:17:51 monserveur kernel:         res 41/40:00:91:a9:cc/00:02:9f:00:00/00 Emask 0x409 (media error) 
Apr 12 13:17:51 monserveur kernel: ata1.00: status: { DRDY ERR }
Apr 12 13:17:51 monserveur kernel: ata1.00: error: { UNC }
Apr 12 13:17:51 monserveur kernel: ata1.00: configured for UDMA/133
Apr 12 13:17:51 monserveur kernel: ata1: EH complete
Apr 12 13:17:51 monserveur kernel: ata1.00: exception Emask 0x0 SAct 0x41 SErr 0x0 action 0x0
Apr 12 13:17:51 monserveur kernel: ata1.00: irq_stat 0x40000008
Apr 12 13:17:51 monserveur kernel: ata1.00: failed command: READ FPDMA QUEUED
Apr 12 13:17:51 monserveur kernel: ata1.00: cmd 60/00:30:31:a9:cc/02:00:9f:00:00/40 tag 6 ncq 262144 in
Apr 12 13:17:51 monserveur kernel:         res 41/40:00:91:a9:cc/00:02:9f:00:00/00 Emask 0x409 (media error) 
Apr 12 13:17:51 monserveur kernel: ata1.00: status: { DRDY ERR }
Apr 12 13:17:51 monserveur kernel: ata1.00: error: { UNC }
Apr 12 13:17:51 monserveur kernel: ata1.00: configured for UDMA/133
Apr 12 13:17:51 monserveur kernel: ata1: EH complete
Apr 12 13:17:51 monserveur kernel: ata1.00: exception Emask 0x0 SAct 0x7 SErr 0x0 action 0x0
Apr 12 13:17:51 monserveur kernel: ata1.00: irq_stat 0x40000008
Apr 12 13:17:51 monserveur kernel: ata1.00: failed command: READ FPDMA QUEUED
Apr 12 13:17:51 monserveur kernel: ata1.00: cmd 60/00:00:31:a9:cc/02:00:9f:00:00/40 tag 0 ncq 262144 in
Apr 12 13:17:51 monserveur kernel:         res 41/40:00:91:a9:cc/00:02:9f:00:00/00 Emask 0x409 (media error) 
Apr 12 13:17:51 monserveur kernel: ata1.00: status: { DRDY ERR }
Apr 12 13:17:51 monserveur kernel: ata1.00: error: { UNC }
Apr 12 13:17:51 monserveur kernel: ata1.00: configured for UDMA/133
Apr 12 13:17:51 monserveur kernel: ata1: EH complete
Apr 12 13:17:52 monserveur kernel: ata1.00: exception Emask 0x0 SAct 0x7 SErr 0x0 action 0x0
Apr 12 13:17:52 monserveur kernel: ata1.00: irq_stat 0x40000008
Apr 12 13:17:52 monserveur kernel: ata1.00: failed command: READ FPDMA QUEUED
Apr 12 13:17:52 monserveur kernel: ata1.00: cmd 60/00:10:31:a9:cc/02:00:9f:00:00/40 tag 2 ncq 262144 in
Apr 12 13:17:52 monserveur kernel:         res 41/40:00:91:a9:cc/00:02:9f:00:00/00 Emask 0x409 (media error) 
Apr 12 13:17:52 monserveur kernel: ata1.00: status: { DRDY ERR }
Apr 12 13:17:52 monserveur kernel: ata1.00: error: { UNC }
Apr 12 13:17:52 monserveur kernel: ata1.00: configured for UDMA/133
Apr 12 13:17:52 monserveur kernel: ata1: EH complete
Apr 12 13:17:52 monserveur kernel: ata1.00: exception Emask 0x0 SAct 0xf SErr 0x0 action 0x0
Apr 12 13:17:52 monserveur kernel: ata1.00: irq_stat 0x40000008
Apr 12 13:17:52 monserveur kernel: ata1.00: failed command: READ FPDMA QUEUED
Apr 12 13:17:52 monserveur kernel: ata1.00: cmd 60/00:00:31:a9:cc/02:00:9f:00:00/40 tag 0 ncq 262144 in
Apr 12 13:17:52 monserveur kernel:         res 41/40:00:91:a9:cc/00:02:9f:00:00/00 Emask 0x409 (media error) 
Apr 12 13:17:52 monserveur kernel: ata1.00: status: { DRDY ERR }
Apr 12 13:17:52 monserveur kernel: ata1.00: error: { UNC }
Apr 12 13:17:52 monserveur kernel: ata1.00: configured for UDMA/133
Apr 12 13:17:52 monserveur kernel: sd 0:0:0:0: [sda] Unhandled sense code
Apr 12 13:17:52 monserveur kernel: sd 0:0:0:0: [sda]  Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Apr 12 13:17:52 monserveur kernel: sd 0:0:0:0: [sda]  Sense Key : Medium Error [current] [descriptor]
Apr 12 13:17:52 monserveur kernel: Descriptor sense data with sense descriptors (in hex):
Apr 12 13:17:52 monserveur kernel:        72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00 
Apr 12 13:17:52 monserveur kernel:        9f cc a9 91 
Apr 12 13:17:52 monserveur kernel: sd 0:0:0:0: [sda]  Add. Sense: Unrecovered read error - auto reallocate failed
Apr 12 13:17:52 monserveur kernel: sd 0:0:0:0: [sda] CDB: Read(10): 28 00 9f cc a9 31 00 02 00 00
Apr 12 13:17:52 monserveur kernel: end_request: I/O error, dev sda, sector 2680990097
Apr 12 13:17:52 monserveur kernel: ata1: EH complete
Apr 12 13:17:52 monserveur kernel: ata1.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0
Apr 12 13:17:52 monserveur kernel: ata1.00: irq_stat 0x40000008
Apr 12 13:17:52 monserveur kernel: ata1.00: failed command: READ FPDMA QUEUED
Apr 12 13:17:52 monserveur kernel: ata1.00: cmd 60/08:00:91:a9:cc/00:00:9f:00:00/40 tag 0 ncq 4096 in
Apr 12 13:17:52 monserveur kernel:         res 41/40:08:91:a9:cc/00:00:9f:00:00/00 Emask 0x409 (media error) 
Apr 12 13:17:52 monserveur kernel: ata1.00: status: { DRDY ERR }
Apr 12 13:17:52 monserveur kernel: ata1.00: error: { UNC }
Apr 12 13:17:52 monserveur kernel: ata1.00: configured for UDMA/133
Apr 12 13:17:52 monserveur kernel: ata1: EH complete
Apr 12 13:17:53 monserveur kernel: ata1.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0
Apr 12 13:17:53 monserveur kernel: ata1.00: irq_stat 0x40000008
Apr 12 13:17:53 monserveur kernel: ata1.00: failed command: READ FPDMA QUEUED
Apr 12 13:17:53 monserveur kernel: ata1.00: cmd 60/08:00:91:a9:cc/00:00:9f:00:00/40 tag 0 ncq 4096 in
Apr 12 13:17:53 monserveur kernel:         res 41/40:08:91:a9:cc/00:00:9f:00:00/00 Emask 0x409 (media error) 
Apr 12 13:17:53 monserveur kernel: ata1.00: status: { DRDY ERR }
Apr 12 13:17:53 monserveur kernel: ata1.00: error: { UNC }
Apr 12 13:17:53 monserveur kernel: ata1.00: configured for UDMA/133
Apr 12 13:17:53 monserveur kernel: ata1: EH complete
Apr 12 13:17:53 monserveur kernel: ata1.00: exception Emask 0x0 SAct 0x7 SErr 0x0 action 0x0
Apr 12 13:17:53 monserveur kernel: ata1.00: irq_stat 0x40000008
Apr 12 13:17:53 monserveur kernel: ata1.00: failed command: READ FPDMA QUEUED
Apr 12 13:17:53 monserveur kernel: ata1.00: cmd 60/08:00:91:a9:cc/00:00:9f:00:00/40 tag 0 ncq 4096 in
Apr 12 13:17:53 monserveur kernel:         res 41/40:08:91:a9:cc/00:00:9f:00:00/00 Emask 0x409 (media error) 
Apr 12 13:17:53 monserveur kernel: ata1.00: status: { DRDY ERR }
Apr 12 13:17:53 monserveur kernel: ata1.00: error: { UNC }
Apr 12 13:17:53 monserveur kernel: ata1.00: configured for UDMA/133
Apr 12 13:17:53 monserveur kernel: ata1: EH complete
Apr 12 13:17:53 monserveur kernel: ata1.00: exception Emask 0x2 SAct 0xf SErr 0x3000400 action 0x6
Apr 12 13:17:53 monserveur kernel: ata1.00: irq_stat 0x40000008
Apr 12 13:17:53 monserveur kernel: ata1: SError: { Proto TrStaTrns UnrecFIS }
Apr 12 13:17:53 monserveur kernel: ata1.00: failed command: READ FPDMA QUEUED
Apr 12 13:17:53 monserveur kernel: ata1.00: cmd 60/00:00:09:40:64/01:00:46:00:00/40 tag 0 ncq 131072 in
Apr 12 13:17:53 monserveur kernel:         res 40/00:18:09:41:64/00:00:46:00:00/40 Emask 0x2 (HSM violation)
Apr 12 13:17:53 monserveur kernel: ata1.00: status: { DRDY }
Apr 12 13:17:53 monserveur kernel: ata1.00: failed command: READ FPDMA QUEUED
Apr 12 13:17:53 monserveur kernel: ata1.00: cmd 60/00:08:41:31:6b/01:00:46:00:00/40 tag 1 ncq 131072 in
Apr 12 13:17:53 monserveur kernel:         res 40/00:18:09:41:64/00:00:46:00:00/40 Emask 0x2 (HSM violation)
Apr 12 13:17:53 monserveur kernel: ata1.00: status: { DRDY }
Apr 12 13:17:53 monserveur kernel: ata1.00: failed command: READ FPDMA QUEUED
Apr 12 13:17:53 monserveur kernel: ata1.00: cmd 60/08:10:91:a9:cc/00:00:9f:00:00/40 tag 2 ncq 4096 in
Apr 12 13:17:53 monserveur kernel:         res 41/40:08:91:a9:cc/00:00:9f:00:00/00 Emask 0x40b (HSM violation) 
Apr 12 13:17:53 monserveur kernel: ata1.00: status: { DRDY ERR }
Apr 12 13:17:53 monserveur kernel: ata1.00: error: { UNC }
Apr 12 13:17:53 monserveur kernel: ata1.00: failed command: READ FPDMA QUEUED
Apr 12 13:17:53 monserveur kernel: ata1.00: cmd 60/00:18:09:41:64/01:00:46:00:00/40 tag 3 ncq 131072 in
Apr 12 13:17:53 monserveur kernel:         res 40/00:18:09:41:64/00:00:46:00:00/40 Emask 0x2 (HSM violation)
Apr 12 13:17:53 monserveur kernel: ata1.00: status: { DRDY }
Apr 12 13:17:53 monserveur kernel: ata1: hard resetting link
Apr 12 13:17:54 monserveur kernel: ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
Apr 12 13:17:54 monserveur kernel: ata1.00: configured for UDMA/133
Apr 12 13:17:54 monserveur kernel: ata1: EH complete
Apr 12 13:17:54 monserveur kernel: ata1.00: exception Emask 0x0 SAct 0x3 SErr 0x0 action 0x0
Apr 12 13:17:54 monserveur kernel: ata1.00: irq_stat 0x40000008
Apr 12 13:17:54 monserveur kernel: ata1.00: failed command: READ FPDMA QUEUED
Apr 12 13:17:54 monserveur kernel: ata1.00: cmd 60/08:08:91:a9:cc/00:00:9f:00:00/40 tag 1 ncq 4096 in
Apr 12 13:17:54 monserveur kernel:         res 41/40:08:91:a9:cc/00:00:9f:00:00/00 Emask 0x409 (media error) 
Apr 12 13:17:54 monserveur kernel: ata1.00: status: { DRDY ERR }
Apr 12 13:17:54 monserveur kernel: ata1.00: error: { UNC }
Apr 12 13:17:54 monserveur kernel: ata1.00: configured for UDMA/133
Apr 12 13:17:54 monserveur kernel: ata1: EH complete
Apr 12 13:17:54 monserveur kernel: ata1.00: exception Emask 0x0 SAct 0x3 SErr 0x0 action 0x0
Apr 12 13:17:54 monserveur kernel: ata1.00: irq_stat 0x40000008
Apr 12 13:17:54 monserveur kernel: ata1.00: failed command: READ FPDMA QUEUED
Apr 12 13:17:54 monserveur kernel: ata1.00: cmd 60/08:00:91:a9:cc/00:00:9f:00:00/40 tag 0 ncq 4096 in
Apr 12 13:17:54 monserveur kernel:         res 41/40:08:91:a9:cc/00:00:9f:00:00/00 Emask 0x409 (media error) 
Apr 12 13:17:54 monserveur kernel: ata1.00: status: { DRDY ERR }
Apr 12 13:17:54 monserveur kernel: ata1.00: error: { UNC }
Apr 12 13:17:54 monserveur mysqld: InnoDB: Error: tried to read 1048576 bytes at offset 0 1048576.
Apr 12 13:17:54 monserveur mysqld: InnoDB: Was only able to read 49152.
Apr 12 13:17:54 monserveur mysqld: InnoDB: Fatal error: cannot read from file. OS error number 17.
Apr 12 13:17:54 monserveur mysqld: 150412 13:17:54  InnoDB: Assertion failure in thread 140178360698656 in file ../../../storage/innobase/os/os0file.c line 2314
Apr 12 13:17:54 monserveur mysqld: InnoDB: We intentionally generate a memory trap.
Apr 12 13:17:54 monserveur mysqld: InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
Apr 12 13:17:54 monserveur mysqld: InnoDB: If you get repeated assertion failures or crashes, even
Apr 12 13:17:54 monserveur mysqld: InnoDB: immediately after the mysqld startup, there may be
Apr 12 13:17:54 monserveur mysqld: InnoDB: corruption in the InnoDB tablespace. Please refer to
Apr 12 13:17:54 monserveur mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html
Apr 12 13:17:54 monserveur mysqld: InnoDB: about forcing recovery.
Apr 12 13:17:54 monserveur mysqld: 11:17:54 UTC - mysqld got signal 6 ;
Apr 12 13:17:54 monserveur mysqld: This could be because you hit a bug. It is also possible that this binary
Apr 12 13:17:54 monserveur mysqld: or one of the libraries it was linked against is corrupt, improperly built,
Apr 12 13:17:54 monserveur mysqld: or misconfigured. This error can also be caused by malfunctioning hardware.
Apr 12 13:17:54 monserveur mysqld: We will try our best to scrape up some info that will hopefully help
Apr 12 13:17:54 monserveur mysqld: diagnose the problem, but since we have already crashed, 
Apr 12 13:17:54 monserveur mysqld: something is definitely wrong and this may fail.
Apr 12 13:17:54 monserveur mysqld: 
Apr 12 13:17:54 monserveur mysqld: key_buffer_size=16777216
Apr 12 13:17:54 monserveur mysqld: read_buffer_size=131072
Apr 12 13:17:54 monserveur mysqld: max_used_connections=0
Apr 12 13:17:54 monserveur mysqld: max_threads=151
Apr 12 13:17:54 monserveur mysqld: thread_count=0
Apr 12 13:17:54 monserveur mysqld: connection_count=0
Apr 12 13:17:54 monserveur mysqld: It is possible that mysqld could use up to 
Apr 12 13:17:54 monserveur mysqld: key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 346534 K  bytes of memory
Apr 12 13:17:54 monserveur mysqld: Hope that's ok; if not, decrease some variables in the equation.
Apr 12 13:17:54 monserveur mysqld: 
Apr 12 13:17:54 monserveur mysqld: Thread pointer: 0x0
Apr 12 13:17:54 monserveur mysqld: Attempting backtrace. You can use the following information to find out
Apr 12 13:17:54 monserveur mysqld: where mysqld died. If you see no messages after this, something went
Apr 12 13:17:54 monserveur mysqld: terribly wrong...
Apr 12 13:17:54 monserveur kernel: ata1.00: configured for UDMA/133
Apr 12 13:17:54 monserveur kernel: sd 0:0:0:0: [sda] Unhandled sense code
Apr 12 13:17:54 monserveur kernel: sd 0:0:0:0: [sda]  Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Apr 12 13:17:54 monserveur kernel: sd 0:0:0:0: [sda]  Sense Key : Medium Error [current] [descriptor]
Apr 12 13:17:54 monserveur kernel: Descriptor sense data with sense descriptors (in hex):
Apr 12 13:17:54 monserveur kernel:        72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00 
Apr 12 13:17:54 monserveur kernel:        9f cc a9 91 
Apr 12 13:17:54 monserveur kernel: sd 0:0:0:0: [sda]  Add. Sense: Unrecovered read error - auto reallocate failed
Apr 12 13:17:54 monserveur kernel: sd 0:0:0:0: [sda] CDB: Read(10): 28 00 9f cc a9 91 00 00 08 00
Apr 12 13:17:54 monserveur kernel: end_request: I/O error, dev sda, sector 2680990097
Apr 12 13:17:54 monserveur kernel: ata1: EH complete
Apr 12 13:17:54 monserveur mysqld: stack_bottom = 0 thread_stack 0x30000
Apr 12 13:17:54 monserveur mysqld: /usr/sbin/mysqld(my_print_stacktrace+0x29) [0x7f7dd1cd8049]
Apr 12 13:17:54 monserveur mysqld: /usr/sbin/mysqld(handle_fatal_signal+0x483) [0x7f7dd1aeac53]
Apr 12 13:17:54 monserveur mysqld: /lib/libpthread.so.0(+0xeff0) [0x7f7dd1235ff0]
Apr 12 13:17:54 monserveur mysqld: /lib/libc.so.6(gsignal+0x35) [0x7f7dcfcd81b5]
Apr 12 13:17:54 monserveur mysqld: /lib/libc.so.6(abort+0x180) [0x7f7dcfcdafc0]
Apr 12 13:17:54 monserveur mysqld: /usr/sbin/mysqld(os_file_flush+0) [0x7f7dd1c03560]
Apr 12 13:17:54 monserveur mysqld: /usr/sbin/mysqld(fil_io+0x1dd) [0x7f7dd1bd329d]
Apr 12 13:17:54 monserveur mysqld: /usr/sbin/mysqld(trx_sys_doublewrite_init_or_restore_pages+0x191) [0x7f7dd1c50741]
Apr 12 13:17:54 monserveur mysqld: /usr/sbin/mysqld(recv_scan_log_recs+0x72c) [0x7f7dd1bf969c]
Apr 12 13:17:54 monserveur mysqld: /usr/sbin/mysqld(recv_recovery_from_checkpoint_start+0x761) [0x7f7dd1bfb811]
Apr 12 13:17:54 monserveur mysqld: /usr/sbin/mysqld(innobase_start_or_create_for_mysql+0x12a3) [0x7f7dd1c3f153]
Apr 12 13:17:54 monserveur mysqld: /usr/sbin/mysqld(+0x5326ab) [0x7f7dd1b956ab]
Apr 12 13:17:54 monserveur mysqld: /usr/sbin/mysqld(ha_initialize_handlerton(st_plugin_int*)+0x31) [0x7f7dd1ada961]
Apr 12 13:17:54 monserveur mysqld: /usr/sbin/mysqld(+0x509932) [0x7f7dd1b6c932]
Apr 12 13:17:54 monserveur mysqld: /usr/sbin/mysqld(plugin_init(int*, char**, int)+0x7d8) [0x7f7dd1b6fed8]
Apr 12 13:17:54 monserveur mysqld: /usr/sbin/mysqld(+0x378f35) [0x7f7dd19dbf35]
Apr 12 13:17:54 monserveur mysqld: /usr/sbin/mysqld(main+0x20e) [0x7f7dd19e046e]
Apr 12 13:17:54 monserveur mysqld: /lib/libc.so.6(__libc_start_main+0xfd) [0x7f7dcfcc4c8d]
Apr 12 13:17:54 monserveur mysqld: /usr/sbin/mysqld(+0x29f609) [0x7f7dd1902609]
Apr 12 13:17:54 monserveur mysqld: The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
Apr 12 13:17:54 monserveur mysqld: information that should help you find out what is causing the crash.
Apr 12 13:17:54 monserveur mysqld_safe: mysqld from pid file /var/run/mysqld/mysqld.pid ended
Apr 12 13:18:01 monserveur /USR/SBIN/CRON[15744]: (root) CMD (/usr/local/rtm/bin/rtm 9 > /dev/null 2> /dev/null)
Apr 12 13:18:04 monserveur /etc/init.d/mysql[15825]: 0 processes alive and '/usr/bin/mysqladmin --defaults-file=/etc/mysql/debian.cnf ping' resulted in
Apr 12 13:18:04 monserveur /etc/init.d/mysql[15825]: #007/usr/bin/mysqladmin: connect to server at 'localhost' failed
Apr 12 13:18:04 monserveur /etc/init.d/mysql[15825]: error: 'Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)'
Apr 12 13:18:04 monserveur /etc/init.d/mysql[15825]: Check that mysqld is running and that the socket: '/var/run/mysqld/mysqld.sock' exists!
Apr 12 13:18:04 monserveur /etc/init.d/mysql[15825]:
- - - Mise à jour - - -

A toute fin utile , voici aussi le rapport Smart Drive Status lancé hier soir :
Code:
smartctl 5.40 2010-07-12 r3124 [x86_64-unknown-linux-gnu] (local build)
Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net

=== START OF INFORMATION SECTION ===
Device Model:     ST2000DM001-9YN164
Serial Number:    W2F02VZN
Firmware Version: CC4C
User Capacity:    2,000,398,934,016 bytes
Device is:        Not in smartctl database [for details use: -P showall]
ATA Version is:   8
ATA Standard is:  ATA-8-ACS revision 4
Local Time is:    Sun Apr 12 13:37:25 2015 CEST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status:  (0x00)	Offline data collection activity
					was never started.
					Auto Offline Data Collection: Disabled.
Self-test execution status:      ( 113)	The previous self-test completed having
					the read element of the test failed.
Total time to complete Offline 
data collection: 		 ( 600) seconds.
Offline data collection
capabilities: 			 (0x73) SMART execute Offline immediate.
					Auto Offline data collection on/off support.
					Suspend Offline collection upon new
					command.
					No Offline surface scan supported.
					Self-test supported.
					Conveyance Self-test supported.
					Selective Self-test supported.
SMART capabilities:            (0x0003)	Saves SMART data before entering
					power-saving mode.
					Supports SMART auto save timer.
Error logging capability:        (0x01)	Error logging supported.
					General Purpose Logging supported.
Short self-test routine 
recommended polling time: 	 (   1) minutes.
Extended self-test routine
recommended polling time: 	 ( 255) minutes.
Conveyance self-test routine
recommended polling time: 	 (   2) minutes.
SCT capabilities: 	       (0x3085)	SCT Status supported.

SMART Attributes Data Structure revision number: 10
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x000f   117   080   006    Pre-fail  Always       -       120159722
  3 Spin_Up_Time            0x0003   093   092   000    Pre-fail  Always       -       0
  4 Start_Stop_Count        0x0032   100   100   020    Old_age   Always       -       33
  5 Reallocated_Sector_Ct   0x0033   097   097   036    Pre-fail  Always       -       4624
  7 Seek_Error_Rate         0x000f   083   060   030    Pre-fail  Always       -       234359129
  9 Power_On_Hours          0x0032   070   070   000    Old_age   Always       -       27100
 10 Spin_Retry_Count        0x0013   100   100   097    Pre-fail  Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   020    Old_age   Always       -       32
183 Runtime_Bad_Block       0x0032   095   095   000    Old_age   Always       -       5
184 End-to-End_Error        0x0032   100   100   099    Old_age   Always       -       0
187 Reported_Uncorrect      0x0032   001   001   000    Old_age   Always       -       1283
188 Command_Timeout         0x0032   100   096   000    Old_age   Always       -       17180262413
189 High_Fly_Writes         0x003a   100   100   000    Old_age   Always       -       0
190 Airflow_Temperature_Cel 0x0022   064   049   045    Old_age   Always       -       36 (Lifetime Min/Max 34/39)
191 G-Sense_Error_Rate      0x0032   100   100   000    Old_age   Always       -       0
192 Power-Off_Retract_Count 0x0032   100   100   000    Old_age   Always       -       31
193 Load_Cycle_Count        0x0032   100   100   000    Old_age   Always       -       942
194 Temperature_Celsius     0x0022   036   051   000    Old_age   Always       -       36 (0 18 0 0)
197 Current_Pending_Sector  0x0012   100   001   000    Old_age   Always       -       79
198 Offline_Uncorrectable   0x0010   100   001   000    Old_age   Offline      -       79
199 UDMA_CRC_Error_Count    0x003e   200   200   000    Old_age   Always       -       0
240 Head_Flying_Hours       0x0000   100   253   000    Old_age   Offline      -       1108101589456
241 Total_LBAs_Written      0x0000   100   253   000    Old_age   Offline      -       6347613856539
242 Total_LBAs_Read         0x0000   100   253   000    Old_age   Offline      -       23417919755213

SMART Error Log Version: 1
ATA Error Count: 2326 (device log contains only the most recent five errors)
	CR = Command Register [HEX]
	FR = Features Register [HEX]
	SC = Sector Count Register [HEX]
	SN = Sector Number Register [HEX]
	CL = Cylinder Low Register [HEX]
	CH = Cylinder High Register [HEX]
	DH = Device/Head Register [HEX]
	DC = Device Command Register [HEX]
	ER = Error register [HEX]
	ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.

Error 2326 occurred at disk power-on lifetime: 27100 hours (1129 days + 4 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 ff ff ff 0f

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 00 00 ff ff ff 4f 00      18:25:34.753  READ FPDMA QUEUED
  60 00 08 ff ff ff 4f 00      18:25:34.753  READ FPDMA QUEUED
  60 00 00 ff ff ff 4f 00      18:25:34.753  READ FPDMA QUEUED
  60 00 00 ff ff ff 4f 00      18:25:34.753  READ FPDMA QUEUED
  60 00 00 ff ff ff 4f 00      18:25:34.753  READ FPDMA QUEUED

Error 2325 occurred at disk power-on lifetime: 27100 hours (1129 days + 4 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 ff ff ff 0f

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 00 00 ff ff ff 4f 00      18:25:34.753  READ FPDMA QUEUED
  60 00 08 ff ff ff 4f 00      18:25:34.753  READ FPDMA QUEUED
  60 00 00 ff ff ff 4f 00      18:25:34.753  READ FPDMA QUEUED
  60 00 00 ff ff ff 4f 00      18:25:34.753  READ FPDMA QUEUED
  60 00 00 ff ff ff 4f 00      18:25:34.753  READ FPDMA QUEUED

Error 2324 occurred at disk power-on lifetime: 27100 hours (1129 days + 4 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 ff ff ff 0f

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 00 00 ff ff ff 4f 00      18:25:34.456  READ FPDMA QUEUED
  60 00 00 ff ff ff 4f 00      18:25:34.456  READ FPDMA QUEUED
  60 00 00 ff ff ff 4f 00      18:25:34.456  READ FPDMA QUEUED
  60 00 00 ff ff ff 4f 00      18:25:34.453  READ FPDMA QUEUED
  60 00 00 ff ff ff 4f 00      18:25:34.453  READ FPDMA QUEUED

Error 2323 occurred at disk power-on lifetime: 27100 hours (1129 days + 4 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 ff ff ff 0f

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 00 00 ff ff ff 4f 00      18:25:34.456  READ FPDMA QUEUED
  60 00 00 ff ff ff 4f 00      18:25:34.456  READ FPDMA QUEUED
  60 00 00 ff ff ff 4f 00      18:25:34.456  READ FPDMA QUEUED
  60 00 00 ff ff ff 4f 00      18:25:34.453  READ FPDMA QUEUED
  60 00 00 ff ff ff 4f 00      18:25:34.453  READ FPDMA QUEUED

Error 2322 occurred at disk power-on lifetime: 27100 hours (1129 days + 4 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 00 ff ff ff 0f

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  60 00 00 ff ff ff 4f 00      18:25:34.156  READ FPDMA QUEUED
  60 00 00 ff ff ff 4f 00      18:25:34.155  READ FPDMA QUEUED
  60 00 08 ff ff ff 4f 00      18:25:34.153  READ FPDMA QUEUED
  60 00 00 ff ff ff 4f 00      18:25:34.153  READ FPDMA QUEUED
  60 00 00 ff ff ff 4f 00      18:25:34.153  READ FPDMA QUEUED

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Extended offline    Completed: read failure       10%     27087         3750761896
# 2  Extended offline    Interrupted (host reset)      20%     27081         -
# 3  Short offline       Completed without error       00%     27078         -
# 4  Extended offline    Aborted by host               90%     27078         -
# 5  Short offline       Completed without error       00%       981         -
# 6  Short offline       Completed without error       00%       971         -
# 7  Short offline       Completed without error       00%       971         -
# 8  Short offline       Completed without error       00%       971         -
# 9  Short offline       Completed without error       00%       971         -
#10  Short offline       Completed without error       00%       971         -
#11  Short offline       Completed without error       00%       971         -
#12  Short offline       Completed without error       00%       971         -
#13  Short offline       Completed without error       00%       971         -
#14  Short offline       Completed without error       00%        12         -
#15  Short offline       Completed without error       00%         3         -
#16  Short offline       Completed without error       00%         3         -

SMART Selective self-test log data structure revision number 1
 SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
    1        0        0  Not_testing
    2        0        0  Not_testing
    3        0        0  Not_testing
    4        0        0  Not_testing
    5        0        0  Not_testing
Selective self-test flags (0x0):
  After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.