#2006 - MySQL 服务器在恢复 mysql 转储时消失了 [重复]

Posted

技术标签:

【中文标题】#2006 - MySQL 服务器在恢复 mysql 转储时消失了 [重复]【英文标题】:#2006 - MySQL server has gone away when restoring mysql dump [duplicate] 【发布时间】:2013-10-27 04:38:54 【问题描述】:

环境:Windows 7 XAMPP 1.7.3

我已经为这个问题经历了许多 *** 解决方案并更改了文件中的设置

my.ini

现在看起来像

 # 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 @localstatedir@) 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]
#user       = your_username
#password   = your_password
host        = .
port        = 3306
socket      = "MySQL"

# Here follows entries for some specific programs

# The MySQL server
[mysqld]
basedir                 = "D:/Program Files/xampp/mysql/"
datadir                 = "D:/Program Files/xampp/mysql/data/"
port                    = 3306
socket                  = "MySQL"
skip-locking
key_buffer              = 16M
max_allowed_packet      = 254M
table_cache             = 64
sort_buffer_size        = 512K
net_buffer_length       = 8K
read_buffer_size        = 256K
read_rnd_buffer_size    = 512K
myisam_sort_buffer_size = 8M

default-time-zone       = "Asia/Calcutta"

log_error           = "D:/Program Files/xampp/mysql/data/mysql.err"
pid_file            = "mysql.pid"
general_log         = 0
general_log_file    = "D:/Program Files/xampp/mysql/data/mysql.log"
slow_query_log      = 0
slow_query_log_file = "D:/Program Files/xampp/mysql/data/mysql-slow.log"

# 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
enable-named-pipe

# Disable Federated by default
skip-federated

# 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           = "D:/Program Files/xampp/tmp/"
#log-update      = "D:/Program Files/xampp/tmp/mysql"

# Uncomment the following if you are using InnoDB tables
#skip-innodb
innodb_data_home_dir            = "D:/Program Files/xampp/mysql/data/"
innodb_data_file_path           = ibdata1:10M:autoextend
innodb_log_group_home_dir       = "D:/Program Files/xampp/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 = 254M

[mysql]
no-auto-rehash
# Remove the next comment character if you are not familiar with SQL
#safe-updates

[isamchk]
key_buffer = 20M
sort_buffer_size = 20M
read_buffer = 2M
write_buffer = 2M

[myisamchk]
key_buffer = 20M
sort_buffer_size = 20M
read_buffer = 2M
write_buffer = 2M

[mysqlhotcopy]
interactive-timeout

但我仍然遇到同样的错误。我正在尝试恢复具有许多 BLOB 内容的大小为 160MB 的 mysqldump。

【问题讨论】:

修改后是否重启了MySQL服务? 备份可能已损坏 【参考方案1】:

这里解释了如何解决这个问题http://eppand.com/solution-to-mysql-error-2006-in-xampp/

【讨论】:

我的设置为 10 亿:max_allowed_pa​​cket=1000000000,但我仍然收到错误消息。现在我要尝试 1 万亿:max_allowed_pa​​cket=1000000000000。【参考方案2】:

尝试在服务器中将max_allowed_packet 设置更改为更大的值。

打开位于 MySQL 安装文件夹中的“my.ini/cnf”,在[mysqld] 部分更改“max_allowed_packet = 64M”,不要忘记重新启动服务器。您可以通过执行来检查该值:

SHOW VARIABLES LIKE 'max_allowed_packet';

参考:http://dev.mysql.com/doc/refman/5.0/en/gone-away.html

【讨论】:

【参考方案3】:

如果有人需要,XAMPP 有未修改的配置文件:

https://drive.google.com/folderview?id=0B8SVZZwmcOIYNjdwbkluUTJERTA&usp=sharing

【讨论】:

以上是关于#2006 - MySQL 服务器在恢复 mysql 转储时消失了 [重复]的主要内容,如果未能解决你的问题,请参考以下文章

mysql 导入数据是报错:2006 - MySQL server has gone away

mysql恢复和数据导入的问题(ERROR 2006 (HY000) at line 1016: MySQL server has gone away)

SQLyog恢复数据库报错解决方法Error Code: 2006 - MySQL server has gone away

Mysql 导入导出,备份和恢复

MySQL · 引擎特性 · InnoDB 崩溃恢复过程

xtrabackup 备份和恢复