MySQL Bugs: #13990: mysqld gets signal 11 after show fields or show columns

Bug #13990	mysqld gets signal 11 after show fields or show columns
Submitted:	13 Oct 2005 2:45	Modified:	22 Nov 2005 8:15
Reporter:	Stefan Tomic	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Server	Severity:	S2 (Serious)
Version:	4.0.25	OS:	Linux (redhat EL 3.0)
Assigned to:		CPU Architecture:	Any

Description:
mysql server gets signal 11 after show fields or show columns. The problem is intermittent and not easily reproducable. The server was upgraded from v. 3.23 approximately 2-3 months ago. This problem did not surface until 1 week ago immediately following installation of a firewire card and connection to a firewire drive.

mysqld kept receiving signal 11 and automatically restarting after "show fields" today. Tried shutting down mysqld with mysqladmin and starting again with init.d script. Server still got signal 11 after "show fields". A hard reboot of the computer solved the problem for now.

Ran "check tables" on tables for which the error occurred and they checked out OK.

The following is the output of the error log and the resolved stack trace from one crash. I apparently fixed the 196608 thread stack warning by setting the thread stack to 124k in my.cnf. I am using glibc 2.3.2. Not sure if this was the right fix but it got rid of the warning.

RESOLVED STACK TRACE
---------------------------------------------
0x8072d74 handle_segfault + 420
0x826d678 pthread_sighandler + 184
0x80e0ffb mysqld_show_fields__FP3THDP13st_table_listPCcb + 459
0x8080164 mysql_execute_command__Fv + 9364
0x8081c45 mysql_parse__FP3THDPcUi + 149
0x807d173 dispatch_command__F19enum_server_commandP3THDPcUi + 1427
0x807cbce do_command__FP3THD + 158
0x807c3f8 handle_one_connection + 648
0x826ae2c pthread_start_thread + 220
0x82a0cda thread_start + 4

ERROR LOG
-------------------------------------------------
Number of processes running now: 0
051012 15:18:11 mysqld restarted
051012 15:18:11 Warning: Asked for 196608 thread stack, but got 126976
051012 15:18:11 InnoDB: Started
/usr/sbin/mysqld: ready for connections.
Version: '4.0.25-standard' socket: '/var/lib/mysql/mysql.sock' port: 3306 Official MySQL RPM
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=8388600
read_buffer_size=131072
max_used_connections=1
max_connections=100
threads_connected=2
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 225791 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd=0x87a0e80
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=0xbfe7f288, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x8072d74
0x826d678
0x80e0ffb
0x8080164
0x8081c45
0x807d173
0x807cbce
0x807c3f8
0x826ae2c
0x82a0cda
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 0x87a4d18 = SHOW FIELDS FROM `phpmyadmin`.`pma_column_info`
thd->thread_id=1

How to repeat:
Intermittent problem. Can't reproduce after restarting the computer.

Suggested fix:
none yet.

Thank you for a problem report. Please, describe your hardware (RAM amount etc.), send the my.cnf content and try to provide additional details on how to reproduce this situation.

Have you tried to use 4.0.26?

Thanks for your response. I tried responding earlier but apparently it didn't get submitted.

After a hard reboot of the computer, the problem can't be reproduced. I am running the same php forms (which perform the sql queries) and they are working fine. I am not assuming the problem just went away quite yet, however. I will try 4.0.26 as you suggested. Any other suggestions are welcome.

Thanks!

600 MHz Dual Processor Pentium III
1 Gb RAM
66 Gb volume (28 Gb used)
 
my.cnf:
[mysqld]
datadir=/var/lib/mysql
socket=/var/lib/mysql/mysql.sock
innodb_data_file_path=ibdata1:10M:autoextend:max:1000M
default-table-type=innodb
user=mysql
set-variable    = thread_stack=124k
log=/var/log/mysql_query.log
     
[mysql.server]
basedir=/var/lib

[safe_mysqld]
err-log=/var/log/mysqld.log
log=/var/log/mysql_query.log
pid-file=/var/run/mysqld/mysqld.pid

Thank you for the additional information. I see no obvious reason for that crash. Can it be a hardware failure (old RAM, power surge)?

Please, try to obtain as much details as possible next time when this will happen (what queries are performed, what happened at the OS level, what tables and storage engines were used etc).

I am especially interested in the crash if it happen after upgrade to 4.0.26. In the meantime, I left this report in "Need Feedback" state.

Please, inform about any crash with 4.0.26 when you'll get it.

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