Bug #81112 Assertion failure
Submitted: 17 Apr 2016 20:14 Modified: 18 May 2016 16:08
Reporter: Nico Niepraschk Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Server: InnoDB storage engine Severity:S1 (Critical)
Version:5.6.30 OS:Any (6.7)
Assigned to: CPU Architecture:Any

[17 Apr 2016 20:14] Nico Niepraschk
Description:
Version: '5.6.30-log'  socket: '/var/lib/mysql/mysql.sock'  port: 3306  MySQL Community Server (GPL)
2016-04-17 01:06:22 7f6cea1fc700 InnoDB: FTS Optimize Removing table maxvis_4_0_cb_els/#sql2-a062-ae4
2016-04-17 01:08:14 7f6cea1fc700  InnoDB: Assertion failure in thread 140105761146624 in file pars0pars.cc line 865
InnoDB: Failing assertion: sym_node->table != NULL
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.
23:08:14 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=134217728
read_buffer_size=8388608
max_used_connections=29
max_threads=300
thread_count=24
connection_count=24
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 2669311 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0
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 = 0 thread_stack 0x40000
/usr/sbin/mysqld(my_print_stacktrace+0x35)[0x8e3015]
/usr/sbin/mysqld(handle_fatal_signal+0x494)[0x668134]
/lib64/libpthread.so.0(+0xf7e0)[0x7f780a33f7e0]
/lib64/libc.so.6(gsignal+0x35)[0x7f7808ddf625]
/lib64/libc.so.6(abort+0x175)[0x7f7808de0e05]
/usr/sbin/mysqld[0x9a52f9]
/usr/sbin/mysqld[0x9a73ff]
/usr/sbin/mysqld(_Z7yyparsev+0xb3f)[0xac3e8f]
/usr/sbin/mysqld[0x9a6405]
/usr/sbin/mysqld[0xac137c]
/usr/sbin/mysqld[0xaa9462]
/usr/sbin/mysqld[0xaaf459]
/usr/sbin/mysqld(_Z23fts_optimize_sync_tablem+0x3d)[0xab4f0d]
/usr/sbin/mysqld[0xab9b96]
/lib64/libpthread.so.0(+0x7aa1)[0x7f780a337aa1]
/lib64/libc.so.6(clone+0x6d)[0x7f7808e9593d]
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.
160417 01:08:14 mysqld_safe Number of processes running now: 0
160417 01:08:14 mysqld_safe mysqld restarted
2016-04-17 01:08:14 0 [Note] /usr/sbin/mysqld (mysqld 5.6.30-log) starting as process 41602 ...
2016-04-17 01:08:14 41602 [Note] Plugin 'FEDERATED' is disabled.
2016-04-17 01:08:14 41602 [Note] InnoDB: Using atomics to ref count buffer pool pages
2016-04-17 01:08:14 41602 [Note] InnoDB: The InnoDB memory heap is disabled
2016-04-17 01:08:14 41602 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2016-04-17 01:08:14 41602 [Note] InnoDB: Memory barrier is not used
2016-04-17 01:08:14 41602 [Note] InnoDB: Compressed tables use zlib 1.2.3
2016-04-17 01:08:14 41602 [Note] InnoDB: Using Linux native AIO
2016-04-17 01:08:14 41602 [Note] InnoDB: Using CPU crc32 instructions
2016-04-17 01:08:14 41602 [Note] InnoDB: Initializing buffer pool, size = 40.0G
2016-04-17 01:08:17 41602 [Note] InnoDB: Completed initialization of buffer pool
2016-04-17 01:08:17 41602 [Note] InnoDB: Highest supported file format is Barracuda.
2016-04-17 01:08:17 41602 [Note] InnoDB: Log scan progressed past the checkpoint lsn 1742971009859
2016-04-17 01:08:17 41602 [Note] InnoDB: Database was not shutdown normally!
2016-04-17 01:08:17 41602 [Note] InnoDB: Starting crash recovery.
2016-04-17 01:08:17 41602 [Note] InnoDB: Reading tablespace information from the .ibd files...
2016-04-17 01:08:23 41602 [Note] InnoDB: Restoring possible half-written data pages
2016-04-17 01:08:23 41602 [Note] InnoDB: from the doublewrite buffer...
...

How to repeat:
?
[18 Apr 2016 3:17] MySQL Verification Team
Looks like:
  Bug 22996488 - CRASH IN FTS_SYNC_INDEX WHEN DOING DDL IN A LOOP
which is fixed in 5.6.31 and is a regression from:
  BUG#22516559 MYSQL INSTANCE STALLS WHEN SYNCING FTS INDEX
[18 Apr 2016 15:46] MySQL Verification Team
Hi Mr. Niepraschk,

Your bug report looks very much an internally reported bug. That duplicate bug was fixed in 5.6.30.

Hence, please, use latest 5.6 release and let us know if the assertion persists. We suspect that this bug is simply, already fixed.

Thanks a lot in advance.
[18 Apr 2016 15:53] Nico Niepraschk
Yes, the assertion occured after (!) updating to version 5.6.30.

Before the update we ran version 5.6.29 and never had this problem.
[18 Apr 2016 16:08] MySQL Verification Team
Hi Mr. Niepraschk,

You have not understood my reply. I strongly suspect that a bug that you have reported is fixed in the version 5.6.31.

So, please, wait until it comes out and test everything again. We do not yet know when will it be out.

Thanks in advance.
[27 Apr 2016 9:19] MySQL Verification Team
Bug #81207 marked as duplicate of this
[3 May 2016 10:36] MySQL Verification Team
Bug #81289 marked as duplicate of this
[19 May 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".