Ce site est optimisé pour être consulté depuis un navigateur moderne dans lequel JavaScript est activé.

Erreur MySql après maj...

pti-jean

Bonjour,

C'est normal que suite à la dernière mise à jour, j'ai MySql qui est en erreur ??
Je ne peux plus m'y connecter:

$ mysql -u root -p
Enter password:
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)

Le log erreur:
https://paste.chapril.org/?1edb408f7aa4b81f#qWEdZdaqhnLGCvrR5w6vPr4UxBjkspHYNjC3zBb3gyp

Une idée du pb ?

JM

bruno

Bonjour,

Il me semble t'avoir dit dans ton dernier message qu'il fallait corriger les erreurs de configuration de MySQL.
Dans tes logs j'en vois au moins trois :

unknown variable 'query_cache_limit=1M'.

The syntax 'validate password plugin' is deprecated and will be removed in a future release. Please use validate_password component instead.

The syntax 'expire-logs-days' is deprecated and will be removed in a future release. Please use binlog_expire_logs_seconds instead.

J'avais aussi indiqué que ce n'est pas une bonne idée de mettre un mot de passe à l'utilisateur root de MySQL. Voir, point 3.4 de la doc MySQL

pti-jean

Re,

Là c'est pas la même machine...
Bruno, tu me montres les messages d'erreurs... qu'est que je pourrais appliquer comme correctif ??

JM

bruno

Il faut supprimer ces directives obsolètes de la configuration de mysql. Voir ces fichiers (et autres) :
/etc/mysql/mysql.cnf
/etc/mysql/mysql.conf.d/mysql.cnf
/etc/mysql/mysql.conf.d/mysqld.cnf

pti-jean

Je dois dire que pour le moment cela ne m'aide pas trop... Comment on reconnaît une directive obsolète ???

JM

pti-jean

Voila le message que j'ai:

L'installation du paquet a échoué Error while installing package: installed mysql-serveur-8.0 package post-installation script subprocess returned error exit status 1

quand je fais une mise à jour maintenant!

JM

bruno

pti-jean a écritComment on reconnaît une directive obsolète ???

Aux erreurs qu'elle génère dans les logs.
Tu aurais au moins pu faire l'effort de chercher dans les fichiers que j'ai indiqué, les directives qui génèrent des erreurs.

S'il y a maintenant une erreur d'installation concernant mysql-server, c'est que tu as désinstallé puis tenter de réinstaller car dans les logs que tu as donné au dpéat le service fonctionnait. Il faut expliquer en détail ce que tu as fait.

pti-jean

Bonjour,

Aux erreurs qu'elle génère dans les logs.
Tu aurais au moins pu faire l'effort de chercher dans les fichiers que j'ai indiqué, les directives qui génèrent des erreurs.

Concernent les directives "query_cache_limit" et "expire_logs_days", je les ai commentés:

$ rgrep "query_cache_limit\|expire_logs_days" /etc/mysql/
grep: /etc/mysql/debian.cnf: Permission non accordée
/etc/mysql/my.cnf:### query_cache_limit = 1M
/etc/mysql/my.cnf:### expire_logs_days  = 10

Concernent la directive "'validate password plugin" à remplacer par "validate_password", j'ai pas trouvé:

$ rgrep password /etc/mysql/
/etc/mysql/my.cnf.fallback:# It has been reported that passwords should be enclosed with ticks/quotes
grep: /etc/mysql/debian.cnf: Permission non accordée
/etc/mysql/my.cnf:# It has been reported that passwords should be enclosed with ticks/quotes

ça a l'air plus subtile... une idée ??

S'il y a maintenant une erreur d'installation concernant mysql-server, c'est que tu as désinstallé puis tenter de réinstaller car dans les logs que tu as donné au dpéat le service fonctionnait. Il faut expliquer en détail ce que tu as fait.

Je n'ai rien fait... j'ai juste fait une mise à jour!

Suite aux dernières modifs, j'ai tenté de redémarrer:

