zoukankan      html  css  js  c++  java
  • mysqldump导出报错"mysqldump: Error 2013: Lost connection to MySQL server during query when dumping table `file_storage` at row: 29"

    今天mysql备份的crontab自动运行的时候,出现了报警,报警内容如下

    mysqldump: Error 2013: Lost connection to MySQL server during query when dumping table `file_storage` at row: 29
    mysqldump: Couldn't execute 'show table status like 'property'': MySQL server has gone away (2006)
    mysqldump: Couldn't execute 'SET OPTION SQL_QUOTE_SHOW_CREATE=1': MySQL server has gone away (2006)
    mysqldump: Couldn't execute 'show fields from `property`': MySQL server has gone away (2006)
    mysqldump: Couldn't execute 'show table status like 'revision'': MySQL server has gone away (2006)
    mysqldump: Couldn't execute 'SET OPTION SQL_QUOTE_SHOW_CREATE=1': MySQL server has gone away (2006)
    mysqldump: Couldn't execute 'show fields from `revision`': MySQL server has gone away (2006)
    mysqldump: Couldn't execute 'show table status like 'revision\_change'': MySQL server has gone away (2006)
    mysqldump: Couldn't execute 'SET OPTION SQL_QUOTE_SHOW_CREATE=1': MySQL server has gone away (2006)
    mysqldump: Couldn't execute 'show fields from `revision_change`': MySQL server has gone away (2006)
    mysqldump: Couldn't execute 'show table status like 'setting'': MySQL server has gone away (2006)
    mysqldump: Couldn't execute 'SET OPTION SQL_QUOTE_SHOW_CREATE=1': MySQL server has gone away (2006)
    mysqldump: Couldn't execute 'show fields from `setting`': MySQL server has gone away (2006)
    mysqldump: Couldn't execute 'show table status like 'setting\_history'': MySQL server has gone away (2006)
    mysqldump: Couldn't execute 'SET OPTION SQL_QUOTE_SHOW_CREATE=1': MySQL server has gone away (2006)
    mysqldump: Couldn't execute 'show fields from `setting_history`': MySQL server has gone away (2006)
    mysqldump: Couldn't execute 'show table status like 'user'': MySQL server has gone away (2006)
    mysqldump: Couldn't execute 'SET OPTION SQL_QUOTE_SHOW_CREATE=1': MySQL server has gone away (2006)
    mysqldump: Couldn't execute 'show fields from `user`': MySQL server has gone away (2006)

     一开始我把故障的错误点定位在"mysqldump: Couldn't execute 'show fields from `revision`': MySQL server has gone away (2006)"这段报错上面,网上的部分建议是检查max_allowed_packet的值,然后改得尽量大一些,我查看当前的值信息如下:

    mysql> show global variables like 'max_allowed_packet';
    +--------------------+-----------+
    | Variable_name      | Value     |
    +--------------------+-----------+
    | max_allowed_packet | 268435456 | 
    +--------------------+-----------+
    1 row in set (0.00 sec)

     可以看到当前的值已经是200M了,说明应该不是这个问题导致的,而且查看报错,这里并没有从select获取大量数据,也没有insert或者update大量数据.

    我重新运行了一下脚本,过会儿又出现了相同的报错了.

    后来注意到有这么一段

    mysqldump: Error 2013: Lost connection to MySQL server during query when dumping table `file_storage` at row: 29

     在一篇文章里看到了针对这个报错的解决措施

    https://ottomatik.groovehq.com/knowledge_base/topics/solving-error-2013-lost-connection-to-mysql-server-during-query-when-dumping-table

    后来将timeout的值调大以后,就可以正常dump了

    mysql> show global variables like '%timeout%';
    +----------------------------+-------+
    | Variable_name              | Value |
    +----------------------------+-------+
    | connect_timeout            | 10    | 
    | delayed_insert_timeout     | 300   | 
    | innodb_lock_wait_timeout   | 100   | 
    | innodb_rollback_on_timeout | OFF   | 
    | interactive_timeout        | 28800 | 
    | net_read_timeout           | 30    | 
    | net_write_timeout          | 60    | 
    | slave_net_timeout          | 3600  | 
    | table_lock_wait_timeout    | 200   | 
    | wait_timeout               | 28800 | 
    +----------------------------+-------+
    10 rows in set (0.00 sec)
    
    mysql> set global net_read_timeout = 120; 
    Query OK, 0 rows affected (0.03 sec)
    
    mysql> set global net_write_timeout = 900;
    Query OK, 0 rows affected (0.00 sec)
    
    mysql> show global variables like '%timeout%';
    +----------------------------+-------+
    | Variable_name              | Value |
    +----------------------------+-------+
    | connect_timeout            | 10    | 
    | delayed_insert_timeout     | 300   | 
    | innodb_lock_wait_timeout   | 100   | 
    | innodb_rollback_on_timeout | OFF   | 
    | interactive_timeout        | 28800 | 
    | net_read_timeout           | 120   | 
    | net_write_timeout          | 900   | 
    | slave_net_timeout          | 3600  | 
    | table_lock_wait_timeout    | 200   | 
    | wait_timeout               | 28800 | 
    +----------------------------+-------+
    10 rows in set (0.00 sec)
  • 相关阅读:
    java web环境搭建
    java动手动脑异常处理
    java动手动脑多态
    python全栈开发day67--字段类型、字段属性、ORM回顾
    python全栈开发day66-视图系统、路由系统
    python全栈开发day65-templates:tags、母版和继承、组件、静态文件相关、simple_tag和inclusion_tag
    python全栈开发day64-模板-变量和(.)的使用,filters和自定义filter
    Django Models的数据类型汇总
    nginx反向代理uwsgi django服务器搭建总结
    Centos更新yum源
  • 原文地址:https://www.cnblogs.com/ilifeilong/p/7091979.html
Copyright © 2011-2022 走看看