Error 2013 Mysql Dump
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 mysqldump error 2013 lost connection to mysql server of this site About Us Learn more about Stack Overflow the company
Mysqldump Error 2013 Lost Connection To Mysql Server During Query
Business Learn more about hiring developers or posting ads with us Database Administrators Questions Tags Users Badges Unanswered Ask mysqldump: got error: 2013: lost connection to mysql server during query when using lock tables Question _ Database Administrators Stack Exchange 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 a database installed, that I would like to backup in mysql. The problem is mysqldump fails on exporting the 'maia_mail' table
Mysqldump Connection Timeout
# 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] 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,34511436 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 co
2014 20:41 Reporter: - - Email Updates: Status: No Feedback Impact on me: None Category:MySQL Server: InnoDB net_read_timeout mysql storage engine Severity:S3 (Non-critical) Version:5.5.37 OS:Linux (Ubuntu 14.04) Assigned to: View mysql lost connection Add Comment Files Developer Edit Submission View Progress Log Contributions [3 May 2014 3:09] - -
Mysqldump Quick
Description: I tried to backup my database with the mysqldump command. But it failed with an error message, "mysqldump: Error 2013: Lost connection to MySQL server during http://dba.stackexchange.com/questions/97846/mysqldump-error-2013 query when dumping table `creation_log` at row: 59655". The log of mysqldump was: ======================================== nodchip@nighthawk ~ % mysqldump -uroot -p[password] -A -v --flush-privileges --rou tines --result-file mysql_backup_2014-05-03.sql (skipped) -- Retrieving table structure for table creation_log... -- Sending SELECT query... -- Retrieving rows... mysqldump: Error 2013: Lost connection to MySQL server during query when https://bugs.mysql.com/bug.php?id=72519 dumping table `creation_log` at row: 59655 ======================================== I added "innodb_force_recovery = 6" to [mysqld] section in my.cnf, restart the mysqld and tried mysqldump again. But the result was not changed. The definition of "creation_log" table is: ======================================== mysql> desc creation_log; +------------+------------------+------+-----+-------------------+-----------------------------+ | Field | Type | Null | Key | Default | Extra | +------------+------------------+------+-----+-------------------+-----------------------------+ | PROBLEM_ID | int(10) unsigned | NO | MUL | NULL | | | USER_CODE | int(10) unsigned | NO | | NULL | | | DATE | timestamp | NO | MUL | CURRENT_TIMESTAMP | on update CURRENT_TIMESTAMP | | MACHINE_IP | text | NO | MUL | NULL | | | SUMMARY | text | YES | | NULL | | +------------+------------------+------+-----+-------------------+-----------------------------+ ======================================== I tried "ALTER TABLE
Sep 2009 12:08 Reporter: John Miller Email Updates: Status: Verified Impact https://bugs.mysql.com/bug.php?id=46103 on me: None Category:MySQL Server: mysqldump Command-line Client Severity:S4 http://serverfault.com/questions/470207/mysql-lost-connection-error-on-mysqldump (Feature request) 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 lost connection run as part 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 lost connection to where id=743; +-----+-----------------+--------+-------------+ | id | 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
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 with us Server Fault Questions Tags Users Badges Unanswered Ask Question _ Server Fault is a question and answer site for system and network administrators. Join them; 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 MySQL lost connection error on mysqldump up vote 5 down vote favorite I have a 1 TB MySQL database that I'd like to dump and reload. Most of the data is in one table. A lot of data has been deleted, so I'm pretty sure if I dump it with mysql, rebuild the database, then reload it the total size will be smaller. I'm dumping the data with this command: mysqldump -uroot -pXXX mydb | gzip -c > data.sql.gz I get this error mysqldump: Error 2013: Lost connection to MySQL server during query when dumping table `MY_TABLE` at row: 596089342 I've tried many variations, including increasing the packet size, doing single translation and going over TCP/IP instead of local socket. mysqldump -uroot -pXXX -h 127.0.0.1 --max-allowed-packet=1024M --single-transaction mydb | gzip -c > data.sql.gz Finally, I even ran the command going to /dev/null to make sure it wasn't gzip. All permutations produce the same error. mysqldump -uroot -pXXX -h 127.0.0.1 mydb > /dev/null Here's some of the settings in my.cnf max_allowed_packet = 1G interactive_timeout = 600 wait_timeout = 600 net_read_timeout=600 net_write_timeout=600 connect_timeout=600 One other odd thing is that the dump always stops on the same place. Approximately 6GB of gzipped data and at approximately the same record. When I do ls -l the file size is always identical. I'm stumped. Any suggestions for next steps? For the record, this is Mysql 5.1.58 running on Ubuntu 11.10 WILL mysql share|improve this question asked Jan 18 '13 at 0:57 Will Glass 5572818 Try: restoring interactive_timeout and wait_timeout to their default values, or using a named pipe. –Michael Hampton♦ Jan 18 '13 at 1:05 Are there any errors in the server log? Did you try a dump via phpmyadmin? –Jure1873 Jan 19 '13 at 20:56 This is a linux server. What is a pipe? (isn't that Windows only). –Will Glass Jan 21 '13 at 16:00 no errors in the log. –Will Glass Jan 21 '13 at 16:01 I tried again after restoring interactive_timeout and wait