目录
- 问题复现
- 原因分析
- 解决办法
- 问题小结
- 1) MySQL 服务宕了
- 2) mysql连接超时
- 3) mysql请求链接进程被主动kill
- 4) Your SQL statement was too large.
问题复现
今天在用Navicat 16.0.6导入.sql文件时,运行一半就报错了。错误如下:
[Err] 2006 - MySQL server has gone away
原因分析
sql文件运行出错,第一反应就是文件内容过大,后来发现是navicat软件默认限制了上传sql语句的大小,修改方法很简单。
解决办法
1、打开 工具--> 服务器监控-->mysql
如下图所示:
2、选择 变量 ,找到 max_allowed_packect ,修改它的值为 999999448 即可。
如下图所示:
问题小结
在导入sql脚本过程中出现2006错误的情况很多,以下收集几种情况作为参考:
1) MySQL 服务宕了
mysql> show global status like 'uptime';
+---------------+--------+
| Variable_name | Value |
+---------------+--------+
| Uptime | 125695 |
+---------------+--------+
1 row in set (0.00 sec)
2) mysql连接超时
mysql> show global variables like '%timeout';
+-----------------------------+----------+
| Variable_name | Value |
+-----------------------------+----------+
| connect_timeout | 10 |
| delayed_insert_timeout | 300 |
| have_statement_timeout | YES |
| innodb_flush_log_at_timeout | 1 |
| 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 |
| rpl_stop_slave_timeout | 31536000 |
| slave_net_timeout | 60 |
| wait_timeout | 28800 |
+-----------------------------+----------+
13 rows in set (0.01 sec)
wait_timeout 是28800秒,即mysql链接在无操作28800秒后被自动关闭
3) mysql请求链接进程被主动kill
mysql> show global status like 'com_kill';
+---------------+-------+
| Variable_name | Value |
+---------------+-------+
| Com_kill | 10 |
+---------------+-------+
1 row in set (0.00 sec)
4) Your SQL statement was too large.
mysql> show global variables like 'max_allowed_packet';
+--------------------+----------+
| Variable_name | Value |
+--------------------+----------+
| max_allowed_packet | 20971520 |
+--------------------+----------+
1 row in set (0.00 sec)