System 7 64 - bit version of centos, start the mysql error, the beginning is can normal boot after installed, then unload the heavy, cannot be launched,
The log is as follows:
180430 10:09:59 mysqld_safe Logging to '/var/log/mysqld. Log'.
180430 10:09:59 mysqld_safe Starting mysqld daemon with databases from/var/lib/mysql
The 2018-04-30 10:10:00 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Do use - explicit_defaults_for_timestamp server option (see documentation for more details).
The 2018-04-30 10:10:00 0 [Note]/usr/sbin/mysqld (mysqld 5.6.40) starting as the process of 10818...
The 10818 10:10:00 2018-04-30 [Warning] Buffered Warning: Changed limits: max_open_files: 1024 (5000) requested

The 10818 10:10:00 2018-04-30 [Warning] Buffered Warning: Changed limits: table_open_cache: 431 (2000) requested

The 10818 10:10:00 2018-04-30 [Note] the Plugin 'FEDERATED is disabled.
The/usr/sbin/mysqld: Unknown storage engine 'InnoDB'
The 10818 10:10:00 2018-04-30 [ERROR] Can 't open the mysql. The plugin table. Both Please run mysql_upgrade to create it.
The 2018-04-30 10:10:00 10818 [Note] InnoDB: Using atomics to ref count buffer pool pages
The 2018-04-30 10:10:00 10818 InnoDB [Note] : The InnoDB heap memory is disabled
The 2018-04-30 10:10:00 10818 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2018-04-30 10:10:00 10818 InnoDB [Note] : the Memory barrier is not 2
The 2018-04-30 10:10:00 10818 [Note] InnoDB: Compressed tables use zlib 1.2.3
The 2018-04-30 10:10:00 10818 [Note] InnoDB: Using Linux native AIO
The 2018-04-30 10:10:00 10818 [Note] InnoDB: Using CPU crc32 instructions
The 2018-04-30 10:10:00 10818 [Note] InnoDB: Initializing buffer pool, size=128.0 M
The 2018-04-30 10:10:00 InnoDB [Note] : 10818 Completed initialization of buffer pool
The 2018-04-30 10:10:00 10818 [Note] InnoDB: Highest supported file format is Barracuda.
The 10818 10:10:00 2018-04-30 [Note] InnoDB: The log sequence Numbers 2589937 and 2589937 in ibdata files do not match The log sequence number 2590220 in The ib_logfiles!
The 10818 10:10:00 2018-04-30 [Note] InnoDB: the Database was not shutdown normally!
The 2018-04-30 10:10:00 10818 [Note] InnoDB: Starting crash recovery.
The 2018-04-30 10:10:00 10818 [Note] InnoDB: Reading in tablespace information from the. Ibd files...
The 2018-04-30 10:10:00 10818 [Note] InnoDB: Restoring possible half - written data pages
The 2018-04-30 10:10:00 10818 [Note] InnoDB: from the doublewrite buffer...
InnoDB: wrong number of columns in SYS_INDEXES record
InnoDB: wrong number of columns in SYS_INDEXES record
InnoDB: wrong number of columns in SYS_INDEXES record
InnoDB: wrong number of columns in SYS_INDEXES record
InnoDB: wrong number of columns in SYS_INDEXES record
02:10:00 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 under 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=151
Thread_count=0
Connection_count=0
It is possible that mysqld could use one
Key_buffer_size + (read_buffer_size + sort_buffer_size) * max_threads=68108 K bytes of memory
Hope that 's ok. If not, decrease some variables in the equation.

Thread pointer: 0 x0
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 0 x40000
The/usr/sbin/mysqld (my_print_stacktrace + 0 x3b) x8e9ceb [0]
The/usr/sbin/mysqld (handle_fatal_signal + 0 x491) x675ca1 [0]
(+/lib64/libpthreads. So. 0 0 xf5e0) x7f5c9aa765e0 [0]
The/usr/sbin/mysqld xa6f8d8 [0]
The/usr/sbin/mysqld xa71819 [0]
The/usr/sbin/mysqld x9dda11 [0]
The/usr/sbin/mysqld x91b298 [0]
The/usr/sbin/mysqld (_Z24ha_initialize_handlertonP13st_plugin_int + 0 x48) x5b6028 [0]
The/usr/sbin/mysqld x6fe4e0 [0]
The/usr/sbin/mysqld (_Z11plugin_initPiPPci + 0 x940) x704cb0 [0]
The/usr/sbin/mysqld (_Z11mysqld_mainiPPc + 0 x8ad) x5af9ed [0]
/lib64/libc. So. 6 (__libc_start_main + 0 xf5) x7f5c9965cc05 [0]
The/usr/sbin/mysqld x5a24bd [0]
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.
180430 10:10:00 mysqld_safe mysqld from pid file/var/run/mysqld/mysqld. Pid ended
180430 10:12:33 mysqld_safe Logging to '/var/log/mysqld. Log'.
180430 10:12:33 mysqld_safe Starting mysqld daemon with databases from/var/lib/mysql
nullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnullnull