MySQL Bugs: #76449: Crash (signal 11) of mysql-server 5.5.41 on create table

Bug #76449	Crash (signal 11) of mysql-server 5.5.41 on create table
Submitted:	23 Mar 2015 10:19	Modified:	10 Oct 2015 11:34
Reporter:	Wiebe Cazemier	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Server	Severity:	S2 (Serious)
Version:	5.5.41-0ubuntu0.12.04.1	OS:	Linux
Assigned to:		CPU Architecture:	Any

Description:
I had a bunch crashes of the MySQL server (5.5.41-0ubuntu0.12.04.1). All I did was create a table:

CREATE TABLE `logDataWithPartitiontestje3` (
  `idLog` bigint(20) unsigned NOT NULL,
  `instance` smallint(5) unsigned NOT NULL, 
  `idDataAttribute` smallint(5) unsigned NOT NULL,
  `valueFloat` float DEFAULT NULL,
  `valueString` varchar(255) DEFAULT NULL,
  `valueEnum` smallint(6) DEFAULT NULL,
  `month` tinyint not null default 0, 
  PRIMARY KEY (`idLog`,`instance`,`idDataAttribute`, `month`),
  CONSTRAINT `logData_ibfk_aaa` FOREIGN KEY (`idLog`) REFERENCES `logs` (`idLog`) ON DELETE CASCADE,
  CONSTRAINT `logData_ibfk_aaa` FOREIGN KEY (`idDataAttribute`) REFERENCES `dataAttributes` (`idDataAttribute`)
) 
ENGINE=InnoDB DEFAULT CHARSET=latin1;

In itself a syntax error (double constraint name), but other DB servers I have, don't crash on it. I don't dare testing with our live production server again, which is the only server I could reproduce this on.

The first crash was:

09:52:40 UTC - 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=110
max_threads=151
thread_count=7
connection_count=7
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 346700 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x7ff75e4cbb50
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 = 7ff7506e7e60 thread_stack 0x30000
/usr/sbin/mysqld(my_print_stacktrace+0x29)[0x7ff756680d79]
/usr/sbin/mysqld(handle_fatal_signal+0x483)[0x7ff756545923]
/lib/x86_64-linux-gnu/libpthread.so.0(+0xfcb0)[0x7ff75528dcb0]
/usr/sbin/mysqld(+0x65ef3f)[0x7ff756783f3f]
/usr/sbin/mysqld(+0x663bc5)[0x7ff756788bc5]
/usr/sbin/mysqld(+0x5edb5d)[0x7ff756712b5d]
/usr/sbin/mysqld(+0x5ee855)[0x7ff756713855]
/usr/sbin/mysqld(+0x5d73c1)[0x7ff7566fc3c1]
/usr/sbin/mysqld(_Z15ha_create_tableP3THDPKcS2_S2_P24st_ha_create_informationb+0x1a2)[0x7ff75654c2c2]
/usr/sbin/mysqld(_Z16rea_create_tableP3THDPKcS2_S2_P24st_ha_create_informationR4ListI12Create_fieldEjP6st_keyP7handler+0x209)[0x7ff7564be6a9]
/usr/sbin/mysqld(+0x36b931)[0x7ff756490931]
/usr/sbin/mysqld(_Z18mysql_create_tableP3THDP10TABLE_LISTP24st_ha_create_informationP10Alter_info+0x9c)[0x7ff7564921bc]
/usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x623a)[0x7ff75642d59a]
/usr/sbin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_state+0x10f)[0x7ff75642dc1f]
/usr/sbin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0x1f26)[0x7ff75642fc16]
/usr/sbin/mysqld(_Z24do_handle_one_connectionP3THD+0x1bd)[0x7ff7564d698d]
/usr/sbin/mysqld(handle_one_connection+0x50)[0x7ff7564d69f0]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x7e9a)[0x7ff755285e9a]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7ff7549b72ed]

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (7ff5ac8c4120): is an invalid pointer
Connection ID (thread ID): 11676395
Status: NOT_KILLED

After that, in trying to create the table again, it crashed again and again. I will attach the log when the bug report has been created.

How to repeat:
I don't quite know how to obtain more information and create a reproducable situation without affecting our live db server, nor can I pinpoint an action that I did that caused this. It seems to be happening on create table for me. Any table (in this one DB).

MySQL error log showing several crashes in a row

Attachment: mysql-crash-complete-error-log.txt (text/plain), 47.16 KiB.

I'm seeing the same issue - specifically running 5.5.43-0ubuntu0.14.0.4.1.  Sometimes, when creating tables with foreign key constraints, the database crashes.  Note - this is not all of the time.  Dropped and recreated said table 3 times with foreign key constraints and on the third time the mysql crashes.  Stack trace:

19:24:56 UTC - 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=29
max_threads=151
thread_count=21
connection_count=21
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 346700 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x7ff54460aed0
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 = 7ff528511e98 thread_stack 0x30000
/usr/sbin/mysqld(my_print_stacktrace+0x20)[0x7ff541780c80]
/usr/sbin/mysqld(handle_fatal_signal+0x3d5)[0x7ff54166af15]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x10340)[0x7ff5403fb340]
/usr/sbin/mysqld(+0x5e38ff)[0x7ff5418738ff]
/usr/sbin/mysqld(+0x5e82d5)[0x7ff5418782d5]
/usr/sbin/mysqld(+0x57824e)[0x7ff54180824e]
/usr/sbin/mysqld(+0x57932c)[0x7ff54180932c]
/usr/sbin/mysqld(+0x567bd1)[0x7ff5417f7bd1]
/usr/sbin/mysqld(_Z15ha_create_tableP3THDPKcS2_S2_P24st_ha_create_informationb+0x13d)[0x7ff54167074d]
/usr/sbin/mysqld(_Z16rea_create_tableP3THDPKcS2_S2_P24st_ha_create_informationR4ListI12Create_fieldEjP6st_keyP7handler+0x1cb)[0x7ff5416092bb]
/usr/sbin/mysqld(+0x352402)[0x7ff5415e2402]
/usr/sbin/mysqld(_Z18mysql_create_tableP3THDP10TABLE_LISTP24st_ha_create_informationP10Alter_info+0x8a)[0x7ff5415e29ca]
/usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x5aa8)[0x7ff54158b2a8]
/usr/sbin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_state+0x160)[0x7ff54158c520]
/usr/sbin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0x1df2)[0x7ff54158eab2]
/usr/sbin/mysqld(_Z24do_handle_one_connectionP3THD+0x176)[0x7ff54161b096]
/usr/sbin/mysqld(handle_one_connection+0x41)[0x7ff54161b0f1]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x8182)[0x7ff5403f3182]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7ff53fb1647d]

We're about the deprecate the server that's doing this. I think I can arrange access for Oracle to test with. However, this machine costs € 500 per month, so it won't be long. It will probably only see out june of july.

Let me know if you need it, and I'll see if I can arrange something.

Please check against released version 5.5.45. Thanks.

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