ERREUR 2006 (HY000) à la ligne 1: le serveur MySQL est parti
ERREUR 2006 (HY000) à la ligne 1: le serveur MySQL est parti
Je suis confronté au même problème. J'essaie de restaurer le fichier mysqldump sur ma machine. La taille du fichier est de 2,7 Mo. Je reçois le message d'erreur «ERREUR 2006 (HY000) à la ligne 1: le serveur MySQL est parti» J'ai augmenté la taille de max_allowed_packet et wait_timeout. Mais rien n'a fonctionné.
Voici le contenu de mon fichier (my-medium.ini), suggérez-moi s'il vous plait. Mon installation contient divers fichiers ini, et j’ai modifié Merci d'avance!!
# Example MySQL config file for medium systems.
#
# This is for a system with little memory (32M - 64M) where MySQL plays
# an important part, or systems up to 128M where MySQL is used together with
# other programs (such as a web server)
#
# You can copy this file to
# /etc/my.cnf to set global options,
# mysql-data-dir/my.cnf to set server-specific options (in this
# installation this directory is C:\mysql\data) or
# ~/.my.cnf to set user-specific options.
#
# In this file, you can use all long options that a program supports.
# If you want to know which options a program supports, run the program
# with the "--help" option.
# The following options will be passed to all MySQL clients
[client]
#password = your_password
port = 3306
socket = /tmp/mysql.sock
# Here follows entries for some specific programs
# The MySQL server
[mysqld]
port = 3306
socket = /tmp/mysql.sock
skip-locking
key_buffer_size = 16M
max_allowed_packet = 512M
table_open_cache = 64
sort_buffer_size = 512K
net_buffer_length = 8K
read_buffer_size = 256K
read_rnd_buffer_size = 512K
myisam_sort_buffer_size = 8M
wait_timeout = 6000
# Don't listen on a TCP/IP port at all. This can be a security enhancement,
# if all processes that need to connect to mysqld run on the same Host.
# All interaction with mysqld must be made via Unix sockets or named pipes.
# Note that using this option without enabling named pipes on Windows
# (via the "enable-named-pipe" option) will render mysqld useless!
#
#skip-networking
# Replication Master Server (default)
# binary logging is required for replication
log-bin=mysql-bin
# binary logging format - mixed recommended
binlog_format=mixed
# required unique id between 1 and 2^32 - 1
# defaults to 1 if master-Host is not set
# but will not function as a master if omitted
server-id = 1
# Replication Slave (comment out master section to use this)
#
# To configure this Host as a replication slave, you can choose between
# two methods :
#
# 1) Use the CHANGE MASTER TO command (fully described in our manual) -
# the syntax is:
#
# CHANGE MASTER TO MASTER_Host=<Host>, MASTER_PORT=<port>,
# MASTER_USER=<user>, MASTER_PASSWORD=<password> ;
#
# where you replace <Host>, <user>, <password> by quoted strings and
# <port> by the master's port number (3306 by default).
#
# Example:
#
# CHANGE MASTER TO MASTER_Host='125.564.12.1', MASTER_PORT=3306,
# MASTER_USER='joe', MASTER_PASSWORD='secret';
#
# OR
#
# 2) Set the variables below. However, in case you choose this method, then
# start replication for the first time (even unsuccessfully, for example
# if you mistyped the password in master-password and the slave fails to
# connect), the slave will create a master.info file, and any later
# change in this file to the variables' values below will be ignored and
# overridden by the content of the master.info file, unless you shutdown
# the slave server, delete master.info and restart the slaver server.
# For that reason, you may want to leave the lines below untouched
# (commented) and instead use CHANGE MASTER TO (see above)
#
# required unique id between 2 and 2^32 - 1
# (and different from the master)
# defaults to 2 if master-Host is set
# but will not function as a slave if omitted
#server-id = 2
#
# The replication master for this slave - required
#master-Host = <hostname>
#
# The username the slave will use for authentication when connecting
# to the master - required
#master-user = <username>
#
# The password the slave will authenticate with when connecting to
# the master - required
#master-password = <password>
#
# The port the master is listening on.
# optional - defaults to 3306
#master-port = <port>
#
# binary logging - not required for slaves, but recommended
#log-bin=mysql-bin
# Point the following paths to different dedicated disks
#tmpdir = /tmp/
#log-update = /path-to-dedicated-directory/hostname
# Uncomment the following if you are using InnoDB tables
#innodb_data_home_dir = C:\mysql\data/
#innodb_data_file_path = ibdata1:10M:autoextend
#innodb_log_group_home_dir = C:\mysql\data/
# You can set .._buffer_pool_size up to 50 - 80 %
# of RAM but beware of setting memory usage too high
#innodb_buffer_pool_size = 16M
#innodb_additional_mem_pool_size = 2M
# Set .._log_file_size to 25 % of buffer pool size
#innodb_log_file_size = 5M
#innodb_log_buffer_size = 8M
#innodb_flush_log_at_trx_commit = 1
#innodb_lock_wait_timeout = 50
[mysqldump]
quick
max_allowed_packet = 512M
[mysql]
no-auto-rehash
# Remove the next comment character if you are not familiar with SQL
#safe-updates
[myisamchk]
key_buffer_size = 20M
sort_buffer_size = 20M
read_buffer = 2M
write_buffer = 2M
[mysqlhotcopy]
interactive-timeout
Je viens de constater que cette erreur se produisait car j'utilisais "windows power-Shell" au lieu de l'invite de commande :)) résolue !!!
Modifier 3 paramètres dans le fichier my.cnf
Sous [mysqld]
max_allowed_packet = 64M
wait_timeout = 6000
Sous [mysqldump]
max_allowed_packet = 64M
Cela devrait résoudre le problème
Cela signifie généralement que vous avez des "incompatibilités avec la version actuelle de MySQL Server", voir mysql_upgrade J'ai rencontré le même problème et je devais simplement exécuter:
mysql_upgrade --password
La documentation indique que "mysql_upgrade doit être exécuté à chaque mise à niveau de MySQL".
Sous [mysqld] j'ai essayé ce qui suit:
max_allowed_packet = 2096M
redémarré mysqld et cela n'a pas fonctionné, mais ce qui a fonctionné pour moi est de définir max_allowed_packet globalement à partir de la ligne de commande, puis d'exécuter l'exportation à partir de dump, le processus s'est déroulé sans aucun problème.
Vous pouvez commencer à partir d'une taille de paquet inférieure en fonction de la base de données. J'ai également réimporté ma base de données avec la même taille.
Pour l'export:-
mysqldump --opt --user=confluenceUser --password='<passwd>' --max_allowed_packet=2147483648 confluencedb | gzip > confluencedb.sql.gz
Pour importation: -
mysql> SET GLOBAL max_allowed_packet=2147483648;
Query OK, 0 rows affected, 1 warning (0.00 sec)
zcat confluence.sql.gz | mysql -uconfluence -p<passwd> confluencedb