$ sudo systemctl restart mysql.service 
Job for mysql.service failed because the control process exited with error code.
See "systemctl status mysql.service" and "journalctl -xe" for details.

$ systemctl status mysql.service
● mysql.service - MySQL Community Server
     Loaded: loaded (/lib/systemd/system/mysql.service; enabled; vendor preset: enabled)
     Active: activating (start) since Fri 2020-10-30 09:32:26 CET; 490ms ago
    Process: 1762912 ExecStartPre=/usr/share/mysql/mysql-systemd-start pre (code=exited, status=0/SUCCESS)
   Main PID: 1762920 (mysqld)
     Status: "Server startup in progress"
      Tasks: 2 (limit: 9349)
     Memory: 232.3M
     CGroup: /system.slice/mysql.service
             └─1762920 /usr/sbin/mysqld

oct. 30 09:32:26 jeanmobile3 systemd[1]: Starting MySQL Community Server...

Le "journalctl -xe":
https://paste.chapril.org/?acfe9b160c5de5ea#J7wiaakRqR4p6s6EVSTmAYADSP5fmCzRUKNpwjGbMr3G

JM

bruno

Il faut indiquer le contenu complet de /etc/mysql/my.cnf.

journalctl ne donne aucune information utile pour l'instant.

pti-jean

Bonjour bruno,

Contant d'avoir des nouvelles! 🙂

Le contenu de /etc/mysql/my.cnf :

$ cat /etc/mysql/my.cnf
#
# The MySQL database server configuration file.
#
# You can copy this to one of:
# - "/etc/mysql/my.cnf" to set global options,
# - "~/.my.cnf" to set user-specific options.
# 
# One can use all long options that the program supports.
# Run program with --help to get a list of available options and with
# --print-defaults to see which it would actually understand and use.
#
# For explanations see
# http://dev.mysql.com/doc/mysql/en/server-system-variables.html

# This will be passed to all mysql clients
# It has been reported that passwords should be enclosed with ticks/quotes
# escpecially if they contain "#" chars...
# Remember to edit /etc/mysql/debian.cnf when changing the socket location.

# Here is entries for some specific programs
# The following values assume you have at least 32M ram

[mysqld_safe]
socket		= /var/run/mysqld/mysqld.sock
nice		= 0

[mysqld]
sql_mode = NO_ENGINE_SUBSTITUTION
#
# * Basic Settings
#
user		= mysql
pid-file	= /var/run/mysqld/mysqld.pid
socket		= /var/run/mysqld/mysqld.sock
port		= 3306
basedir		= /usr
datadir		= /var/lib/mysql
tmpdir		= /tmp
lc-messages-dir	= /usr/share/mysql
skip-external-locking
#
# Instead of skip-networking the default is now to listen only on
# localhost which is more compatible and is not less secure.
bind-address		= 127.0.0.1
#
# * Fine Tuning
#
key_buffer_size		= 16M
max_allowed_packet	= 16M
thread_stack		= 192K
thread_cache_size       = 8
# This replaces the startup script and checks MyISAM tables if needed
# the first time they are touched
myisam-recover-options  = BACKUP
#max_connections        = 100
#table_cache            = 64
#thread_concurrency     = 10
#
# * Query Cache Configuration
#
### query_cache_limit	= 1M
query_cache_size        = 16M
#
# * Logging and Replication
#
# Both location gets rotated by the cronjob.
# Be aware that this log type is a performance killer.
# As of 5.1 you can enable the log at runtime!
#general_log_file        = /var/log/mysql/mysql.log
#general_log             = 1
#
# Error log - should be very few entries.
#
log_error = /var/log/mysql/error.log
#
# Here you can see queries with especially long duration
#log_slow_queries	= /var/log/mysql/mysql-slow.log
#long_query_time = 2
#log-queries-not-using-indexes
#
# The following can be used as easy to replay backup logs or for replication.
# note: if you are setting up a replication slave, see README.Debian about
#       other settings you may need to change.
#server-id		= 1
#log_bin			= /var/log/mysql/mysql-bin.log
### expire_logs_days	= 10
max_binlog_size   = 100M
#binlog_do_db		= include_database_name
#binlog_ignore_db	= include_database_name
#
# * InnoDB
#
# InnoDB is enabled by default with a 10MB datafile in /var/lib/mysql/.
# Read the manual for more InnoDB related options. There are many!
#
# * Security Features
#
# Read the manual, too, if you want chroot!
# chroot = /var/lib/mysql/
#
# For generating SSL certificates I recommend the OpenSSL GUI "tinyca".
#
# ssl-ca=/etc/mysql/cacert.pem
# ssl-cert=/etc/mysql/server-cert.pem
# ssl-key=/etc/mysql/server-key.pem

