#2006 - MySQL server has gone away 问题解决方法 （全） （转）

#2006 - MySQL server has gone away 问题解决方法

原文地址：http://www.cnblogs.com/bisonjob/archive/2009/08/18/1548611.html

一、应用程序（好比PHP）长时间的执行批量的MYSQL语句。
最多见的就是采集或者新旧数据转化。

解决方案：

在my.ini文件中添加或者修改如下两个变量：
wait_timeout=2880000
interactive_timeout = 2880000

关于两个变量的具体说明能够google或者看官方手册。
若是不能修改my.cnf，则能够在链接数据库的时候设置CLIENT_INTERACTIVE，好比：
sql = "set interactive_timeout=24*3600";
mysql_real_query(...)

二、执行一个SQL，但SQL语句过大或者语句中含有BLOB或者longblob字段。
好比，图片数据的处理
解决方案

在my.cnf文件中添加或者修改如下变量：
max_allowed_packet = 10M  (也能够设置本身须要的大小)

max_allowed_packet 参数的做用是，用来控制其通讯缓冲区的最大长度。

－－－－－－－－－－－－ 如下是网络搜索的资料 －－－－－－－－－－－－－－－－－－－

也许其余人遇到这个问题，不必定是这儿的缘由，那么，就把我在网上找到比较全面的分析放到下面：
有两篇，第一篇比较直观，第二篇比较深奥。
解决MySQL server has gone away 2009-01-09 16:23:22
来自：http://www.webjx.com/database/mysql-8817.html
今天遇到相似的情景，MySQL只是冷冷的说：MySQL server has gone away。
大概浏览了一下，主要多是由于如下几种缘由：
一种多是发送的SQL语句太长，以至超过了max_allowed_packet的大小，若是是这种缘由，你只要修改my.cnf，加大max_allowed_packet的值便可。
还有一种多是由于某些缘由致使超时，好比说程序中获取数据库链接时采用了Singleton的作法，虽然屡次链接数据库，但其实使用的都是同一个链接， 并且程序中某两次操做数据库的间隔时间超过了wait_timeout（SHOW STATUS能看到此设置），那么就可能出现问题。最简单的处理方式就是把wait_timeout改大，固然你也能够在程序里时不时顺手 mysql_ping()一下，这样MySQL就知道它不是一我的在战斗。
解决MySQL server has gone away

一、应用程序（好比PHP）长时间的执行批量的MYSQL语句。最多见的就是采集或者新旧数据转化。

解决方案：

在my.cnf文件中添加或者修改如下两个变量：

wait_timeout=2880000
interactive_timeout = 2880000　　
关于两个变量的具体说明能够google或者看官方手册。若是不能修改my.cnf，则能够在链接数据库的时候设置CLIENT_INTERACTIVE，好比：

sql = "set interactive_timeout=24*3600";
mysql_real_query(...)

二、执行一个SQL，但SQL语句过大或者语句中含有BLOB或者longblob字段。好比，图片数据的处理

解决方案：

在my.cnf文件中添加或者修改如下变量：

max_allowed_packet = 10M
(也能够设置本身须要的大小)

max_allowed_packet
参数的做用是，用来控制其通讯缓冲区的最大长度

MySQL: 诡异的MySQL server has gone away及其解决
来自：http://fz9493.blog.sohu.com/38472203.html

jimmy | 15 三月, 2007 20:32

在Mysql执行show status，一般更关注缓存效果、进程数等，每每忽略了两个值：

Variable_name Value 
Aborted_clients 3792 
Aborted_connects 376


一般只占query的0.0x%，因此并不为人所重视。并且在传统Web应用上，query错误对用户而言影响并不大，只是从新刷新一下页面就OK了。最近的基础改造中，把不少应用做为service运行，没法提示用户从新刷新，这种状况下，可能就会影响到服务的品质。

经过程序脚本的日志跟踪，主要报错信息为“MySQL server has gone away”。官方的解释是：

The most common reason for the MySQL server has gone away error is that the server timed out and closed the connection.

Some other common reasons for the MySQL server has gone away error are:

You (or the db administrator) has killed the running thread with a KILL statement or a mysqladmin kill command.

You tried to run a query after closing the connection to the server. This indicates a logic error in the application that should be corrected.

A client application running on a different host does not have the necessary privileges to connect to the MySQL server from that host.

You got a timeout from the TCP/IP connection on the client side. This may happen if you have been using the commands: mysql_options(..., MYSQL_OPT_READ_TIMEOUT,...) or mysql_options(..., MYSQL_OPT_WRITE_TIMEOUT,...). In this case increasing the timeout may help solve the problem.

You have encountered a timeout on the server side and the automatic reconnection in the client is disabled (the reconnect flag in the MYSQL structure is equal to 0).

You are using a Windows client and the server had dropped the connection (probably because wait_timeout expired) before the command was issued.

The problem on Windows is that in some cases MySQL doesn't get an error from the OS when writing to the TCP/IP connection to the server, but instead gets the error when trying to read the answer from the connection.

In this case, even if the reconnect flag in the MYSQL structure is equal to 1, MySQL does not automatically reconnect and re-issue the query as it doesn't know if the server did get the original query or not.

The solution to this is to either do a mysql_ping on the connection if there has been a long time since the last query (this is what MyODBC does) or set wait_timeout on the mysqld server so high that it in practice never times out.

