Error 2013 Lost Connection To Mysql Server During Query Mysqldump
Contents |
to: mysqldump: Error 2013: Lost connection to MySQL
Mysqldump Error 2013 Lost Connection To Mysql Server During Query When Dumping Table At Row
server during query when dumping table ....If so there error 2013 lost connection to mysql server during query sql statement are several options you can try to resolve: 1) it is possible that the general error 2013 lost connection to mysql server during query backup is hitting the MySQL timeout limits. The particular variables in question here are net_read_timeout and net_write_timeout which are set to 30
Error 2013 (hy000): Lost Connection To Mysql Server During Query
and 60 seconds respectivley. You can change these in the my.cnf config file by setting them as you desire. Here is an example. After making these changes to my.cnf you must restart MySQL net_read_timeout = 120 net_write_timeout = 900 If you prefer to change these settings
Error Code 2013 Lost Connection To Mysql Server During Query
without needing to reboot MySQL you can do that with the following SQL statements: set global net_read_timeout = 120; set global net_write_timeout = 900; Again, use the value for these settings that you feel is appropriate for your setup. 2) Increase max_allowed_packet setting You might try increasing the max_allowed_packet configuration setting. You could try setting it to 256M or even up to 1G 3) You could have a corrupt table Sometimes "Lost connection" errors are caused by a corrupt table. You could try setting innodb_force_recovery = 1 and restart mysql to see if that helps. If it does, doing the dump might fix the page cache in which you can often turn this back to 0 or remove. Was this article helpful? Yes / No, I want to contact support Powered by Groove
Oct 2011 22:02 Reporter: Guy Baconniere Email Updates: Status: No Feedback Impact on me: None Category:MySQL Server: Command-line Clients Severity:S2 error 2013 (hy000) lost connection to mysql server during query innodb (Serious) Version:4.1.11,5.1.34 OS:Linux Assigned to: Tags: big table, compatible mysql40, dump table,
2013 Lost Connection To Mysql Server During Query Phpmyadmin
ERROR 2013, Latin1, Lost connection, mysqldump, rt ticket, utf8 Triage: Needs Triage: D3 (Medium) View Add Comment mysqldump: got error: 2013: lost connection to mysql server during query when using lock tables Files Developer Edit Submission View Progress Log Contributions [19 May 2009 13:19] Guy Baconniere Description: We use a latin1 InnoDB table to store email attachments. This table contains https://ottomatik.groovehq.com/knowledge_base/topics/solving-error-2013-lost-connection-to-mysql-server-during-query-when-dumping-table 1.5 mio rows for 18 GB of data. We can only dump it successfully when we use the mysqldump default options (--opt etc) but we cannot dump it when using --default-character-set=latin1 or --compatible=mysql40. We tried to increase --max-allowed-packet up to 1G on both server and client side and use --quick but we got always the same https://bugs.mysql.com/bug.php?id=44953 error after a random period of time : <> <> ... We need to dump it using latin1 or mysql40 compatiblity (latin1) otherwise all utf8 characters stored in latin1 are lost. This seems related to another bugs : http://bugs.mysql.com/bug.php?id=11612 http://bugs.mysql.com/bug.php?id=26557 http://bugs.mysql.com/bug.php?id=30162 N.B. Some attachments contains utf8 characters but the current version of the application (RT 3.4.CHALDEA) was designed to run on MySQL 4.0 and it cannot handle table in utf8 in the version we are running. We know MySQL 4.1.11 is quite old but we need to be able to dump it to move to the last release of MySQL 5.0 on 64-bit OS with splitted tablespace InnoDB etc. How to repeat: 1) Install mysql 4.1.11 2) CREATE TABLE `Attachments` ( `id` int(11) NOT NULL auto_increment, `TransactionId` int(11) NOT NULL default '0', `Parent` int(11)
Community Podcasts MySQL.com Downloads Documentation Section Menu: MySQL Forums :: Backup :: mysqldump: Error 2013: Lost connection to MySQL server during query when dumping table New Topic Advanced Search http://forums.mysql.com/read.php?28,641205,641205 mysqldump: Error 2013: Lost connection to MySQL server during query when dumping table https://bugs.mysql.com/bug.php?id=30809 Posted by: B P () Date: January 07, 2016 05:02AM Hello, I have the following problem to backup / dump a large table on my Database : test01 ~ # mysqldump -u root -p -v MyDB > test.sql Enter password: -- Connecting to localhost... -- Retrieving table structure for table lost connection MyTable0... -- Sending SELECT query... -- Retrieving rows... -- Retrieving table structure for table MyTable1... -- Sending SELECT query... -- Retrieving rows... mysqldump: Error 2013: Lost connection to MySQL server during query when dumping table `MyTable1` at row: 18132197 As I tried the following things to try to fix this issue - Increase the net_write_time / net_read_time value : mysql> SET GLOBAL lost connection to net_write_timeout=3600; Query OK, 0 rows affected (0.00 sec) mysql> SET GLOBAL net_read_timeout=3600; Query OK, 0 rows affected (0.00 sec) I have also tried to dump my DB with the following mysqldump parameters : - mysqldump -u root -p MyDB | gzip -c > MyDB.sql.gz - mysqldump -u root -p MyDB > MyDB.sql - mysqldump -u root -p -q --single-transaction -v MyDB > MyDB.sql - mysqldump -u root -p --max_allowed_packet=500m --net_buffer_length=16m -q --single-transaction -v MyDB > MyDB.sql - mysqldump -u root -p --max_allowed_packet=2147483648 --net_buffer_length=16777216 -v MyDB > MyDB.sql - mysqldump -u root -p --max_allowed_packet=2147483648 --net_buffer_length=16777216 -q --single-transaction -v MyDB > MyDB.sql Note I add the following lines to my.cfg : wait_timeoued_timeout=28800 interactive_timeout = 28800 net_read_timeout =3600 net_write_timeout =3600 But only the parameter interactive_timeout seems modified : test01 ~ # mysqladmin -u root -p variables | grep _timeout Enter password: | connect_timeout | 10 | 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 So I started manually mysqld using the f
Email Updates: Status: No Feedback Impact on me: None Category:MySQL Server Severity:S3 (Non-critical) Version:5.1.20 OS:Linux Assigned to: View Add Comment Files Developer Edit Submission View Progress Log Contributions [4 Sep 2007 20:38] aiton goldman Description: While running mysqldump, I get the following error intermitently : Error 2013: Lost connection to MySQL server during query when dumping table.... It doesn't happen consistently on any one table (when I have gotten the error, it has been on tables that range in size from 1gig to 5gigs), nor does it happen on any specific row. I have set the interactive_timeout setting to a ridiculously high number (172800), and I have increased the max_allowed_packet setting to 30M, but the lost connections still occur. Even with --log-warnings set to 2, I don't see anything about the lost connections reported in the server error log. How to repeat: The full command I use : mysqldump -S /tmp/mysql.sock --single-transaction -C -q --allow-keywords --hex-blob --quote-names -u backup -p