Error 2013 Lost Connection To Mysql Server
Contents |
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 error 2013 lost connection to mysql server during query when dumping table more about Stack Overflow the company Business Learn more about hiring developers or posting error 2013 lost connection to mysql server during query when dumping table at row ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack error 2013 lost connection to mysql server during query Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up Error Code: 2013. Lost connection to MySQL server during query up
Error 2013 Lost Connection To Mysql Server During Query Sql Statement
vote 67 down vote favorite 22 I got the Error Code: 2013. Lost connection to MySQL server during query error when I tried to add an index to a table using MySQL Workbench. I noticed also that it appears whenever I run long query. Is there away to increase the timeout value? mysql mysql-workbench share|improve this question edited Oct 6 at 8:06 agold 2,66571532 asked May 12 '12 2013 lost connection to mysql server at 'reading initial communication packet' system error 0 at 12:14 user836026 2,50054582 add a comment| 16 Answers 16 active oldest votes up vote 118 down vote accepted New versions of MySQL WorkBench have an option to change specific timeouts. For me it was under Edit → Preferences → SQL Editor → DBMS connection read time out (in seconds): 600 Changed the value to 6000. Also unchecked limit rows as putting a limit in every time I want to search the whole data set gets tiresome. share|improve this answer edited Oct 8 '12 at 22:53 Marko 8,109102653 answered Oct 8 '12 at 22:49 eric william nord 1,204273 1 Is it possible to increase this limit over 99,999 seconds? The DBMS connection read time out field only accept up to 5 figures, and setting the field to 0 is equivalent to the default parameter (600 seconds). (Windows 7 64-bit Ultimate, MySQL Workbench 5.2.47 CE) –Franck Dernoncourt Jun 1 '13 at 21:30 1 Following stackoverflow.com/q/16877574/395857, this issue is now solved (bugs.mysql.com/bug.php?id=69395) –Franck Dernoncourt Jun 18 '13 at 3:46 2 uncheck limit rows in in Edit → Preferences →SQL Queries –Jon Mar 2 '14 at 16:32 1 I tried this and it now shows Error 0 with no message when I right-click
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 lost connection to mysql server at 'reading initial communication packet' system error 110 ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join
Lost Connection To Mysql Server At 'reading Initial Communication Packet' System Error 104
the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes
Lost Connection To Mysql Server At 'reading Initial Communication Packet' System Error 113
a minute: Sign up Lost connection to MySQL server during query? [duplicate] up vote 28 down vote favorite 11 Possible Duplicate: Lost connection to MySQL server during query I am importing some data from a large csv to a mysql table. http://stackoverflow.com/questions/10563619/error-code-2013-lost-connection-to-mysql-server-during-query I am losing the connection to the server during the process of importing the file to the table. What is going wrong? The error code is 2013: Lost connection to the mySql server during the query. I am running these queries from a ubuntu machine remotely on a windows server. mysql share|improve this question edited Apr 10 '14 at 20:57 lImbus 1,28231125 asked Jun 29 '11 at 7:09 Shyam Natraj Kanagasabapathy 6754923 marked as duplicate by Martin Geisler, Jocelyn, the Tin Man, http://stackoverflow.com/questions/6516943/lost-connection-to-mysql-server-during-query CodingWithSpike, JYelton Nov 29 '12 at 0:52 This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question. add a comment| 6 Answers 6 active oldest votes up vote 22 down vote Try the following 2 things... 1) Add this to your my.cnf / my.ini in the [mysqld] section max_allowed_packet=32M (you might have to set this value higher based on your existing database). 2) If the import still does not work, try it like this as well... mysql -u 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 http://stackoverflow.com/questions/33336220/2013-lost-connection-to-mysql-server-during-query-but-not-timeout-and-not-la Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up “2013 - Lost connection to MySQL lost connection server during query” but NOT TIMEOUT and NOT LARGE PACKET up vote 0 down vote favorite I'm getting this lost connection error, but all the help I can find on-line seems to be around either timeout or large packet problems. I'm pretty sure neither of those apply in my case because it is failing instantly (sub 1 second) so, that pretty well rules out a timeout problem. lost connection to And, it's failing on simple queries against a small sample data set, so I can't imagine how packet size would be a factor. Based on some of my playing around, it seems like it's some internal issue because sometimes if I drop and re-create a table or view that will get the error to go away (but not always). It does seem to be only certain tables in my model that are having this problem. How do I debug this problem? I can't figure out what is actually causing this. I'm running MySQL version 5.5.29 on my MacBook Pro (10.10.5) via MAMP (2.1.2). I'm hitting it via both PHP code also running locally, and also via the SequelPro tool (v1.1, build 4499). When I am able to identify the offending query in my PHP code it tends to also give the same error via SequelPro. The error I am getting is: SQLSTATE[HY000]: General error: 2013 Lost connection to MySQL server during query I checked out the error log and I see that mysqld is seg-faulting. 151031 10:07:05 [ERROR] Found index case_id_name whose column info does not match that of MySQL. 151031 10:07:05 [ERROR] Build InnoDB index t