Re: ERROR 2013 (HY000): Lost connection to MySQL server during query
2014/1/7 h...@tbbs.net 2014/01/06 17:07 +0100, Reindl Harald what about look in the servers logfiles most likely max_allowed_packet laughable low Is this then, too, likly when the server and the client are the same machine? I left this out, that it only then happens when the client has been idle, and right afterwards the client repeats the request and all goes well. The message is no more than an irritatind break between request and fulfillment. Hello, That happens when you're trying to re-use an existing connection which wasn't properly closed and as you said, it's been idle. When you repeat the operation, the thread is created again and thus everything goes normal. Review the following variables wait_timeout net_write_timeout net_read_timeout Manu
Re: ERROR 2013 (HY000): Lost connection to MySQL server during query
2014/01/06 17:07 +0100, Reindl Harald what about look in the servers logfiles most likely max_allowed_packet laughable low Is this then, too, likly when the server and the client are the same machine? I left this out, that it only then happens when the client has been idle, and right afterwards the client repeats the request and all goes well. The message is no more than an irritatind break between request and fulfillment. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
ERROR 2013 (HY000): Lost connection to MySQL server during query
Now that I installed 5.6.14 on our Vista machine, when using mysql I often see that error-message, which under 5.5.8 I never saw. What is going on? -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
Re: ERROR 2013 (HY000): Lost connection to MySQL server during query
Am 06.01.2014 15:36, schrieb h...@tbbs.net: Now that I installed 5.6.14 on our Vista machine, when using mysql I often see that error-message, which under 5.5.8 I never saw. What is going on? what about look in the servers logfiles most likely max_allowed_packet laughable low signature.asc Description: OpenPGP digital signature
Re: ERROR 2013 (HY000): Lost connection to MySQL server during query
If you did not work directly on mysql server (login by mysql command), please try this. Using script (PHP, ...) may lose connection, as my experience. Best --- On Mon, 3/5/12, Singer X.J. Wang w...@singerwang.com wrote: From: Singer X.J. Wang w...@singerwang.com Subject: Re: ERROR 2013 (HY000): Lost connection to MySQL server during query To: javad bakhshi javadbakh...@yahoo.com Cc: mysql@lists.mysql.com mysql@lists.mysql.com Date: Monday, March 5, 2012, 10:40 PM Checking your firewall settings.. S On Mon, Mar 5, 2012 at 08:39, javad bakhshi javadbakh...@yahoo.com wrote: Hi, Still have the same problem and changing connect_timeout didn't help. Any other Ideas? Is there even any solution to this? Best regards, Javad Bakhshi, From: mail...@securitylabs.it mail...@securitylabs.it To: mysql@lists.mysql.com Sent: Thursday, March 1, 2012 11:09 AM Subject: Re: ERROR 2013 (HY000): Lost connection to MySQL server during query Il 01/03/2012 11:03, javad bakhshi ha scritto: Hi, I am trying to load data into my table from a very large file but after some time I get this error: ERROR 2013 (HY000): Lost connection to MySQL server during query My file size is around 4G and I have 220M lines in my file which have to be loaded in to my table. I have 10 of these files which have to loaded in the same table. My MySQL version is 5.1.59, I have changed the max_allowed_packet to 346030080. any ideas how I can solve this problem? Best regards, Javad Bakhshi, In order to resolve the problem you may need to increase these two values in mysql.ini or my.cnf, and restart mysql: wait_timeout = 28800 connect_timeout = 28800 -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/mysql -- -- Pythian proud winner of Oracle North America Titan Award for Exadata Solution...watch the video on pythian.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
Re: ERROR 2013 (HY000): Lost connection to MySQL server during query
Hi, Still have the same problem and changing connect_timeout didn't help. Any other Ideas? Is there even any solution to this? Best regards, Javad Bakhshi, From: mail...@securitylabs.it mail...@securitylabs.it To: mysql@lists.mysql.com Sent: Thursday, March 1, 2012 11:09 AM Subject: Re: ERROR 2013 (HY000): Lost connection to MySQL server during query Il 01/03/2012 11:03, javad bakhshi ha scritto: Hi, I am trying to load data into my table from a very large file but after some time I get this error: ERROR 2013 (HY000): Lost connection to MySQL server during query My file size is around 4G and I have 220M lines in my file which have to be loaded in to my table. I have 10 of these files which have to loaded in the same table. My MySQL version is 5.1.59, I have changed the max_allowed_packet to 346030080. any ideas how I can solve this problem? Best regards, Javad Bakhshi, In order to resolve the problem you may need to increase these two values in mysql.ini or my.cnf, and restart mysql: wait_timeout = 28800 connect_timeout = 28800 -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/mysql
Re: ERROR 2013 (HY000): Lost connection to MySQL server during query
Checking your firewall settings.. S On Mon, Mar 5, 2012 at 08:39, javad bakhshi javadbakh...@yahoo.com wrote: Hi, Still have the same problem and changing connect_timeout didn't help. Any other Ideas? Is there even any solution to this? Best regards, Javad Bakhshi, From: mail...@securitylabs.it mail...@securitylabs.it To: mysql@lists.mysql.com Sent: Thursday, March 1, 2012 11:09 AM Subject: Re: ERROR 2013 (HY000): Lost connection to MySQL server during query Il 01/03/2012 11:03, javad bakhshi ha scritto: Hi, I am trying to load data into my table from a very large file but after some time I get this error: ERROR 2013 (HY000): Lost connection to MySQL server during query My file size is around 4G and I have 220M lines in my file which have to be loaded in to my table. I have 10 of these files which have to loaded in the same table. My MySQL version is 5.1.59, I have changed the max_allowed_packet to 346030080. any ideas how I can solve this problem? Best regards, Javad Bakhshi, In order to resolve the problem you may need to increase these two values in mysql.ini or my.cnf, and restart mysql: wait_timeout = 28800 connect_timeout = 28800 -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql -- -- Pythian proud winner of Oracle North America Titan Award for Exadata Solution...watch the video on pythian.com
ERROR 2013 (HY000): Lost connection to MySQL server during query
Hi, I am trying to load data into my table from a very large file but after some time I get this error: ERROR 2013 (HY000): Lost connection to MySQL server during query My file size is around 4G and I have 220M lines in my file which have to be loaded in to my table. I have 10 of these files which have to loaded in the same table. My MySQL version is 5.1.59, I have changed the max_allowed_packet to 346030080. any ideas how I can solve this problem? Best regards, Javad Bakhshi,
Re: ERROR 2013 (HY000): Lost connection to MySQL server during query
Il 01/03/2012 11:03, javad bakhshi ha scritto: Hi, I am trying to load data into my table from a very large file but after some time I get this error: ERROR 2013 (HY000): Lost connection to MySQL server during query My file size is around 4G and I have 220M lines in my file which have to be loaded in to my table. I have 10 of these files which have to loaded in the same table. My MySQL version is 5.1.59, I have changed the max_allowed_packet to 346030080. any ideas how I can solve this problem? Best regards, Javad Bakhshi, In order to resolve the problem you may need to increase these two values in mysql.ini or my.cnf, and restart mysql: wait_timeout = 28800 connect_timeout = 28800 -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql
ERROR 2013 (HY000): Lost connection to MySQL server during query, 061220 14:48:44 mysqld restarted
I have MySQL 4.1.22 source installation on a 1.66 Intel Core Duo Mac Mini running OS X Server 10.4.8. It is a slave replicating to a master over ssl. Replication works fine, however I get this error always if I execute the STOP SLAVE statement ([EMAIL PROTECTED]) (none) stop slave; ERROR 2013 (HY000): Lost connection to MySQL server during query ([EMAIL PROTECTED]) (none) 061220 14:48:44 mysqld restarted Also, if I execute mysqladmin shutdown, it restarts also slmini:/usr/local admin$ mysqladmin -u root -p shutdown Enter password: slmini:/usr/local admin$ 061220 14:59:19 mysqld restarted The source has been compiled with SSL feature. I have exact same installation on a single CPU powerpc G4 XServe with no problems. My installation procedure/flags are here: Any ideas what the problem might be? Should I just rebuild the OS from scratch? Could it be corrupt data that needs to be recopied form the master? I'm baffled at this point. Regards, Kieran -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: ERROR 2013 (HY000): Lost connection to MySQL server during query, 061220 14:48:44 mysqld restarted
I left out URL to source compilation procedure and flags in original message. Here it is: http://homepage.mac.com/kelleherk/iblog/C711669388/E20061121141451/ index.html ANy advice would be really appreciated. Regards, Kieran On Dec 20, 2006, at 3:08 PM, Kieran Kelleher wrote: I have MySQL 4.1.22 source installation on a 1.66 Intel Core Duo Mac Mini running OS X Server 10.4.8. It is a slave replicating to a master over ssl. Replication works fine, however I get this error always if I execute the STOP SLAVE statement ([EMAIL PROTECTED]) (none) stop slave; ERROR 2013 (HY000): Lost connection to MySQL server during query ([EMAIL PROTECTED]) (none) 061220 14:48:44 mysqld restarted Also, if I execute mysqladmin shutdown, it restarts also slmini:/usr/local admin$ mysqladmin -u root -p shutdown Enter password: slmini:/usr/local admin$ 061220 14:59:19 mysqld restarted The source has been compiled with SSL feature. I have exact same installation on a single CPU powerpc G4 XServe with no problems. My installation procedure/flags are here: Any ideas what the problem might be? Should I just rebuild the OS from scratch? Could it be corrupt data that needs to be recopied form the master? I'm baffled at this point. Regards, Kieran -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql? [EMAIL PROTECTED] -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: ERROR 2013 (HY000): Lost connection to MySQL server during query, 061220 14:48:44 mysqld restarted
Replying to myself again... OK, some more light on the subject. I did a complete dump of the master and reloaded the slave thinking maybe I had corrupt tables or something. Having started the slave with skip-start-slave, I found that I could stop mysqld on command line using mysqladmin without problems. As soon as I started the slave and tried to issue a stop slave, then the crash happened again. So basically the crash only happens if we try and stop the slave threads. This wouls explain why mysaadmin shutdown crashed when slave IO was on, but not when slave IO was stopped. Here is error I got this time for stop slave: stop slave; ERROR 2013 (HY000): Lost connection to MySQL server during query ([EMAIL PROTECTED]) (none) /usr/local/mysql/bin/mysqld_safe: line 1: 401 Illegal instruction nohup /usr/local/mysql/libexec/ mysqld --defaults-extra-file=/usr/local/mysql/data/my.cnf --basedir=/ usr/local/mysql --datadir=/usr/local/mysql/data --user=mysql --pid- file=/usr/local/mysql/data/slmini.local.pid --socket=/tmp/mysql.sock --skip-slave-start /usr/local/mysql/data/slmini.local.err 21 061220 16:02:05 mysqld restarted Any ideas what could be wrong here or is this possibly a bug? Regards, Kieran On Dec 20, 2006, at 3:08 PM, Kieran Kelleher wrote: I have MySQL 4.1.22 source installation on a 1.66 Intel Core Duo Mac Mini running OS X Server 10.4.8. It is a slave replicating to a master over ssl. Replication works fine, however I get this error always if I execute the STOP SLAVE statement ([EMAIL PROTECTED]) (none) stop slave; ERROR 2013 (HY000): Lost connection to MySQL server during query ([EMAIL PROTECTED]) (none) 061220 14:48:44 mysqld restarted Also, if I execute mysqladmin shutdown, it restarts also slmini:/usr/local admin$ mysqladmin -u root -p shutdown Enter password: slmini:/usr/local admin$ 061220 14:59:19 mysqld restarted The source has been compiled with SSL feature. I have exact same installation on a single CPU powerpc G4 XServe with no problems. My installation procedure/flags are here: Any ideas what the problem might be? Should I just rebuild the OS from scratch? Could it be corrupt data that needs to be recopied form the master? I'm baffled at this point. Regards, Kieran -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql? [EMAIL PROTECTED] -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
ERROR 2013 (HY000): Lost connection to MySQL server during query
Hi, I am getting this error. Can anyone please help? mysql create table sfgbackup.advEmail select * from sfg.advEmail; ERROR 2013 (HY000): Lost connection to MySQL server during query Bye [EMAIL PROTECTED] mgandikota]$ mysql -V mysql Ver 14.7 Distrib 5.0.2-alpha, for pc-linux (i686) Thanks Murthy __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
Re: ERROR 2013 (HY000): Lost connection to MySQL server during query
Hello That version is quite old and is an alpha version. I think you can download a release for production use. Gu Lei - Original Message - From: murthy gandikota [EMAIL PROTECTED] To: mysql@lists.mysql.com Sent: Thursday, June 08, 2006 9:04 PM Subject: ERROR 2013 (HY000): Lost connection to MySQL server during query Hi, I am getting this error. Can anyone please help? mysql create table sfgbackup.advEmail select * from sfg.advEmail; ERROR 2013 (HY000): Lost connection to MySQL server during query Bye [EMAIL PROTECTED] mgandikota]$ mysql -V mysql Ver 14.7 Distrib 5.0.2-alpha, for pc-linux (i686) Thanks Murthy __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
ERROR 2013 (HY000): Lost connection to MySQL server during query
Hello, again, I'm having problems with InnoDB tables. A certain table cannot be dropped. If I'm issueing the drop table statement, the connection is lost and I get the following in the logfile: 060327 14:38:11 InnoDB: error: space object of table db15670/mw_pagelinks, InnoDB: space id 12 did not exist in memory. Retrying an open. InnoDB: Error: trying to add tablespace 12 of name './db15670/mw_pagelinks.ibd' InnoDB: to the tablespace memory cache, but tablespace InnoDB: 12 of name './db15720/admin.ibd' already exists in the tablespace InnoDB: memory cache! 060327 14:38:11 InnoDB: Error: page 3 log sequence number 0 153218641 InnoDB: is in the future! Current system log sequence number 0 14322402. InnoDB: Your database may be corrupt. 060327 14:38:11InnoDB: Assertion failure in thread 196621 in file fsp0fsp.c line 3202 InnoDB: Failing assertion: xdes_get_bit(descr, XDES_FREE_BIT, buf_frame_get_page_no(header) % FSP_EXTENT_SIZE, mtr) == FALSE InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to http://bugs.mysql.com. InnoDB: If you get repeated assertion failures or crashes, even InnoDB: immediately after the mysqld startup, there may be InnoDB: corruption in the InnoDB tablespace. Please refer to InnoDB: http://dev.mysql.com/doc/mysql/en/Forcing_recovery.html InnoDB: about forcing recovery. mysqld got signal 11; This could be because you hit a bug. It is also possible that this binary or one of the libraries it was linked against is corrupt, improperly built, or misconfigured. This error can also be caused by malfunctioning hardware. We will try our best to scrape up some info that will hopefully help diagnose the problem, but since we have already crashed, something is definitely wrong and this may fail. key_buffer_size=402653184 read_buffer_size=2093056 max_used_connections=12 max_connections=1000 threads_connected=5 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 290904 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. thd=0x8a000c18 Attempting backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong... Cannot determine thread, fp=0xbe1fbe08, backtrace may not be correct. Stack range sanity check OK, backtrace follows: 0x80a43b4 0x82bf71c 0x820a5fd 0x81b64f5 0x8169f26 0x81a4bc7 0x81a4224 0x81a36c2 0x817f332 0x817e57d 0x819376b 0x8125411 0x811ba68 0x812abe0 0x812a500 0x80b76b2 0x80bbb72 0x80b54bd 0x80b5102 0x80b48f9 0x82bb001 0x82ed89a New value of fp=(nil) failed sanity check, terminating stack trace! Please read http://dev.mysql.com/doc/mysql/en/Using_stack_trace.html and follow instructions on how to resolve the stack trace. Resolved stack trace is much more helpful in diagnosing the problem, so please do resolve it Trying to get some variables. Some pointers may be invalid and cause the dump to abort... thd-query at 0x8bb38e0 = drop table mw_pagelinks thd-thread_id=220 The manual page at http://www.mysql.com/doc/en/Crashing.html contains information that should help you find out what is causing the crash. Number of processes running now: 0 060327 14:38:12 mysqld restarted 060327 14:38:12 InnoDB: Database was not shut down normally! InnoDB: Starting crash recovery. The whole mysql-server crashed just because something is wrong in one innodb table. The force-recovery-hint didn't help at all, because it just made it possible do drop the table, but nothing was fixed and I couldn't create the table back then. Why does this happen? Regards Marten -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: ERROR 2013 (HY000): Lost connection to MySQL server during query
Marten, can you email the complete .err log from the server to [EMAIL PROTECTED] I am interested in what caused the very first crash in the server. Now your database seems to be seriously corrupt, since the log sequence number in the log files is only 14 MB, while it is = 153 MB in a data file! Did you move around or delete ib_logfiles or ibdata files or .ibd files, or edit my.cnf while mysqld was running? Are you using some exotic file system? The output looks like ib_logfiles and data files from different servers would be mixed. Best regards, Heikki Oracle Corp./Innobase Oy InnoDB - transactions, row level locking, and foreign keys for MySQL InnoDB Hot Backup - a hot backup tool for InnoDB which also backs up MyISAM tables http://www.innodb.com/order.php - Original Message - From: Marten Lehmann [EMAIL PROTECTED] Newsgroups: mailing.database.myodbc Sent: Monday, March 27, 2006 3:46 PM Subject: ERROR 2013 (HY000): Lost connection to MySQL server during query Hello, again, I'm having problems with InnoDB tables. A certain table cannot be dropped. If I'm issueing the drop table statement, the connection is lost and I get the following in the logfile: 060327 14:38:11 InnoDB: error: space object of table db15670/mw_pagelinks, InnoDB: space id 12 did not exist in memory. Retrying an open. InnoDB: Error: trying to add tablespace 12 of name './db15670/mw_pagelinks.ibd' InnoDB: to the tablespace memory cache, but tablespace InnoDB: 12 of name './db15720/admin.ibd' already exists in the tablespace InnoDB: memory cache! 060327 14:38:11 InnoDB: Error: page 3 log sequence number 0 153218641 InnoDB: is in the future! Current system log sequence number 0 14322402. InnoDB: Your database may be corrupt. 060327 14:38:11InnoDB: Assertion failure in thread 196621 in file fsp0fsp.c line 3202 InnoDB: Failing assertion: xdes_get_bit(descr, XDES_FREE_BIT, buf_frame_get_page_no(header) % FSP_EXTENT_SIZE, mtr) == FALSE InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to http://bugs.mysql.com. InnoDB: If you get repeated assertion failures or crashes, even InnoDB: immediately after the mysqld startup, there may be InnoDB: corruption in the InnoDB tablespace. Please refer to InnoDB: http://dev.mysql.com/doc/mysql/en/Forcing_recovery.html InnoDB: about forcing recovery. mysqld got signal 11; This could be because you hit a bug. It is also possible that this binary or one of the libraries it was linked against is corrupt, improperly built, or misconfigured. This error can also be caused by malfunctioning hardware. We will try our best to scrape up some info that will hopefully help diagnose the problem, but since we have already crashed, something is definitely wrong and this may fail. key_buffer_size=402653184 read_buffer_size=2093056 max_used_connections=12 max_connections=1000 threads_connected=5 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 290904 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. thd=0x8a000c18 Attempting backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong... Cannot determine thread, fp=0xbe1fbe08, backtrace may not be correct. Stack range sanity check OK, backtrace follows: 0x80a43b4 0x82bf71c 0x820a5fd 0x81b64f5 0x8169f26 0x81a4bc7 0x81a4224 0x81a36c2 0x817f332 0x817e57d 0x819376b 0x8125411 0x811ba68 0x812abe0 0x812a500 0x80b76b2 0x80bbb72 0x80b54bd 0x80b5102 0x80b48f9 0x82bb001 0x82ed89a New value of fp=(nil) failed sanity check, terminating stack trace! Please read http://dev.mysql.com/doc/mysql/en/Using_stack_trace.html and follow instructions on how to resolve the stack trace. Resolved stack trace is much more helpful in diagnosing the problem, so please do resolve it Trying to get some variables. Some pointers may be invalid and cause the dump to abort... thd-query at 0x8bb38e0 = drop table mw_pagelinks thd-thread_id=220 The manual page at http://www.mysql.com/doc/en/Crashing.html contains information that should help you find out what is causing the crash. Number of processes running now: 0 060327 14:38:12 mysqld restarted 060327 14:38:12 InnoDB: Database was not shut down normally! InnoDB: Starting crash recovery. The whole mysql-server crashed just because something is wrong in one innodb table. The force-recovery-hint didn't help at all, because it just made it possible do drop the table, but nothing was fixed and I couldn't create the table back then. Why does this happen? Regards Marten -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