Au pire sur cet ordinateur, je crois que mes bases de données sont pas importantes... On pourrait peut-être purger le tout avec un "apt puge"... une idée de la cmd ?

JM

bruno

Remet le fichier fournit par la mainteneur du paquet mysql-server8.0 :

# The MySQL database server configuration file.
#
# One can use all long options that the program supports.
# Run program with --help to get a list of available options and with
# --print-defaults to see which it would actually understand and use.
#
# For explanations see
# http://dev.mysql.com/doc/mysql/en/server-system-variables.html

# Here is entries for some specific programs
# The following values assume you have at least 32M ram

[mysqld]
#
# * Basic Settings
#
user		= mysql
# pid-file	= /var/run/mysqld/mysqld.pid
# socket	= /var/run/mysqld/mysqld.sock
# port		= 3306
# datadir	= /var/lib/mysql


# If MySQL is running as a replication slave, this should be
# changed. Ref https://dev.mysql.com/doc/refman/8.0/en/server-system-variables.html#sysvar_tmpdir
# tmpdir		= /tmp
#
# Instead of skip-networking the default is now to listen only on
# localhost which is more compatible and is not less secure.
bind-address		= 127.0.0.1
#
# * Fine Tuning
#
key_buffer_size		= 16M
# max_allowed_packet	= 64M
# thread_stack		= 256K

# thread_cache_size       = -1

# This replaces the startup script and checks MyISAM tables if needed
# the first time they are touched
myisam-recover-options  = BACKUP

# max_connections        = 151

# table_open_cache       = 4000

#
# * Logging and Replication
#
# Both location gets rotated by the cronjob.
#
# Log all queries
# Be aware that this log type is a performance killer.
# general_log_file        = /var/log/mysql/query.log
# general_log             = 1
#
# Error log - should be very few entries.
#
log_error = /var/log/mysql/error.log
#
# Here you can see queries with especially long duration
# slow_query_log		= 1
# slow_query_log_file	= /var/log/mysql/mysql-slow.log
# long_query_time = 2
# log-queries-not-using-indexes
#
# The following can be used as easy to replay backup logs or for replication.
# note: if you are setting up a replication slave, see README.Debian about
#       other settings you may need to change.
# server-id		= 1
# log_bin			= /var/log/mysql/mysql-bin.log
# binlog_expire_logs_seconds	= 2592000
max_binlog_size   = 100M
# binlog_do_db		= include_database_name
# binlog_ignore_db	= include_database_name

pti-jean

Ok Bruno, ça a résolu le problème.
Chose que j’explique pas... j'accède à la base par:

$ sudo mysql

alors que j'ai un mot de passe root dans mon gestionnaire de mot de passe ??
Va savoir Charles!!! 😉

JM

pti-jean

Merci Bruno! 🙂

JM

bruno

#12 c'est expliqué dans la doc [doc]mysql[/doc]

pti-jean

#12 c'est expliqué dans la doc mysql

Ha... tu crois ? Quel chapitre ?? qui explique pourquoi je suis passé d'une base MySql avec un mot de passe root, à une base MySql sans!?

De plus.... sur l'autre machine... Celle qui a eu un problème de répertoire log après migration et nettoyage des rc:
http://forum.ubuntu-fr.org/viewtopic.php?id=2057668
J'y ai effectué toutes les mises à jours, et j'ai toujours le mot de passe root... Bizarre que les deux Kubuntu se comportent différemment!

JM