Broken forklift -- 5.5.50 > 5.6.31

mysqld.log

 160719 09:05:47 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql/data
2016-07-19 09:05:47 0 [Warning] Using unique option prefix key_buffer instead of key_buffer_size is deprecated and will be removed in a future release. Please use the full name instead.
2016-07-19 09:05:47 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2016-07-19 09:05:47 0 [Note] /usr/sbin/mysqld (mysqld 5.6.31) starting as process 63750 ...
2016-07-19 09:05:47 63750 [Note] Plugin 'FEDERATED' is disabled.
2016-07-19 09:05:47 7f70474f8720 InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
2016-07-19 09:05:47 63750 [Note] InnoDB: Using atomics to ref count buffer pool pages
2016-07-19 09:05:47 63750 [Note] InnoDB: The InnoDB memory heap is disabled
2016-07-19 09:05:47 63750 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2016-07-19 09:05:47 63750 [Note] InnoDB: Memory barrier is not used
2016-07-19 09:05:47 63750 [Note] InnoDB: Compressed tables use zlib 1.2.3
2016-07-19 09:05:47 63750 [Note] InnoDB: Using Linux native AIO
2016-07-19 09:05:47 63750 [Note] InnoDB: Using CPU crc32 instructions
2016-07-19 09:05:47 63750 [Note] InnoDB: Initializing buffer pool, size = 26.0G
2016-07-19 09:05:48 63750 [Note] InnoDB: Completed initialization of buffer pool
2016-07-19 09:05:49 63750 [Note] InnoDB: Highest supported file format is Barracuda.
2016-07-19 09:05:49 7f70474f8720  InnoDB: Operating system error number 2 in a file operation.
InnoDB: The error means the system cannot find the path specified.
InnoDB: If you are installing InnoDB, remember that you must create
InnoDB: directories yourself, InnoDB does not create them.
2016-07-19 09:05:49 63750 [ERROR] InnoDB: Could not find a valid tablespace file for 'foo/bar'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2016-07-19 09:05:49 63750 [ERROR] InnoDB: Tablespace open failed for '"foo"."bar"', ignored.
2016-07-19 09:05:49 7f70474f8720  InnoDB: Operating system error number 2 in a file operation.
InnoDB: The error means the system cannot find the path specified.
InnoDB: If you are installing InnoDB, remember that you must create
InnoDB: directories yourself, InnoDB does not create them.
2016-07-19 09:05:49 63750 [ERROR] InnoDB: Could not find a valid tablespace file for 'mysql_tmp/#sql475e_2_3'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2016-07-19 09:05:49 63750 [ERROR] InnoDB: Tablespace open failed for '"mysql_tmp"."#sql475e_2_3"', ignored.
2016-07-19 09:05:49 7f70474f8720  InnoDB: Assertion failure in thread 140120209458976 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.
16:05:49 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=1073741824
read_buffer_size=10485760
max_used_connections=0
max_threads=500
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 = 11294974 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)[0x8e1f85]
/usr/sbin/mysqld(handle_fatal_signal+0x494)[0x666ca4]
/lib64/libpthread.so.0[0x323de0f7e0]
/lib64/libc.so.6(gsignal+0x35)[0x323da32625]
/lib64/libc.so.6(abort+0x175)[0x323da33e05]
/usr/sbin/mysqld[0x9a94d9]
/usr/sbin/mysqld[0x9ab9fa]
/usr/sbin/mysqld(_Z7yyparsev+0x994)[0xac9c94]
/usr/sbin/mysqld[0x9aa725]
/usr/sbin/mysqld[0x9af8b8]
/usr/sbin/mysqld[0x9d7434]
/usr/sbin/mysqld[0x9d8679]
/usr/sbin/mysqld[0x9806da]
/usr/sbin/mysqld[0xa0023d]
/usr/sbin/mysqld[0x9448cd]
/usr/sbin/mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x48)[0x5aa8d8]
/usr/sbin/mysqld[0x6f0091]
/usr/sbin/mysqld(_Z11plugin_initPiPPci+0xbb6)[0x6f3ef6]
/usr/sbin/mysqld[0x59cde8]
/usr/sbin/mysqld(_Z11mysqld_mainiPPc+0x425)[0x5a2005]
/lib64/libc.so.6(__libc_start_main+0xfd)[0x323da1ed5d]
/usr/sbin/mysqld[0x593b55]
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.
160719 09:05:49 mysqld_safe mysqld from pid file /var/lib/mysql/data/p-xxxbak-101. pid ended