Bug #15716 Lost connection during query
Submitted: 13 Dec 2005 16:34 Modified: 13 Jan 2006 16:53
Reporter: Sruli Ganor Email Updates:
Status: No Feedback Impact on me:
Category:MySQL Server Severity:S1 (Critical)
Version:4.0.14 OS:Windows (Win 2000 server)
Assigned to: CPU Architecture:Any

[13 Dec 2005 16:34] Sruli Ganor
Hi MySql gurus,

My application queries a database every 5 seconds. 
The query is very simple and uses 2 tables with a few thousands of rows in each. 
The application runs on the database server machine.

The query is:
SELECT brain_seq.Package_Id,brain_seq.Sequence  FROM brain_seq,Users  WHERE Users.Username='sruli' AND brain_seq.User_Id = Users.User_Id AND brain_seq.Status = 100  ORDER BY brain_seq.Sequence 

After some time (hours or days) the query fails and returns these errors:

[MySQL][ODBC 3.51 Driver][mysqld-4.0.15-nt]Lost connection to MySQL server during query (SQL state: S1000 , native error code: 2013)
[MySQL][ODBC 3.51 Driver][mysqld-4.0.15-nt]MySQL server has gone away (SQL state: S1000 , native error code: 2006)

During this time MySql service is up and running.

Any suggestions would be welcome.
Thanks in advance.


How to repeat:
Cannot be repeated - happens randomly.
[13 Dec 2005 16:53] Valeriy Kravchuk
Thank you for a problem report. The error messages you got mean that MySQL server was not working at the moment you sent a query or connection was lost for some other reason (http://dev.mysql.com/doc/refman/4.1/en/error-messages-client.html):

Message: MySQL server has gone away

Error: 2013 (CR_SERVER_LOST)
Message: Lost connection to MySQL server during query

There should be something in the server's error log (usually - hostname.err file in the data directory) when you get this error messages. Please, check.

Can you upgrade to a newer version (4.0.26)? Your 4.0.15 is really old.

What exact version of MyODBC do you use?
[14 Jan 2006 0:00] Bugs System
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".