gros problème avec mysql, suite a un problème de coupure de courant ma base de données ne démarre plus!!!
voir le message qui apparait en essayant de démarrer la base mysql: texte en gras
ERROR 2002 (HY000): Can’t connect to local MySQL server through socket ‘/var/run/mysqld/mysqld.sock’ (2 “No such file or directory”)
ensuite différente info:
root@didiercl:/var/run/mysqld# systemctl status mysql.service
● mysql.service - LSB: Start and stop the mysql database server daemon
Loaded: loaded (/etc/init.d/mysql)
Active: failed (Result: exit-code) since Sun 2017-12-24 15:57:48 CET; 35s ago
Process: 8474 ExecStart=/etc/init.d/mysql start (code=exited, status=1/FAILURE )
Dec 24 15:57:15 didiercl.me systemd[1]: Starting LSB: Start and stop the mys… Dec 24 15:57:48 didiercl.me mysql[8474]: Starting MariaDB database server: m…! Dec 24 15:57:48 didiercl.me systemd[1]: mysql.service: control process exite…1 Dec 24 15:57:48 didiercl.me systemd[1]: Failed to start LSB: Start and stop … Dec 24 15:57:48 didiercl.me systemd[1]: Unit mysql.service entered failed state. Hint: Some lines were ellipsized, use -l to show in full. root@didiercl:/var/run/mysqld# journalctl -xn – Logs begin at Sat 2017-12-23 23:45:02 CET, end at Sun 2017-12-24 15:58:30 CET Dec 24 15:58:27 didiercl.me imap[8927]: antispam: pipe backend program arg[0] = Dec 24 15:58:27 didiercl.me imap[8927]: antispam: pipe backend program arg[1] = Dec 24 15:58:27 didiercl.me imap[8927]: antispam: pipe backend program arg[2] = Dec 24 15:58:27 didiercl.me imap[8927]: antispam: pipe backend program arg[3] = Dec 24 15:58:27 didiercl.me imap[8927]: antispam: pipe backend tmpdir /tmp Dec 24 15:58:27 didiercl.me dovecot[2943]: imap(dclaus): Disconnected: Logged ou Dec 24 15:58:30 didiercl.me systemd[1]: Cannot add dependency job for unit rmilt Dec 24 15:58:30 didiercl.me systemd[1]: Cannot add dependency job for unit rspam Dec 24 15:58:30 didiercl.me systemd[1]: Starting YunoHost VPN Client Checker… – Subject: Unit ynh-vpnclient-checker.service has begun with start-up – Defined-By: systemd – Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel – – Unit ynh-vpnclient-checker.service has begun starting up. Dec 24 15:58:30 didiercl.me systemd[1]: Started YunoHost VPN Client Checker… – Subject: Unit ynh-vpnclient-checker.service has finished start-up – Defined-By: systemd – Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel – – Unit ynh-vpnclient-checker.service has finished starting up. – – The start-up result is done. lines 1-23…skipping… – Logs begin at Sat 2017-12-23 23:45:02 CET, end at Sun 2017-12-24 15:58:30 CET. – Dec 24 15:58:27 didiercl.me imap[8927]: antispam: pipe backend program arg[0] = -h Dec 24 15:58:27 didiercl.me imap[8927]: antispam: pipe backend program arg[1] = localhost:11334 Dec 24 15:58:27 didiercl.me imap[8927]: antispam: pipe backend program arg[2] = -P Dec 24 15:58:27 didiercl.me imap[8927]: antispam: pipe backend program arg[3] = q1 Dec 24 15:58:27 didiercl.me imap[8927]: antispam: pipe backend tmpdir /tmp Dec 24 15:58:27 didiercl.me dovecot[2943]: imap(dclaus): Disconnected: Logged out in=89 out=878 Dec 24 15:58:30 didiercl.me systemd[1]: Cannot add dependency job for unit rmilter.socket, ignoring: Unit rmilter.socket failed to load: No such file or directory. Dec 24 15:58:30 didiercl.me systemd[1]: Cannot add dependency job for unit rspamd.socket, ignoring: Unit rspamd.socket failed to load: No such file or directory. Dec 24 15:58:30 didiercl.me systemd[1]: Starting YunoHost VPN Client Checker… – Subject: Unit ynh-vpnclient-checker.service has begun with start-up – Defined-By: systemd – Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel – – Unit ynh-vpnclient-checker.service has begun starting up. Dec 24 15:58:30 didiercl.me systemd[1]: Started YunoHost VPN Client Checker… – Subject: Unit ynh-vpnclient-checker.service has finished start-up – Defined-By: systemd – Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel – – Unit ynh-vpnclient-checker.service has finished starting up. –
– The start-up result is done.
y a t’il une solution pour essayer de réparer tout les services sont “out” à part la messagerie.
==> /var/lib/mysql/didiercl.me.err <==
171224 13:54:29 [ERROR] Fatal error: Can't open and lock privilege tables: Incorrect file format 'host'
171224 13:54:30 mysqld_safe mysqld from pid file /var/lib/mysql/didiercl.me.pid ended
171224 15:49:38 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
171224 15:49:38 [Note] /usr/sbin/mysqld (mysqld 10.0.32-MariaDB-0+deb8u1) starting as process 8203 ...
171224 15:49:38 [Note] InnoDB: innodb_empty_free_list_algorithm has been changed to legacy because of small buffer pool size. In order to use backoff, increase buffer pool at least up to 20MB.
171224 15:49:38 [Note] InnoDB: Using mutexes to ref count buffer pool pages
171224 15:49:38 [Note] InnoDB: The InnoDB memory heap is disabled
171224 15:49:38 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
171224 15:49:38 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
171224 15:49:38 [Note] InnoDB: Compressed tables use zlib 1.2.8
171224 15:49:38 [Note] InnoDB: Using Linux native AIO
171224 15:49:38 [Note] InnoDB: Not using CPU crc32 instructions
171224 15:49:38 [Note] InnoDB: Initializing buffer pool, size = 128.0M
171224 15:49:38 [Note] InnoDB: Completed initialization of buffer pool
171224 15:49:38 [Note] InnoDB: Highest supported file format is Barracuda.
171224 15:49:38 [Note] InnoDB: The log sequence numbers 548999839 and 548999839 in ibdata files do not match the log sequence number 549033522 in the ib_logfiles!
171224 15:49:38 [Note] InnoDB: Restoring possible half-written data pages from the doublewrite buffer...
171224 15:49:38 [Note] InnoDB: 128 rollback segment(s) are active.
171224 15:49:38 [Note] InnoDB: Waiting for purge to start
171224 15:49:38 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.36-82.1 started; log sequence number 549033522
171224 15:49:39 [Note] Plugin 'FEEDBACK' is disabled.
171224 15:49:39 [ERROR] Can't open the mysql.plugin table. Please run mysql_upgrade to create it.
171224 15:49:39 [Note] Server socket created on IP: '::'.
171224 15:49:39 [ERROR] Fatal error: Can't open and lock privilege tables: Incorrect file format 'host'
171224 15:49:39 mysqld_safe mysqld from pid file /var/lib/mysql/didiercl.me.pid ended
171224 15:57:16 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
171224 15:57:16 [Note] /usr/sbin/mysqld (mysqld 10.0.32-MariaDB-0+deb8u1) starting as process 8612 ...
171224 15:57:16 [Note] InnoDB: innodb_empty_free_list_algorithm has been changed to legacy because of small buffer pool size. In order to use backoff, increase buffer pool at least up to 20MB.
171224 15:57:16 [Note] InnoDB: Using mutexes to ref count buffer pool pages
171224 15:57:16 [Note] InnoDB: The InnoDB memory heap is disabled
171224 15:57:16 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
171224 15:57:16 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
171224 15:57:16 [Note] InnoDB: Compressed tables use zlib 1.2.8
171224 15:57:16 [Note] InnoDB: Using Linux native AIO
171224 15:57:16 [Note] InnoDB: Not using CPU crc32 instructions
171224 15:57:16 [Note] InnoDB: Initializing buffer pool, size = 128.0M
171224 15:57:16 [Note] InnoDB: Completed initialization of buffer pool
171224 15:57:16 [Note] InnoDB: Highest supported file format is Barracuda.
171224 15:57:16 [Note] InnoDB: The log sequence numbers 548999839 and 548999839 in ibdata files do not match the log sequence number 549033522 in the ib_logfiles!
171224 15:57:16 [Note] InnoDB: Restoring possible half-written data pages from the doublewrite buffer...
171224 15:57:17 [Note] InnoDB: 128 rollback segment(s) are active.
171224 15:57:17 [Note] InnoDB: Waiting for purge to start
171224 15:57:17 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.36-82.1 started; log sequence number 549033522
171224 15:57:17 [Note] Plugin 'FEEDBACK' is disabled.
171224 15:57:17 [ERROR] Can't open the mysql.plugin table. Please run mysql_upgrade to create it.
171224 15:57:17 [Note] Server socket created on IP: '::'.
171224 15:57:17 [ERROR] Fatal error: Can't open and lock privilege tables: Incorrect file format 'host'
171224 15:57:17 mysqld_safe mysqld from pid file /var/lib/mysql/didiercl.me.pid ended
==> /var/lib/mysql/yunohost.yunohost.org.err <==
170327 22:07:38 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
170327 22:07:39 [Note] /usr/sbin/mysqld (mysqld 10.0.30-MariaDB-0+deb8u1) starting as process 18090 ...
170327 22:07:39 [Note] InnoDB: Using mutexes to ref count buffer pool pages
170327 22:07:39 [Note] InnoDB: The InnoDB memory heap is disabled
170327 22:07:39 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
170327 22:07:39 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
170327 22:07:39 [Note] InnoDB: Compressed tables use zlib 1.2.8
170327 22:07:39 [Note] InnoDB: Using Linux native AIO
170327 22:07:39 [Note] InnoDB: Not using CPU crc32 instructions
170327 22:07:39 [Note] InnoDB: Initializing buffer pool, size = 128.0M
170327 22:07:39 [Note] InnoDB: Completed initialization of buffer pool
170327 22:07:39 [Note] InnoDB: Highest supported file format is Barracuda.
170327 22:07:39 [Note] InnoDB: 128 rollback segment(s) are active.
170327 22:07:39 [Note] InnoDB: Waiting for purge to start
170327 22:07:39 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.35-80.0 started; log sequence number 1616827
170327 22:07:39 [Note] Plugin 'FEEDBACK' is disabled.
170327 22:07:39 [Note] Server socket created on IP: '::'.
170327 22:07:39 [Note] /usr/sbin/mysqld: ready for connections.
Version: '10.0.30-MariaDB-0+deb8u1' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Debian)
du coup ca ressemble à de la corruption de DB mysql (assez typique quand il y a des coupures de courant… mais ca reste très rageant que mysql n’ait pas de meilleurs mécanismes pour empecher ca…)
En tout cas je pense que tu peux tenter la procédure donnée dans ce thread … même si c’est pas garanti de résoudre le problème
Il te faut deux terminal différents connectés en SSH sur ton serveur.
Dans le 1er terminal, lancer manuellement mysql (en bypassant les permissions) :
$ sudo mysqld --skip-grant-tables
Dans le 2eme terminal, ouvrir une console mysql et demander à réparer la table host.
$ mysql
mysql> use mysql
mysql> repair table host use_frm;
mysql> exit
Retour dans le premier terminal : faire Ctrl+C pour clore le processus mysql
Relancer proprement le service mysql
$ service mysql restart
Verifier que mysql s’est bien lancé via service mysql status. Si il y a toujours un problème, refaire un tail -n 50 /var/lib/mysql/*.err
Je pensais le problème résolue mais suite au redémarrage de la brique je me suis rendue compte que cela persistait enfin de compte c’ est le bout de code suivant qui permet de redémarrer la base mysql “mysqld_safe --user=root --skip-grant-tables” et cela ne fonctionne que sur les applications installées en essayant d’en installer une autre je me suis rendu compte que l’instal ce déroule sans problème mais que l’application n’est pas présente dans l’interface utilisateur.
Donc je me retrouve au même point.
As tu peut être une autre idée merci d’avance pour ton aide.
