MySQL Bugs: #26823: ERROR 2013 (HY000): Lost connection to MySQL server during query

Bug #26823	ERROR 2013 (HY000): Lost connection to MySQL server during query
Submitted:	3 Mar 2007 14:00	Modified:	10 May 2007 17:49
Reporter:	Yuriy Filatov	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Server	Severity:	S1 (Critical)
Version:	5.0.32	OS:	Linux (Debian Linux)
Assigned to:		CPU Architecture:	Any
Tags:	show status crash error 2006

Description:
any SHOW

mysqld: Can't create/write to file '/tmp/ib3m5yU0' (Errcode: 13)
070303 15:49:22 InnoDB: Error: unable to create temporary file; errno: 13
070303 15:49:22 [Note] mysqld: ready for connections.
Version: '5.0.32-Debian_7-log' socket: '/var/run/mysqld/mysqld.sock' port: 3306 Debian etch distribution
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=16777216
read_buffer_size=131072
max_used_connections=1
max_connections=100
threads_connected=1
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 233983 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd=0x8a64e08
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=0xb5a679a8, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x81c0649
0x82ed21e
0x826ca54
0x829e61a
0x829d576
0x8220149
0x8221c20
0x822248e
0x81d7495
0x81dba07
0x81dbec0
0x81dd188
0x81ddb94
0xb7ee2240
0xb7d1d3de
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 0x8a9d358 = show status
thd->thread_id=1
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.

How to repeat:
SHOW STATUS command crashes Server:

mysql> show status;
ERROR 2006 (HY000): MySQL server has gone away
No connection. Trying to reconnect...
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (111)
ERROR:
Can't connect to the server

mysql>

Thank you for a problem report. Please, send the resolved stack trace, you my.cnf file content and the results of:

uname -a
ulimit -a
df -k

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".

Feedback is still needed.

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".