1、修改mysqld的配置文件my.cnf
调整max_allowed_packet的值,修改为5M就比较合适了。
[mysqld]
port = 3308
socket = /dev/shm/mysqld.sock
skip-external-locking
key_buffer_size = 16M
max_allowed_packet = 10M
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
2、修改[mysqld]中的值
[mysqldump]
quick
max_allowed_packet = 10M
如果以上办法不能解决,或者没有my.cnf或my.ini,推荐用以下办法解决:
1、你的MySQL服务器真的消失了。
通过查看服务器正常运行时间和服务器错误日志,我们可以轻松地检查这一点。
$ mysql -uroot -p -e "show global status like 'uptime';"
+---------------+-------+
| Variable_name | Value |
+---------------+-------+
| Uptime | 68928 |
+---------------+-------+
1 row in set (0.04 sec)
$ tail /var/log/mysql/error.log
130101 22:22:30 InnoDB: Initializing buffer pool, size = 256.0M
130101 22:22:30 InnoDB: Completed initialization of buffer pool
130101 22:22:30 InnoDB: highest supported file format is Barracuda.
130101 22:22:30 InnoDB: 1.1.8 started; log sequence number 63444325509
130101 22:22:30 [Note] Server hostname (bind-address): '127.0.0.1'; port: 3306
130101 22:22:30 [Note] - '127.0.0.1' resolves to '127.0.0.1';
130101 22:22:30 [Note] Server socket created on IP: '127.0.0.1'.
130101 22:22:30 [Note] Event Scheduler: Loaded 0 events
130101 22:22:30 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.5.28-cll' socket: '/var/lib/mysql/mysql.sock' port: 3306 MySQL Community Server (GPL)
在这两种情况下,服务器已经启动了一段时间,并且没有任何错误消息来表示问题。
如果MySQL服务器确实消失了,是关机还是崩溃?MySQL错误日志将提供答案。通常,mysqld守护进程(Mysqld)将由mysqld_security包装进程重新启动。
2、连接超时
$ mysql -uroot -p -e "show global variables like '%timeout';"
+----------------------------+----------+
| Variable_name | Value |
+----------------------------+----------+
| connect_timeout | 30 |
| delayed_insert_timeout | 300 |
| innodb_lock_wait_timeout | 50 |
| innodb_rollback_on_timeout | OFF |
| interactive_timeout | 28800 |
| lock_wait_timeout | 31536000 |
| net_read_timeout | 30 |
| net_write_timeout | 60 |
| slave_net_timeout | 3600 |
| wait_timeout | 28800 |
+----------------------------+----------+
这些值是相对合理的MySQL缺省值。但是,如果超时时间很短,则可能会出现此错误。
这里只是一个例子。
mysql> SET SESSION wait_timeout=5;
## Wait 10 seconds
mysql> SELECT NOW();
ERROR 2006 (HY000): MySQL server has gone away
No connection. Trying to reconnect...
Connection id: 132361
Current database: *** NONE ***
+---------------------+
| NOW() |
+---------------------+
| 2013-01-02 11:31:15 |
+---------------------+
1 row in set (0.00 sec)
3、您的sql语句被干掉了。
有些系统会主动终止运行时间过长的SQL语句。
您可以很容易地通过查看已经执行了多少个杀死语句来检查这种情况是否可能发生。
$ mysql -uroot -p -e "show global status like 'com_kill'"
+---------------+-------+
| Variable_name | Value |
+---------------+-------+
| Com_kill | 0 |
+---------------+-------+
Not killed this time.
4、您的sql语句太大了
测试和验证有点困难,但是MySQL使用最大的数据包站点在服务器和客户端之间进行通信。如果这包括大字段(例如BLOB列),您可能会因为大小而终止SQL语句。
默认情况下,这是相对较小的。
mysql> show global variables like 'max_allowed_packet';
+--------------------+---------+
| Variable_name | Value |
+--------------------+---------+
| max_allowed_packet | 1048576 |
+--------------------+---------+
1 row in set (0.00 sec)
例如,可以增加到16M,包括:
mysql -u root -p //注意先登录
mysql> set global max_allowed_packet=1024*1024*16;
mysql> show global variables like 'max_allowed_packet';
+--------------------+----------+
| Variable_name | Value |
+--------------------+----------+
| max_allowed_packet | 16777216 |
+--------------------+----------+
1 row in set (0.00 sec)
好消息是,这是今天客户的原因,现在不再有错误了!
确保在MySQL重新启动时保留此值。
#my.cnf
[mysqld]
max_allowed_packet = 16M