Bug #83331 InnoDB: Assertion failure
Submitted: 11 Oct 2016 6:24 Modified: 11 Nov 2016 10:18
Reporter: Vinoth kumar Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Server Severity:S2 (Serious)
Version:5.5.47 OS:CentOS (centos-release-7-2.1511.el7.centos.2.10.x86_64)
Assigned to: CPU Architecture:Any
Tags: MySQL

[11 Oct 2016 6:24] Vinoth kumar
Description:
Log : 

0:30:27  InnoDB: Assertion failure in thread 139846752941824 in file fil0fil.c line 834
InnoDB: Failing assertion: ret
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.5/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
07:30:27 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.

key_buffer_size=8388608
read_buffer_size=67108864
max_used_connections=64
max_threads=1000
thread_count=30
connection_count=30
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 131091746 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0xa29cc00
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 = 7f309c082ec0 thread_stack 0x40000
/usr/sbin/mysqld(my_print_stacktrace+0x3b)[0x7bd01b]
/usr/sbin/mysqld(handle_fatal_signal+0x4a1)[0x687761]
/lib64/libpthread.so.0(+0xf100)[0x7f30a08e1100]
/lib64/libc.so.6(gsignal+0x37)[0x7f309fc075f7]
/lib64/libc.so.6(abort+0x148)[0x7f309fc08ce8]
/usr/sbin/mysqld[0x8917e4]
/usr/sbin/mysqld[0x8919e8]
/usr/sbin/mysqld[0x89bed3]
/usr/sbin/mysqld[0x872f19]
/usr/sbin/mysqld[0x861897]
/usr/sbin/mysqld[0x84a0d1]
/usr/sbin/mysqld[0x84b622]
/usr/sbin/mysqld[0x8fd471]
/usr/sbin/mysqld[0x900d0a]
/usr/sbin/mysqld[0x900f97]
/usr/sbin/mysqld[0x7fc894]
/usr/sbin/mysqld[0x7e9068]
/usr/sbin/mysqld(_ZN7handler12ha_write_rowEPh+0x70)[0x68e640]
/usr/sbin/mysqld(_Z12write_recordP3THDP5TABLEP12st_copy_info+0x6e)[0x57c12e]
/usr/sbin/mysqld(_Z12mysql_insertP3THDP10TABLE_LISTR4ListI4ItemERS3_IS5_ES6_S6_15enum_duplicatesb+0xc64)[0x57eac4]
/usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x37bd)[0x59469d]
/usr/sbin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_state+0x16a)[0x597d3a]
/usr/sbin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0x1bd1)[0x59a161]
/usr/sbin/mysqld(_Z24do_handle_one_connectionP3THD+0x132)[0x633f62]
/usr/sbin/mysqld(handle_one_connection+0x4a)[0x63402a]
/lib64/libpthread.so.0(+0x7dc5)[0x7f30a08d9dc5]
/lib64/libc.so.6(clone+0x6d)[0x7f309fcc821d]

How to repeat:
It happens sometime not able to pin down when it happens.
[11 Oct 2016 10:18] MySQL Verification Team
Thank you for the bug report. We need a repeatable test case you also could test most recent release 5.5.51, check hardware and memory usage: key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 131091746 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
[12 Nov 2016 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".