Bug #68711 InterfaceError: 2013: Lost connection to MySQL server during query
Submitted: 19 Mar 2013 4:29 Modified: 24 Mar 2013 7:52
Reporter: PBL Narasimha Rao Email Updates:
Status: Not a Bug Impact on me:
None 
Category:Connector / Python Severity:S1 (Critical)
Version:1.0.9 OS:Windows (XP)
Assigned to: CPU Architecture:Any
Tags: MySQL Python Connector

[19 Mar 2013 4:29] PBL Narasimha Rao
Description:
We get frequently "InterfaceError: 2013: Lost connection to MySQL server during query" this we faced in 1.0.7 too. Tried to upgrade to 1.0.8, but mysql.connector.connect() call ctypes.WinDLL('ws2_32.dll').inet_pton(). The function "inet_pton" in Windows 7 "ws2_32.dll", but in Windows XP or 2003.

Previously we used fetchall(), thought some issue in fetchall() so changed to fetchone() and iterated through cursor result. It solved issue up to some extend, But the issue still persists.

Here is my Python Trace-back

Traceback (most recent call last):
  File "DB_Module.py", line 165, in QueryDatabase
  File "\\ps\show_time\Showtime_Package\showtime\Modules\mysql\connector\cursor.py", line 599, in fetchone
    row = self._fetch_row()
  File "\\ps\show_time\Showtime_Package\showtime\Modules\mysql\connector\cursor.py", line 579, in _fetch_row
    (foo, eof) = self._nextrow = self._connection.get_row()
  File "\\ps\show_time\Showtime_Package\showtime\Modules\mysql\connector\connection.py", line 468, in get_row
    (rows, eof) = self.get_rows(count=1)
  File "\\ps\show_time\Showtime_Package\showtime\Modules\mysql\connector\connection.py", line 451, in get_rows
    rows = self._protocol.read_text_result(self._socket, count)
  File "\\ps\show_time\Showtime_Package\showtime\Modules\mysql\connector\protocol.py", line 234, in read_text_result
    packet = sock.recv()
  File "\\ps\show_time\Showtime_Package\showtime\Modules\mysql\connector\network.py", line 169, in recv_plain
    raise errors.InterfaceError(errno=2013)
InterfaceError: 2013: Lost connection to MySQL server during query

How to repeat:
There is no particular situation case to repeat this. 
But we think this is happening when query returns a large number of records.
[19 Mar 2013 4:31] PBL Narasimha Rao
Lost Connection TraceBack

Attachment: LostConnection_TraceBack.txt (text/plain), 1.07 KiB.

[24 Mar 2013 7:52] Andrii Nikitin
Hi, it doesn't look like Connector/Python problem.
Al least you must provide some proof that it is not some problem described in 
http://dev.mysql.com/doc/refman/5.5/en/error-lost-connection.html

Below is canned answer regarding how the problem looks:

We're sorry, but the bug system is not the appropriate forum for asking help on using MySQL products. Your problem is not the result of a bug.

Support on using our products is available both free in our forums at http://forums.mysql.com/ and for a reasonable fee direct from our skilled support engineers at http://www.mysql.com/support/

Thank you for your interest in MySQL.
[21 Jan 2016 7:43] Chiranjeevi Battula
http://bugs.mysql.com/bug.php?id=79790 marked as duplicate of this one.