Bug #66569 General Crash when executing query " SHOW TABLE STATUS FROM `mysql`"
Submitted: 28 Aug 2012 9:25 Modified: 28 Sep 2012 9:54
Reporter: daniel murga Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Server: Errors Severity:S1 (Critical)
Version:5.1.30 OS:Linux (debian squezee)
Assigned to: CPU Architecture:Any
Tags: crash

[28 Aug 2012 9:25] daniel murga
Description:
Hello all,

After executing the query  " SHOW TABLE STATUS FROM `mysql`" the server crashes. The following appear on .err file:

/opt/lampp/sbin/mysqld(my_print_stacktrace+0x22)[0x84ac6c2]
/opt/lampp/sbin/mysqld(handle_segfault+0x39e)[0x81d558e]
[0xb77b8400]
/opt/lampp/sbin/mysqld(_Z12ha_checktypeP3THD14legacy_db_typebb+0x54)[0x82c8bc4]
/opt/lampp/sbin/mysqld(_Z14open_table_defP3THDP14st_table_sharej+0xa57)[0x82317f7]
/opt/lampp/sbin/mysqld(_Z15get_table_shareP3THDP10TABLE_LISTPcjjPi+0x1da)[0x8220eba]
/opt/lampp/sbin/mysqld[0x82261e8]
/opt/lampp/sbin/mysqld(_Z10open_tableP3THDP10TABLE_LISTP11st_mem_rootPbj+0x61b)[0x822976b]
/opt/lampp/sbin/mysqld(_Z11open_tablesP3THDPP10TABLE_LISTPjj+0x649)[0x822a609]
/opt/lampp/sbin/mysqld(_Z30open_normal_and_derived_tablesP3THDP10TABLE_LISTj+0x27)[0x822a8e7]
/opt/lampp/sbin/mysqld(_Z14get_all_tablesP3THDP10TABLE_LISTP4Item+0x966)[0x82f9a66]
/opt/lampp/sbin/mysqld(_Z24get_schema_tables_resultP4JOIN23enum_schema_table_state+0x1bf)[0x82ea1cf]
/opt/lampp/sbin/mysqld(_ZN4JOIN4execEv+0x4db)[0x825607b]
/opt/lampp/sbin/mysqld(_Z12mysql_selectP3THDPPP4ItemP10TABLE_LISTjR4ListIS1_ES2_jP8st_orderSB_S2_SB_yP13select_resultP18st_select_lex_unitP13st_select_lex+0x158)[0x8258818]
/opt/lampp/sbin/mysqld(_Z13handle_selectP3THDP6st_lexP13select_resultm+0x14a)[0x82590ca]
/opt/lampp/sbin/mysqld[0x81e076d]
/opt/lampp/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x1d06)[0x81e5f06]
/opt/lampp/sbin/mysqld(_Z11mysql_parseP3THDPKcjPS2_+0x211)[0x81eda61]
/opt/lampp/sbin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0x434)[0x81edea4]
/opt/lampp/sbin/mysqld(_Z10do_commandP3THD+0xe0)[0x81ef030]
/opt/lampp/sbin/mysqld(handle_one_connection+0x692)[0x81dde32]
/lib/i686/cmov/libpthread.so.0(+0x5955)[0xb779d955]
/lib/i686/cmov/libc.so.6(clone+0x5e)[0xb751458e]
120828 11:19:41 - 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=262144
max_used_connections=3
max_threads=151
threads_connected=2
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 133305 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd: 0xa9812d40
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...
stack_bottom = 0xa97ff384 thread_stack 0x30000
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 0x9695048 = SHOW TABLE STATUS FROM `mysql`
thd->thread_id=9
thd->killed=NOT_KILLED
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
120828 11:19:41 mysqld_safe Number of processes running now: 0
120828 11:19:41 mysqld_safe mysqld restarted
120828 11:19:41 [Warning] The syntax 'for replication startup options' is deprecated and will be removed in MySQL 5.2. Please use 'CHANGE MASTER' instead.
120828 11:19:41 [Warning] The syntax '--log_slow_queries' is deprecated and will be removed in MySQL 7.0. Please use '--slow_query_log'/'--slow_query_log_file' instead.
InnoDB: No valid checkpoint found.
InnoDB: If this error appears when you are creating an InnoDB database,
InnoDB: the problem may be that during an earlier attempt you managed
InnoDB: to create the InnoDB data files, but log file creation failed.
InnoDB: If that is the case, please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/error-creating-innodb.html
120828 11:19:41 [ERROR] Plugin 'InnoDB' init function returned error.
120828 11:19:41 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
120828 11:19:41 [Note] PrimeBase XT (PBXT) Engine 1.0.07 RC loaded...
120828 11:19:41 [Note] Paul McCullagh, PrimeBase Technologies GmbH, http://www.primebase.org
120828 11:19:41 [Note] The server was not shutdown correctly, recovery required
/opt/lampp/sbin/mysqld: File '/var/log/mysql/mysql-slow.log' not found (Errcode: 13)
120828 11:19:41 [ERROR] Could not use /var/log/mysql/mysql-slow.log for logging (error 13). Turning logging off for the whole duration of the MySQL server process. To turn it on again: fix the cause, shutdown the MySQL server and restart it.
120828 11:19:41 [Note] Slave SQL thread initialized, starting replication in log 'mysql-bin.000021' at position 2742340, relay log '/opt/lampp/var/mysql/slave-relay.000263' position: 251
120828 11:19:41 [Note] Event Scheduler: Loaded 0 events
120828 11:19:41 [Note] /opt/lampp/sbin/mysqld: ready for connections.
Version: '5.1.30-log'  socket: '/opt/lampp/var/mysql/mysql.sock'  port: 3306  Source distribution
120828 11:19:41 [Note] Slave I/O thread: connected to master 'replicadb@172.25.2.75:3306',replication started in log 'mysql-bin.000021' at position 2742340
root@srvtradws1:/opt/lampp-data/mysql-data#

How to repeat:
The way to repeat the issue is just executing the query another time.
[28 Aug 2012 9:54] Valeriy Kravchuk
Please, check if the same problem still happens with a recent version, 5.1.65.
[29 Sep 2012 1: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".