Mysqldump Error 2013 Lost Connection To Mysql
Contents |
log in tour help Tour Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads
Error 2013: Lost Connection To Mysql Server
with us Database Administrators Questions Tags Users Badges Unanswered Ask Question _ Database Administrators Stack Exchange mysqldump: got error: 2013: lost connection to mysql server during query when using lock tables is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. Join them; mysqldump net_write_timeout it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top mysqldump Error 2013 up vote 6 down vote favorite 2 I have
Mysqldump Connection Timeout
a database installed, that I would like to backup in mysql. The problem is mysqldump fails on exporting the 'maia_mail' table # mysqldump -u root -p maia > maia.sql mysqldump: Error 2013: Lost connection to MySQL server during query when dumping table `maia_mail` at row: 15 It runs for less than 30 seconds and gets error out as above. The total size of the DB is 1.3GB with the maia_mail table being 1.0GB In my.cnf I have these set: [mysqld] max_allowed_packet = 1300M [mysqldump]
Net_read_timeout Mysql
max_allowed_packet = 1300M Please advise or give some guidance on how to dump the database? mysql mysqldump share|improve this question edited Apr 15 '15 at 1:08 KASQLDBA 4,38011436 asked Apr 14 '15 at 19:17 garfink 3113 Do you have enough space on the hard drive? Try watching the space while the dump is being done. –Jehad Keriaki Apr 14 '15 at 19:41 @jehad Keriaki - 170GB free space. It's also the same whether I dump to machine db is on or remote –garfink Apr 14 '15 at 19:49 What type of data this table has.. do you think it has special characters that affects saving into text file? –Jehad Keriaki Apr 14 '15 at 19:55 copies of email so varchar data mainly –garfink Apr 14 '15 at 20:01 Restore max_allowed_packet to its default value max_allowed_packet=1048576 (Restart the server after that plz) –Jehad Keriaki Apr 14 '15 at 20:14 | show 7 more comments 3 Answers 3 active oldest votes up vote 4 down vote I could easily suggest changing InnoDB settings which might be a littel heavy-handed just to get a mysqldump to work. You may not like what I am about the suggest, but I believe it's your best (only) option. Here it goes: SUGGESTION #1 : Disable extended inserts The default setting for mysqldump would include clumping together hundreds or thousands of rows in a single INSERT. This is known as an extended INSERT. It is ca
2012 5:34 Reporter: wu mg mysql lost connection Email Updates: Status: Closed Impact on me: None
Mysqldump Skip Table
Category:MySQL Server: InnoDB storage engine Severity:S2 (Serious) Version:5.5.8-log MySQL Community Server (GPL) mysqldump quick OS:Microsoft Windows (win7) Assigned to: Tags: 2013, Lost connection, mysqldump View Add Comment Files Developer Edit Submission View Progress Log http://dba.stackexchange.com/questions/97846/mysqldump-error-2013 Contributions [13 Jun 2012 6:53] wu mg Description: Hi, when i backup database by using mysqldump tool, it report error 2013 mysqldump -uuser -ppwd dbname > d:/backup.sql mysqldump: Error 2013: Lost connection to MySQL server during query when dumping table `o_log_xxxxxxx` https://bugs.mysql.com/bug.php?id=65596 at row: 4600 error row is not fixed, sometimes change to another number such as 4544 i can execute query normal in the error table, such as "select * from o_log_xxxxxxx limit 10", and get correct result i search some reported bugs, and change max_allowed_packet from 10M to 500M, but get same result. is there any suggestion? mysql error log: 120613 14:26:12 InnoDB: Error: space id and page n:o stored in the page InnoDB: read in are 3130291633:962663424, should be 0:3282! InnoDB: Database page corruption on disk or a failed InnoDB: file read of page 3282. InnoDB: You may have to recover from a backup. 120613 14:26:12 InnoDB: Page dump in ascii and hex (16384 bytes): len 16384; hex 47494638396114001400d53f00b98721fde56a966712fedd5afce58fffe354fed536ba9475b19cd8fef7d8fffffeffdd44946aab8f5877fbcc33a976166b31a3ffe65bfcb42cfebb1bffdb47fdb513ffe04effe349ffcb2cfeefa0fdb44bfaab39fdf1c5e6bf40ffbe12d1a952895a0cdab53cd09017f4d24bfed443fed44edfc792ead4a5faa822fcbd51fcebb5e8d8cbffe2407d55baeee8e279500bfdce5cfefdf19c7530fde436da9b37f9f4eaf3f1fbf6fdfff99b3fd8c7afe3a940e5b12dfbdf7df7b91fd4b367ffffff21f9040100003f002c00000000140014000006e0c09f70482c1a8b8b8b7279245a16148bd4b2b4349f9d88b6300a7528136bd1d2793d02016d08243018c2484b20a3caa4030402ef3d4166140a310a190b198281307042491c0a36082d07333e0c08801c1e15430b168d2b10a01f0da0370a09999b05042a040c100d061fa02b1c3ca88b050552142c0e3b0e0e181b1b12139a8b16b9115c02cd023429291a12c73f0b24251103253a0735260f0f1ae3156242181411251b2780350002381b15d5421618182428ed0a2e320f28e8991b720f438f0f26721c102042e0150c1344086003c061937318003ca057efa2c78f207f0401003b00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
Sep 2009 12:08 Reporter: John Miller Email Updates: Status: Verified Impact on me: https://bugs.mysql.com/bug.php?id=46103 None Category:MySQL Server: mysqldump Command-line Client Severity:S4 (Feature request) http://forums.mysql.com/read.php?28,641205,641205 Version:5.1.34-community via TCP/IP OS:Microsoft Windows (2k3 SP2) Assigned to: Triage: Needs Triage: D2 (Serious) View Add Comment Files Developer Edit Submission View Progress Log Contributions [9 Jul 2009 22:47] John Miller Description: This command gets run as part lost connection of our backup: D:\util\mantis_backup_test>mysqldump -q -e --max_allowed_packet=500m --net_buffer_length=16m -u XXXX -pXXXXXXXXX rpcbugtracker 1>test.backup mysqldump: Error 2013: Lost connection to MySQL server during query when dumping table `mantis_bug_file_table` at row: 743 Row 743 does not seem "special": mysql> select id, length(content), bug_id,filename from mantis_bug_file_table where id=743; +-----+-----------------+--------+-------------+ | id lost connection to | length(content) | bug_id | filename | +-----+-----------------+--------+-------------+ | 743 | 76288 | 2313 | P0130rs.doc | +-----+-----------------+--------+-------------+ 1 row in set (0.00 sec) If I go into my application (mantis) and remove that attachment - removing that row from the table: mysql> select id, length(content), bug_id,filename from mantis_bug_file_table where id=743; Empty set (0.00 sec) I just get the same error with a different row: mysqldump: Error 2013: Lost connection to MySQL server during query when dumping table `mantis_bug_file_table` at row: 429 The table itself is big: D:\Program Files\MySQL\MySQL Server 5.0\data\rpcbugtracker>dir /os Volume in drive D is Applications Volume Serial Number is 1099-7FDC Directory of D:\Program Files\MySQL\MySQL Server 5.0\data\rpcbugtracker 01/21/2009 05:03 AM
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 mysqldump: Error 2013: Lost connection to MySQL server during query when dumping table 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 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 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 following cmd and cross c