You can also get these errors if you send a query to the server that is incorrect or too large. If mysqld receives a packet that is too large or out of order, it assumes that something has gone wrong with the client and closes the connection. If you need big queries (for example, if you are working with big BLOB columns), you can increase the query limit by setting the server's max_allowed_packet variable, which has a default value of 1MB. You may also need to increase the maximum packet size on the client end. More information on setting the packet size is given in Section A.1.2.9, “Packet too large”.

An INSERT or REPLACE statement that inserts a great many rows can also cause these sorts of errors. Either one of these statements sends a single request to the server irrespective of the number of rows to be inserted; thus, you can often avoid the error by reducing the number of rows sent per INSERT or REPLACE.

You also get a lost connection if you are sending a packet 16MB or larger if your client is older than 4.0.8 and your server is 4.0.8 and above, or the other way around.

It is also possible to see this error if hostname lookups fail (for example, if the DNS server on which your server or network relies goes down). This is because MySQL is dependent on the host system for name resolution, but has no way of knowing whether it is working — from MySQL's point of view the problem is indistinguishable from any other network timeout.

You may also see the MySQL server has gone away error if MySQL is started with the --skip-networking option.

Another networking issue that can cause this error occurs if the MySQL port (default 3306) is blocked by your firewall, thus preventing any connections at all to the MySQL server.

You can also encounter this error with applications that fork child processes, all of which try to use the same connection to the MySQL server. This can be avoided by using a separate connection for each child process.

You have encountered a bug where the server died while executing the query.



据此分析，可能缘由有3：

1，Mysql服务端与客户端版本不匹配。

2，Mysql服务端配置有缺陷或者优化不足

3，须要改进程序脚本

经过更换多个服务端与客户端版本，发现只能部分减小报错，并不能彻底解决。排除1。

对服务端进行了完全的优化，也未能达到理想效果。在timeout的取值设置上，从经验值的10，到PHP默认的60，进行了屡次尝试。而Mysql官方默认值(8小时)明显是不可能的。从而对2也进行了排除。(更多优化的经验分享，将在之后整理提供)

针对3对程序代码进行分析，发现程序中大量应用了相似以下的代码(为便于理解，用原始api描述)：

$conn=mysql_connect( ... ... );

... ... ... ...

if(!$conn){ //reconnect

$conn=mysql_connect( ... ... );

}

mysql_query($sql, $conn);

这段代码的含义，与Mysql官方建议的方法思路相符[ If you have a script, you just have to issue the query again for the client to do an automatic reconnection. ]。在实际分析中发现，if(!$conn)并非可靠的，程序经过了if(!$conn)的检验后，仍然会返回上述错误。

对程序进行了改写：

if(!conn){ // connect ...}

elseif(!mysql_ping($conn)){ // reconnect ... }

mysql_query($sql, $conn);

经实际观测，MySQL server has gone away的报错基本解决。

BTW： 附带一个关于 reconnect 的疑问，

在php4x+client3x+mysql4x的旧环境下，reconnet的代码：

$conn=mysql_connect(...) 能够正常工做。

可是，在php5x+client4x+mysql4x的新环境下，$conn=mysql_connect(...)返回的$conn有部分状况下不可用。须要书写为：

mysql_close($conn);

$conn=mysql_connect(...);

返回的$conn才能够正常使用。缘由未明。未作深刻研究，也未见相关讨论。或许mysql官方的BUG汇报中会有吧。

～～呵呵～～


本文来自CSDN博客，转载请标明出处：http://blog.csdn.net/brightsnow/archive/2009/03/17/3997705.aspx


description: 
remember that your MySQL "max_allowed_packet" configuration setting (default 1MB) 
mysql 默认最大可以处理的是1MB 
若是你在sql使用了大的text或者BLOB数据，就会出现这个问题。 php手册上的注释 

When trying to INSERT or UPDATE and trying to put a large amount of text or data (blob) into a mysql table you might run into problems. 
In mysql.err you might see: 
Packet too large (73904) 
To fix you just have to start up mysql with the option -O max_allowed_packet=maxsize 
You would just replace maxsize with the max size you want to insert, the default is 65536 


mysql手册上说 

Both the client and the server have their own max_allowed_packet variable, so if you want to handle big packets, you must increase this variable both in the client and in the server. 

If you are using the mysql client program, its default max_allowed_packet variable is 16MB. To set a larger value, start mysql like this: 

shell> mysql --max_allowed_packet=32M That sets the packet size to 32MB. 

The server's default max_allowed_packet value is 1MB. You can increase this if the server needs to handle big queries (for example, if you are working with big BLOB columns). For example, to set the variable to 16MB, start the server like this: 

shell> mysqld --max_allowed_packet=16M You can also use an option file to set max_allowed_packet. For example, to set the size for the server to 16MB, add the following lines in an option file: 

[mysqld]max_allowed_packet=16M 

使用mysql作数据库还原的时候，因为有些数据很大，会出现这样的错误：The MySQL Server returned this Error:MySQL Error Nr.2006-MySQL server has gone away。个人一个150mb的备份还原的时候就出现了这错误。解决的方法就是找到mysql安装目录，找到my.ini文件，在文件的最后添 加：max_allowed_packet = 10M(也能够设置本身须要的大小)。 max_allowed_packet 参数的做用是，用来控制其通讯缓冲区的最大长度。