Server crashed while creating CREATE TABLE innodb_table_monitor (a INT) ENGINE=INNODB;

Bug #1303749 reported by Muhammad Naseer hatti
18
This bug affects 2 people
Affects Status Importance Assigned to Milestone
MySQL Server
Unknown
Unknown
Percona Server moved to https://jira.percona.com/projects/PS
Fix Released
High
Unassigned
5.6
Fix Released
High
Unassigned

Bug Description

Using Server version: 5.6.16-64.0-553.wheezy (Debian). When I run the following sql,
CREATE TABLE innodb_table_monitor (a INT) ENGINE=INNODB; the server crashes complaining,

2014-04-07 12:18:06 7fdc4552e700 InnoDB: Assertion failure in thread 140584032593664 in file ha_innodb.cc line 11533
InnoDB: Failing assertion: ib_table->stat_initialized
InnoDB: We intentionally generate a memory trap.
...
140407 12:18:07 mysqld_safe Number of processes running now: 0
140407 12:18:07 mysqld_safe mysqld restarted

And mysql processes have to be killed and manually restarted. Let me know if more information is required.

Tags: upstream

Related branches

Revision history for this message
Jericho Rivera (jericho-rivera) wrote :

Can you attach the full error log as well as a copy of your my.cnf please.

Changed in percona-server:
status: New → Incomplete
Revision history for this message
Muhammad Naseer hatti (nbhatti) wrote :

error log file

Revision history for this message
Muhammad Naseer hatti (nbhatti) wrote :

my.cnf

Changed in percona-server:
status: Incomplete → New
Revision history for this message
Jericho Rivera (jericho-rivera) wrote :
Revision history for this message
Jericho Rivera (jericho-rivera) wrote :
Download full text (3.6 KiB)

Tested from upstream HOW-TO-REPEAT case:
CREATE TABLE innodb_table_wo_primary_key (id int, name varchar(200));
SELECT * FROM innodb_table_wo_primary_key;
CREATE TABLE innodb_table_monitor (a INT) ENGINE=INNODB;
SELECT * FROM innodb_table_wo_primary_key;

See note #4.

Warning: Using innodb_table_monitor is deprecated and it may be removed in future releases. Please use the InnoDB INFORMATION_SCHEMA tables instead, see http://dev.mysql.com/doc/refman/5.6/en/innodb-i_s-tables.html
2014-04-07 14:00:12 7f217f9be700 InnoDB: Assertion failure in thread 139781851571968 in file ha_innodb.cc line 11533
InnoDB: Failing assertion: ib_table->stat_initialized
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
14:00:12 UTC - mysqld got signal 6 ;
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.
Please help us make Percona Server better by reporting any
bugs at http://bugs.percona.com/

key_buffer_size=16777216
read_buffer_size=131072
max_used_connections=2
max_threads=153
thread_count=1
connection_count=1
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 77348 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x7f21af2b9ee0
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 = 7f217f9bde30 thread_stack 0x30000
/usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x7f21ac61c96e]
/usr/sbin/mysqld(handle_fatal_signal+0x40b)[0x7f21ac3c4c0b]
/lib/x86_64-linux-gnu/libpthread.so.0(+0xf030)[0x7f21abb28030]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0x35)[0x7f21a9d63475]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x180)[0x7f21a9d666f0]
/usr/sbin/mysqld(+0x77fb90)[0x7f21ac6d6b90]
/usr/sbin/mysqld(+0x6310f4)[0x7f21ac5880f4]
/usr/sbin/mysqld(_ZN4JOIN8optimizeEv+0x5e8)[0x7f21ac58afb8]
/usr/sbin/mysqld(_Z12mysql_selectP3THDP10TABLE_LISTjR4ListI4ItemEPS4_P10SQL_I_ListI8st_orderESB_S7_yP13select_resultP18st_select_lex_unitP13st_select_lex+0x21e)[0x7f21ac46290e]
/usr/sbin/mysqld(_Z13handle_selectP3THDP13select_resultm+0x16d)[0x7f21ac462bfd]
/usr/sbin/mysqld(+0x390786)[0x7f21ac2e7786]
/usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x3583)[0x7f21ac440923]
/usr/sbin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_state+0x5d8)[0x7f21ac442cd8]
/usr/sbin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0x12f9)[0x7f21ac444059]
/usr/sbin/mysqld(_Z24do_handle_one_connectionP3T...

Read more...

Revision history for this message
Valerii Kravchuk (valerii-kravchuk) wrote :

Set to Confirmed for PS 5.6 based on comment #5 from Jericho.

tags: added: upstream
Revision history for this message
Shahriyar Rzayev (rzayev-sehriyar) wrote :

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-780

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Related blueprints

Remote bug watches

Bug watches keep track of this bug in other bug trackers.