Description:
160426 05:45:06 mysqld_safe mysqld from pid file /spare/u00/mysqldata/zta1gfc001.webex.com.pid ended
160426 05:53:31 mysqld_safe Starting mysqld daemon with databases from /spare/u00/mysqldata
2016-04-26 05:53:31 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2016-04-26 05:53:31 0 [Note] /usr/sbin/mysqld (mysqld 5.6.27-log) starting as process 29140 ...
2016-04-26 05:53:31 29140 [Note] Plugin 'FEDERATED' is disabled.
2016-04-26 05:53:31 29140 [Note] InnoDB: Using atomics to ref count buffer pool pages
2016-04-26 05:53:31 29140 [Note] InnoDB: The InnoDB memory heap is disabled
2016-04-26 05:53:31 29140 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2016-04-26 05:53:31 29140 [Note] InnoDB: Memory barrier is not used
2016-04-26 05:53:31 29140 [Note] InnoDB: Compressed tables use zlib 1.2.3
2016-04-26 05:53:31 29140 [Note] InnoDB: Using Linux native AIO
2016-04-26 05:53:31 29140 [Note] InnoDB: Using CPU crc32 instructions
2016-04-26 05:53:31 29140 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2016-04-26 05:53:31 29140 [Note] InnoDB: Completed initialization of buffer pool
2016-04-26 05:53:31 29140 [Note] InnoDB: Highest supported file format is Barracuda.
2016-04-26 05:53:32 7f3888219720 InnoDB: Assertion failure in thread 139880778798880 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.
05:53:32 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=131072
max_used_connections=0
max_threads=1500
thread_count=0
connection_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 603387 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)[0x8ddb85]
/usr/sbin/mysqld(handle_fatal_signal+0x494)[0x665b44]
/lib64/libpthread.so.0(+0xf710)[0x7f3887dfa710]
/lib64/libc.so.6(gsignal+0x35)[0x7f388689c625]
/lib64/libc.so.6(abort+0x175)[0x7f388689de05]
/usr/sbin/mysqld[0x9e5149]
/usr/sbin/mysqld[0x9e749a]
/usr/sbin/mysqld(_Z7yyparsev+0x994)[0xb02da4]
/usr/sbin/mysqld[0x9e57f5]
/usr/sbin/mysqld[0x9eb548]
/usr/sbin/mysqld[0xa126ac]
/usr/sbin/mysqld[0xa13919]
/usr/sbin/mysqld[0x9bc5ba]
/usr/sbin/mysqld[0xa3af74]
/usr/sbin/mysqld[0x980fed]
/usr/sbin/mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x48)[0x5a9608]
/usr/sbin/mysqld[0x6ef341]
/usr/sbin/mysqld(_Z11plugin_initPiPPci+0xbb6)[0x6f2de6]
/usr/sbin/mysqld[0x59c008]
/usr/sbin/mysqld(_Z11mysqld_mainiPPc+0x425)[0x5a1085]
/lib64/libc.so.6(__libc_start_main+0xfd)[0x7f3886888d5d]
/usr/sbin/mysqld[0x592f65]
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.
160426 05:53:32 mysqld_safe mysqld from pid file /spare/u00/mysqldata/zta1gfc001.webex.com.pid ended
How to repeat:
No, but can reproduce every time in one server.
Suggested fix:
None
