在我的环境中有一个装在VMware的RHEL上的MySQL.由于某些原因,我不得不将整个物理机硬关机,因此,造成了MySQL的Crash.

在物理机重新启动后,Linux系统起来没有问题,但是MySQL的启动却报错了.

具体内容如下:

启动服务:

[root@mysql02 log]# service mysqld start
Redirecting to /bin/systemctl start mysqld.service
Job for mysqld.service failed because the control process exited with error code. See "systemctl status mysqld.service" and "journalctl -xe" for details.
[root@mysql02 log]# 

可以看到,上面报错了.

看看报错信息吧:

[root@mysql02 log]# journalctl -xe
-- Unit session-143.scope has finished starting up.
-- 
-- The start-up result is done.
Oct 22 16:20:01 mysql02.adamhuan.com systemd[1]: Started Session 142 of user root.
-- Subject: Unit session-142.scope has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit session-142.scope has finished starting up.
-- 
-- The start-up result is done.
Oct 22 16:20:01 mysql02.adamhuan.com CROND[4733]: (root) CMD (sh /root/sync_index.sh )
Oct 22 16:20:01 mysql02.adamhuan.com CROND[4734]: (root) CMD (/usr/lib64/sa/sa1 1 1)
Oct 22 16:20:05 mysql02.adamhuan.com postfix/pickup[4107]: 1401A13A171: uid=0 from=<root
Oct 22 16:20:05 mysql02.adamhuan.com postfix/cleanup[4751]: 1401A13A171: message-id=<201
Oct 22 16:20:05 mysql02.adamhuan.com postfix/qmgr[1436]: 1401A13A171: from=<root@mysql02
Oct 22 16:20:05 mysql02.adamhuan.com postfix/local[4754]: 1401A13A171: to=<root@mysql02.
Oct 22 16:20:05 mysql02.adamhuan.com postfix/qmgr[1436]: 1401A13A171: removed
[root@mysql02 log]# 

看看错误日志中的表现:

[root@mysql02 log]# cat /etc/my.cnf | grep error
log-error=/mysql_data/log/mysqld.log
log-error=/mysql_data/log/mysqld.log
[root@mysql02 log]# 
[root@mysql02 log]# pwd
/mysql_data/log
[root@mysql02 log]# 
[root@mysql02 log]# ls -ltr
total 1912
-rw-r----- 1 root  root  1837920 Oct 21 20:56 mysqld.log_20191021_2056
-rw-r----- 1 mysql mysql   38616 Oct 21 20:57 mysqld.log_20191022_1615
-rw-r--r-- 1 mysql mysql   77230 Oct 22 16:16 mysqld.log
[root@mysql02 log]# 
[root@mysql02 log]# cat mysqld.log | wc -l
910
[root@mysql02 log]# 

日志内容较长,所以,没有在命令行中[cat].
详情看下面的内容吧:

2019-10-22T08:16:09.281340Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2019-10-22T08:16:09.283671Z 0 [Note] /usr/sbin/mysqld (mysqld 5.7.27-log) starting as process 4253 ...
2019-10-22T08:16:09.288702Z 0 [Note] InnoDB: PUNCH HOLE support available
2019-10-22T08:16:09.288746Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2019-10-22T08:16:09.288756Z 0 [Note] InnoDB: Uses event mutexes
2019-10-22T08:16:09.288763Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2019-10-22T08:16:09.288770Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2019-10-22T08:16:09.288784Z 0 [Note] InnoDB: Using Linux native AIO
2019-10-22T08:16:09.289195Z 0 [Note] InnoDB: Number of pools: 1
2019-10-22T08:16:09.289401Z 0 [Note] InnoDB: Using CPU crc32 instructions
2019-10-22T08:16:09.292289Z 0 [Note] InnoDB: Initializing buffer pool, total size = 4G, instances = 8, chunk size = 128M
2019-10-22T08:16:09.639131Z 0 [Note] InnoDB: Completed initialization of buffer pool
2019-10-22T08:16:09.764766Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2019-10-22T08:16:09.779933Z 0 [Note] InnoDB: Highest supported file format is Barracuda.
2019-10-22T08:16:09.883054Z 0 [Note] InnoDB: Log scan progressed past the checkpoint lsn 89665825
2019-10-22T08:16:09.883125Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 89665834
2019-10-22T08:16:09.883136Z 0 [Note] InnoDB: Database was not shutdown normally!
2019-10-22T08:16:09.883144Z 0 [Note] InnoDB: Starting crash recovery.
2019-10-22T08:16:10.031214Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=5] log sequence number 89667292 is in the future! Current system log sequence number 89665843.
2019-10-22T08:16:10.031263Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2019-10-22T08:16:10.055008Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=219] log sequence number 89666290 is in the future! Current system log sequence number 89665843.
2019-10-22T08:16:10.055033Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2019-10-22T08:16:10.055371Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=488] log sequence number 89666290 is in the future! Current system log sequence number 89665843.
2019-10-22T08:16:10.055389Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2019-10-22T08:16:10.055610Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=220] log sequence number 89666791 is in the future! Current system log sequence number 89665843.
2019-10-22T08:16:10.055625Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2019-10-22T08:16:10.055907Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=480] log sequence number 89666791 is in the future! Current system log sequence number 89665843.
2019-10-22T08:16:10.055922Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2019-10-22T08:16:10.056164Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=221] log sequence number 89667292 is in the future! Current system log sequence number 89665843.
2019-10-22T08:16:10.056198Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2019-10-22T08:16:10.153945Z 0 [Note] InnoDB: Last MySQL binlog file position 0 15488347, file name mysql_binary_log.000006
2019-10-22T08:16:10.264389Z 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
2019-10-22T08:16:10.264430Z 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2019-10-22T08:16:10.264492Z 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2019-10-22T08:16:10.287763Z 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
2019-10-22T08:16:10.288909Z 0 [Note] InnoDB: 96 redo rollback segment(s) found. 96 redo rollback segment(s) are active.
2019-10-22T08:16:10.289032Z 0 [Note] InnoDB: 32 non-redo rollback segment(s) are active.
2019-10-22T08:16:10.289438Z 0 [Note] InnoDB: Waiting for purge to start
2019-10-22 01:16:10 0x7f9091593700  InnoDB: Assertion failure in thread 140258890561280 in file fut0lst.ic line 85
InnoDB: Failing assertion: addr.page == FIL_NULL || addr.boffset >= FIL_PAGE_DATA
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.7/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
08:16:10 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.
Attempting to collect some information that could help diagnose the problem.
As this is a crash and something is definitely wrong, the information
collection process might fail.

key_buffer_size=8388608
read_buffer_size=2097152
max_used_connections=0
max_threads=151
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 = 1556452 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x7f90680008c0
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 = 7f9091592db0 thread_stack 0x40000
/usr/sbin/mysqld(my_print_stacktrace+0x3b)[0xf080bb]
/usr/sbin/mysqld(handle_fatal_signal+0x461)[0x7b9ce1]
/lib64/libpthread.so.0(+0xf630)[0x7f91b067b630]
/lib64/libc.so.6(gsignal+0x37)[0x7f91af065377]
/lib64/libc.so.6(abort+0x148)[0x7f91af066a68]
/usr/sbin/mysqld[0x789ff8]
/usr/sbin/mysqld[0x789b08]
/usr/sbin/mysqld[0x10a2a95]
/usr/sbin/mysqld[0x10a4b98]
/usr/sbin/mysqld(_Z9trx_purgemmb+0x3c9)[0x10a7399]
/usr/sbin/mysqld(srv_purge_coordinator_thread+0xded)[0x107f9bd]
/lib64/libpthread.so.0(+0x7ea5)[0x7f91b0673ea5]
/lib64/libc.so.6(clone+0x6d)[0x7f91af12d8cd]

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0): Connection ID (thread ID): 0
Status: NOT_KILLED

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.
2019-10-22T08:16:11.550590Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2019-10-22T08:16:11.552774Z 0 [Note] /usr/sbin/mysqld (mysqld 5.7.27-log) starting as process 4303 ...
2019-10-22T08:16:11.557751Z 0 [Note] InnoDB: PUNCH HOLE support available
2019-10-22T08:16:11.557794Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2019-10-22T08:16:11.557803Z 0 [Note] InnoDB: Uses event mutexes
2019-10-22T08:16:11.557824Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2019-10-22T08:16:11.557832Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2019-10-22T08:16:11.557847Z 0 [Note] InnoDB: Using Linux native AIO
2019-10-22T08:16:11.558268Z 0 [Note] InnoDB: Number of pools: 1
2019-10-22T08:16:11.558452Z 0 [Note] InnoDB: Using CPU crc32 instructions
2019-10-22T08:16:11.561368Z 0 [Note] InnoDB: Initializing buffer pool, total size = 4G, instances = 8, chunk size = 128M
2019-10-22T08:16:11.901409Z 0 [Note] InnoDB: Completed initialization of buffer pool
2019-10-22T08:16:11.934717Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2019-10-22T08:16:11.949426Z 0 [Note] InnoDB: Highest supported file format is Barracuda.
2019-10-22T08:16:11.971304Z 0 [Note] InnoDB: Log scan progressed past the checkpoint lsn 89665825
2019-10-22T08:16:11.971387Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 89665834
2019-10-22T08:16:11.971397Z 0 [Note] InnoDB: Database was not shutdown normally!
2019-10-22T08:16:11.971419Z 0 [Note] InnoDB: Starting crash recovery.
2019-10-22T08:16:12.069061Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=5] log sequence number 89667292 is in the future! Current system log sequence number 89665843.
2019-10-22T08:16:12.069125Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2019-10-22T08:16:12.123307Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=219] log sequence number 89666290 is in the future! Current system log sequence number 89665843.
2019-10-22T08:16:12.123364Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2019-10-22T08:16:12.123707Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=488] log sequence number 89666290 is in the future! Current system log sequence number 89665843.
2019-10-22T08:16:12.123726Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2019-10-22T08:16:12.123944Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=220] log sequence number 89666791 is in the future! Current system log sequence number 89665843.
2019-10-22T08:16:12.123962Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2019-10-22T08:16:12.124322Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=480] log sequence number 89666791 is in the future! Current system log sequence number 89665843.
2019-10-22T08:16:12.124341Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2019-10-22T08:16:12.124536Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=221] log sequence number 89667292 is in the future! Current system log sequence number 89665843.
2019-10-22T08:16:12.124554Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2019-10-22T08:16:12.229285Z 0 [Note] InnoDB: Last MySQL binlog file position 0 15488347, file name mysql_binary_log.000006
2019-10-22T08:16:12.338530Z 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
2019-10-22T08:16:12.338563Z 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2019-10-22T08:16:12.338625Z 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2019-10-22T08:16:12.360329Z 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
2019-10-22T08:16:12.361298Z 0 [Note] InnoDB: 96 redo rollback segment(s) found. 96 redo rollback segment(s) are active.
2019-10-22T08:16:12.361317Z 0 [Note] InnoDB: 32 non-redo rollback segment(s) are active.
2019-10-22T08:16:12.361684Z 0 [Note] InnoDB: Waiting for purge to start
2019-10-22 01:16:12 0x7fbd8eb92700  InnoDB: Assertion failure in thread 140452120045312 in file fut0lst.ic line 85
InnoDB: Failing assertion: addr.page == FIL_NULL || addr.boffset >= FIL_PAGE_DATA
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.7/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
08:16:12 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.
Attempting to collect some information that could help diagnose the problem.
As this is a crash and something is definitely wrong, the information
collection process might fail.

key_buffer_size=8388608
read_buffer_size=2097152
max_used_connections=0
max_threads=151
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 = 1556452 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x7fbd6c0008c0
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 = 7fbd8eb91db0 thread_stack 0x40000
/usr/sbin/mysqld(my_print_stacktrace+0x3b)[0xf080bb]
/usr/sbin/mysqld(handle_fatal_signal+0x461)[0x7b9ce1]
/lib64/libpthread.so.0(+0xf630)[0x7fbeae122630]
/lib64/libc.so.6(gsignal+0x37)[0x7fbeacb0c377]
/lib64/libc.so.6(abort+0x148)[0x7fbeacb0da68]
/usr/sbin/mysqld[0x789ff8]
/usr/sbin/mysqld[0x789b08]
/usr/sbin/mysqld[0x10a2a95]
/usr/sbin/mysqld[0x10a4b98]
/usr/sbin/mysqld(_Z9trx_purgemmb+0x3c9)[0x10a7399]
/usr/sbin/mysqld(srv_purge_coordinator_thread+0xded)[0x107f9bd]
/lib64/libpthread.so.0(+0x7ea5)[0x7fbeae11aea5]
/lib64/libc.so.6(clone+0x6d)[0x7fbeacbd48cd]

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0): Connection ID (thread ID): 0
Status: NOT_KILLED

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.
2019-10-22T08:16:13.789947Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2019-10-22T08:16:13.792137Z 0 [Note] /usr/sbin/mysqld (mysqld 5.7.27-log) starting as process 4354 ...
2019-10-22T08:16:13.796860Z 0 [Note] InnoDB: PUNCH HOLE support available
2019-10-22T08:16:13.796910Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2019-10-22T08:16:13.796919Z 0 [Note] InnoDB: Uses event mutexes
2019-10-22T08:16:13.796933Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2019-10-22T08:16:13.796943Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2019-10-22T08:16:13.796955Z 0 [Note] InnoDB: Using Linux native AIO
2019-10-22T08:16:13.797359Z 0 [Note] InnoDB: Number of pools: 1
2019-10-22T08:16:13.797515Z 0 [Note] InnoDB: Using CPU crc32 instructions
2019-10-22T08:16:13.800499Z 0 [Note] InnoDB: Initializing buffer pool, total size = 4G, instances = 8, chunk size = 128M
2019-10-22T08:16:14.185171Z 0 [Note] InnoDB: Completed initialization of buffer pool
2019-10-22T08:16:14.256850Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2019-10-22T08:16:14.272635Z 0 [Note] InnoDB: Highest supported file format is Barracuda.
2019-10-22T08:16:14.294405Z 0 [Note] InnoDB: Log scan progressed past the checkpoint lsn 89665825
2019-10-22T08:16:14.294484Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 89665834
2019-10-22T08:16:14.294496Z 0 [Note] InnoDB: Database was not shutdown normally!
2019-10-22T08:16:14.294505Z 0 [Note] InnoDB: Starting crash recovery.
2019-10-22T08:16:14.409265Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=5] log sequence number 89667292 is in the future! Current system log sequence number 89665843.
2019-10-22T08:16:14.409321Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2019-10-22T08:16:14.461411Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=219] log sequence number 89666290 is in the future! Current system log sequence number 89665843.
2019-10-22T08:16:14.461437Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2019-10-22T08:16:14.461800Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=488] log sequence number 89666290 is in the future! Current system log sequence number 89665843.
2019-10-22T08:16:14.461819Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2019-10-22T08:16:14.462024Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=220] log sequence number 89666791 is in the future! Current system log sequence number 89665843.
2019-10-22T08:16:14.462042Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2019-10-22T08:16:14.462353Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=480] log sequence number 89666791 is in the future! Current system log sequence number 89665843.
2019-10-22T08:16:14.462371Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2019-10-22T08:16:14.462560Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=221] log sequence number 89667292 is in the future! Current system log sequence number 89665843.
2019-10-22T08:16:14.462577Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2019-10-22T08:16:14.556255Z 0 [Note] InnoDB: Last MySQL binlog file position 0 15488347, file name mysql_binary_log.000006
2019-10-22T08:16:14.665025Z 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
2019-10-22T08:16:14.665046Z 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2019-10-22T08:16:14.665114Z 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2019-10-22T08:16:14.687001Z 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
2019-10-22T08:16:14.688453Z 0 [Note] InnoDB: 96 redo rollback segment(s) found. 96 redo rollback segment(s) are active.
2019-10-22T08:16:14.688483Z 0 [Note] InnoDB: 32 non-redo rollback segment(s) are active.
2019-10-22T08:16:14.688904Z 0 [Note] InnoDB: Waiting for purge to start
2019-10-22 01:16:14 0x7f324d6d0700  InnoDB: Assertion failure in thread 139854024083200 in file fut0lst.ic line 85
InnoDB: Failing assertion: addr.page == FIL_NULL || addr.boffset >= FIL_PAGE_DATA
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.7/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
08:16: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.
Attempting to collect some information that could help diagnose the problem.
As this is a crash and something is definitely wrong, the information
collection process might fail.

key_buffer_size=8388608
read_buffer_size=2097152
max_used_connections=0
max_threads=151
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 = 1556452 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x7f32240008c0
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 = 7f324d6cfdb0 thread_stack 0x40000
/usr/sbin/mysqld(my_print_stacktrace+0x3b)[0xf080bb]
/usr/sbin/mysqld(handle_fatal_signal+0x461)[0x7b9ce1]
/lib64/libpthread.so.0(+0xf630)[0x7f336cc60630]
/lib64/libc.so.6(gsignal+0x37)[0x7f336b64a377]
/lib64/libc.so.6(abort+0x148)[0x7f336b64ba68]
/usr/sbin/mysqld[0x789ff8]
/usr/sbin/mysqld[0x789b08]
/usr/sbin/mysqld[0x10a2a95]
/usr/sbin/mysqld[0x10a4b98]
/usr/sbin/mysqld(_Z9trx_purgemmb+0x3c9)[0x10a7399]
/usr/sbin/mysqld(srv_purge_coordinator_thread+0xded)[0x107f9bd]
/lib64/libpthread.so.0(+0x7ea5)[0x7f336cc58ea5]
/lib64/libc.so.6(clone+0x6d)[0x7f336b7128cd]

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0): Connection ID (thread ID): 0
Status: NOT_KILLED

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.
2019-10-22T08:16:15.956416Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2019-10-22T08:16:15.958393Z 0 [Note] /usr/sbin/mysqld (mysqld 5.7.27-log) starting as process 4404 ...
2019-10-22T08:16:15.962936Z 0 [Note] InnoDB: PUNCH HOLE support available
2019-10-22T08:16:15.962981Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2019-10-22T08:16:15.962991Z 0 [Note] InnoDB: Uses event mutexes
2019-10-22T08:16:15.963003Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2019-10-22T08:16:15.963012Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2019-10-22T08:16:15.963026Z 0 [Note] InnoDB: Using Linux native AIO
2019-10-22T08:16:15.963405Z 0 [Note] InnoDB: Number of pools: 1
2019-10-22T08:16:15.963594Z 0 [Note] InnoDB: Using CPU crc32 instructions
2019-10-22T08:16:15.966282Z 0 [Note] InnoDB: Initializing buffer pool, total size = 4G, instances = 8, chunk size = 128M
2019-10-22T08:16:16.271110Z 0 [Note] InnoDB: Completed initialization of buffer pool
2019-10-22T08:16:16.302448Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2019-10-22T08:16:16.317661Z 0 [Note] InnoDB: Highest supported file format is Barracuda.
2019-10-22T08:16:16.339073Z 0 [Note] InnoDB: Log scan progressed past the checkpoint lsn 89665825
2019-10-22T08:16:16.339173Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 89665834
2019-10-22T08:16:16.339185Z 0 [Note] InnoDB: Database was not shutdown normally!
2019-10-22T08:16:16.339194Z 0 [Note] InnoDB: Starting crash recovery.
2019-10-22T08:16:16.374484Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=5] log sequence number 89667292 is in the future! Current system log sequence number 89665843.
2019-10-22T08:16:16.374530Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2019-10-22T08:16:16.399408Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=219] log sequence number 89666290 is in the future! Current system log sequence number 89665843.
2019-10-22T08:16:16.399432Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2019-10-22T08:16:16.399779Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=488] log sequence number 89666290 is in the future! Current system log sequence number 89665843.
2019-10-22T08:16:16.399796Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2019-10-22T08:16:16.400162Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=220] log sequence number 89666791 is in the future! Current system log sequence number 89665843.
2019-10-22T08:16:16.400182Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2019-10-22T08:16:16.400682Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=480] log sequence number 89666791 is in the future! Current system log sequence number 89665843.
2019-10-22T08:16:16.400700Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2019-10-22T08:16:16.400905Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=221] log sequence number 89667292 is in the future! Current system log sequence number 89665843.
2019-10-22T08:16:16.400922Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2019-10-22T08:16:16.504358Z 0 [Note] InnoDB: Last MySQL binlog file position 0 15488347, file name mysql_binary_log.000006
2019-10-22T08:16:16.612833Z 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
2019-10-22T08:16:16.612856Z 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2019-10-22T08:16:16.612925Z 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2019-10-22T08:16:16.646337Z 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
2019-10-22T08:16:16.647331Z 0 [Note] InnoDB: 96 redo rollback segment(s) found. 96 redo rollback segment(s) are active.
2019-10-22T08:16:16.647353Z 0 [Note] InnoDB: 32 non-redo rollback segment(s) are active.
2019-10-22T08:16:16.647772Z 0 [Note] InnoDB: Waiting for purge to start
2019-10-22 01:16:16 0x7f3f883c5700  InnoDB: Assertion failure in thread 139910845323008 in file fut0lst.ic line 85
InnoDB: Failing assertion: addr.page == FIL_NULL || addr.boffset >= FIL_PAGE_DATA
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.7/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
08:16:16 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.
Attempting to collect some information that could help diagnose the problem.
As this is a crash and something is definitely wrong, the information
collection process might fail.

key_buffer_size=8388608
read_buffer_size=2097152
max_used_connections=0
max_threads=151
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 = 1556452 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x7f3f600008c0
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 = 7f3f883c4db0 thread_stack 0x40000
/usr/sbin/mysqld(my_print_stacktrace+0x3b)[0xf080bb]
/usr/sbin/mysqld(handle_fatal_signal+0x461)[0x7b9ce1]
/lib64/libpthread.so.0(+0xf630)[0x7f40a7955630]
/lib64/libc.so.6(gsignal+0x37)[0x7f40a633f377]
/lib64/libc.so.6(abort+0x148)[0x7f40a6340a68]
/usr/sbin/mysqld[0x789ff8]
/usr/sbin/mysqld[0x789b08]
/usr/sbin/mysqld[0x10a2a95]
/usr/sbin/mysqld[0x10a4b98]
/usr/sbin/mysqld(_Z9trx_purgemmb+0x3c9)[0x10a7399]
/usr/sbin/mysqld(srv_purge_coordinator_thread+0xded)[0x107f9bd]
/lib64/libpthread.so.0(+0x7ea5)[0x7f40a794dea5]
/lib64/libc.so.6(clone+0x6d)[0x7f40a64078cd]

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0): Connection ID (thread ID): 0
Status: NOT_KILLED

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.
2019-10-22T08:16:18.041630Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2019-10-22T08:16:18.044001Z 0 [Note] /usr/sbin/mysqld (mysqld 5.7.27-log) starting as process 4454 ...
2019-10-22T08:16:18.048989Z 0 [Note] InnoDB: PUNCH HOLE support available
2019-10-22T08:16:18.049040Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2019-10-22T08:16:18.049049Z 0 [Note] InnoDB: Uses event mutexes
2019-10-22T08:16:18.049056Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2019-10-22T08:16:18.049063Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2019-10-22T08:16:18.049076Z 0 [Note] InnoDB: Using Linux native AIO
2019-10-22T08:16:18.049494Z 0 [Note] InnoDB: Number of pools: 1
2019-10-22T08:16:18.049662Z 0 [Note] InnoDB: Using CPU crc32 instructions
2019-10-22T08:16:18.052532Z 0 [Note] InnoDB: Initializing buffer pool, total size = 4G, instances = 8, chunk size = 128M
2019-10-22T08:16:18.378791Z 0 [Note] InnoDB: Completed initialization of buffer pool
2019-10-22T08:16:18.426820Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2019-10-22T08:16:18.441878Z 0 [Note] InnoDB: Highest supported file format is Barracuda.
2019-10-22T08:16:18.462575Z 0 [Note] InnoDB: Log scan progressed past the checkpoint lsn 89665825
2019-10-22T08:16:18.462660Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 89665834
2019-10-22T08:16:18.462671Z 0 [Note] InnoDB: Database was not shutdown normally!
2019-10-22T08:16:18.462680Z 0 [Note] InnoDB: Starting crash recovery.
2019-10-22T08:16:18.482160Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=5] log sequence number 89667292 is in the future! Current system log sequence number 89665843.
2019-10-22T08:16:18.482224Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2019-10-22T08:16:18.507394Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=219] log sequence number 89666290 is in the future! Current system log sequence number 89665843.
2019-10-22T08:16:18.507449Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2019-10-22T08:16:18.507780Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=488] log sequence number 89666290 is in the future! Current system log sequence number 89665843.
2019-10-22T08:16:18.507798Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2019-10-22T08:16:18.508006Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=220] log sequence number 89666791 is in the future! Current system log sequence number 89665843.
2019-10-22T08:16:18.508023Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2019-10-22T08:16:18.508354Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=480] log sequence number 89666791 is in the future! Current system log sequence number 89665843.
2019-10-22T08:16:18.508372Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2019-10-22T08:16:18.508591Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=221] log sequence number 89667292 is in the future! Current system log sequence number 89665843.
2019-10-22T08:16:18.508607Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2019-10-22T08:16:18.580342Z 0 [Note] InnoDB: Last MySQL binlog file position 0 15488347, file name mysql_binary_log.000006
2019-10-22T08:16:18.690471Z 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
2019-10-22T08:16:18.690508Z 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2019-10-22T08:16:18.690633Z 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2019-10-22T08:16:18.713980Z 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
2019-10-22T08:16:18.715177Z 0 [Note] InnoDB: 96 redo rollback segment(s) found. 96 redo rollback segment(s) are active.
2019-10-22T08:16:18.715212Z 0 [Note] InnoDB: 32 non-redo rollback segment(s) are active.
2019-10-22T08:16:18.715668Z 0 [Note] InnoDB: Waiting for purge to start
2019-10-22 01:16:18 0x7fc78918b700  InnoDB: Assertion failure in thread 140494975317760 in file fut0lst.ic line 85
InnoDB: Failing assertion: addr.page == FIL_NULL || addr.boffset >= FIL_PAGE_DATA
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.7/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
08:16:18 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.
Attempting to collect some information that could help diagnose the problem.
As this is a crash and something is definitely wrong, the information
collection process might fail.

key_buffer_size=8388608
read_buffer_size=2097152
max_used_connections=0
max_threads=151
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 = 1556452 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x7fc770000900
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 = 7fc78918adb0 thread_stack 0x40000
/usr/sbin/mysqld(my_print_stacktrace+0x3b)[0xf080bb]
/usr/sbin/mysqld(handle_fatal_signal+0x461)[0x7b9ce1]
/lib64/libpthread.so.0(+0xf630)[0x7fc8a8273630]
/lib64/libc.so.6(gsignal+0x37)[0x7fc8a6c5d377]
/lib64/libc.so.6(abort+0x148)[0x7fc8a6c5ea68]
/usr/sbin/mysqld[0x789ff8]
/usr/sbin/mysqld[0x789b08]
/usr/sbin/mysqld[0x10a2a95]
/usr/sbin/mysqld[0x10a4b98]
/usr/sbin/mysqld(_Z9trx_purgemmb+0x3c9)[0x10a7399]
/usr/sbin/mysqld(srv_purge_coordinator_thread+0xded)[0x107f9bd]
/lib64/libpthread.so.0(+0x7ea5)[0x7fc8a826bea5]
/lib64/libc.so.6(clone+0x6d)[0x7fc8a6d258cd]

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0): Connection ID (thread ID): 0
Status: NOT_KILLED

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.
2019-10-22T08:16:19.999015Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2019-10-22T08:16:20.001031Z 0 [Note] /usr/sbin/mysqld (mysqld 5.7.27-log) starting as process 4504 ...
2019-10-22T08:16:20.005634Z 0 [Note] InnoDB: PUNCH HOLE support available
2019-10-22T08:16:20.005762Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2019-10-22T08:16:20.005782Z 0 [Note] InnoDB: Uses event mutexes
2019-10-22T08:16:20.005790Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2019-10-22T08:16:20.005798Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2019-10-22T08:16:20.005815Z 0 [Note] InnoDB: Using Linux native AIO
2019-10-22T08:16:20.006211Z 0 [Note] InnoDB: Number of pools: 1
2019-10-22T08:16:20.006447Z 0 [Note] InnoDB: Using CPU crc32 instructions
2019-10-22T08:16:20.009511Z 0 [Note] InnoDB: Initializing buffer pool, total size = 4G, instances = 8, chunk size = 128M
2019-10-22T08:16:20.312240Z 0 [Note] InnoDB: Completed initialization of buffer pool
2019-10-22T08:16:20.345217Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2019-10-22T08:16:20.360287Z 0 [Note] InnoDB: Highest supported file format is Barracuda.
2019-10-22T08:16:20.380514Z 0 [Note] InnoDB: Log scan progressed past the checkpoint lsn 89665825
2019-10-22T08:16:20.380582Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 89665834
2019-10-22T08:16:20.380592Z 0 [Note] InnoDB: Database was not shutdown normally!
2019-10-22T08:16:20.380601Z 0 [Note] InnoDB: Starting crash recovery.
2019-10-22T08:16:20.423283Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=5] log sequence number 89667292 is in the future! Current system log sequence number 89665843.
2019-10-22T08:16:20.423353Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2019-10-22T08:16:20.480809Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=219] log sequence number 89666290 is in the future! Current system log sequence number 89665843.
2019-10-22T08:16:20.480905Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2019-10-22T08:16:20.481348Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=488] log sequence number 89666290 is in the future! Current system log sequence number 89665843.
2019-10-22T08:16:20.481367Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2019-10-22T08:16:20.481629Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=220] log sequence number 89666791 is in the future! Current system log sequence number 89665843.
2019-10-22T08:16:20.481660Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2019-10-22T08:16:20.481999Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=480] log sequence number 89666791 is in the future! Current system log sequence number 89665843.
2019-10-22T08:16:20.482016Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2019-10-22T08:16:20.482200Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=221] log sequence number 89667292 is in the future! Current system log sequence number 89665843.
2019-10-22T08:16:20.482217Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2019-10-22T08:16:20.608908Z 0 [Note] InnoDB: Last MySQL binlog file position 0 15488347, file name mysql_binary_log.000006
2019-10-22T08:16:20.718199Z 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
2019-10-22T08:16:20.718221Z 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2019-10-22T08:16:20.718280Z 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2019-10-22T08:16:20.740630Z 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
2019-10-22T08:16:20.741617Z 0 [Note] InnoDB: 96 redo rollback segment(s) found. 96 redo rollback segment(s) are active.
2019-10-22T08:16:20.741637Z 0 [Note] InnoDB: 32 non-redo rollback segment(s) are active.
2019-10-22T08:16:20.742009Z 0 [Note] InnoDB: Waiting for purge to start
2019-10-22 01:16:20 0x7f2894b95700  InnoDB: Assertion failure in thread 139812270593792 in file fut0lst.ic line 85
InnoDB: Failing assertion: addr.page == FIL_NULL || addr.boffset >= FIL_PAGE_DATA
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.7/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
08:16:20 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.
Attempting to collect some information that could help diagnose the problem.
As this is a crash and something is definitely wrong, the information
collection process might fail.

key_buffer_size=8388608
read_buffer_size=2097152
max_used_connections=0
max_threads=151
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 = 1556452 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x7f286c0008c0
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 = 7f2894b94db0 thread_stack 0x40000
/usr/sbin/mysqld(my_print_stacktrace+0x3b)[0xf080bb]
/usr/sbin/mysqld(handle_fatal_signal+0x461)[0x7b9ce1]
/lib64/libpthread.so.0(+0xf630)[0x7f29b4125630]
/lib64/libc.so.6(gsignal+0x37)[0x7f29b2b0f377]
/lib64/libc.so.6(abort+0x148)[0x7f29b2b10a68]
/usr/sbin/mysqld[0x789ff8]
/usr/sbin/mysqld[0x789b08]
/usr/sbin/mysqld[0x10a2a95]
/usr/sbin/mysqld[0x10a4b98]
/usr/sbin/mysqld(_Z9trx_purgemmb+0x3c9)[0x10a7399]
/usr/sbin/mysqld(srv_purge_coordinator_thread+0xded)[0x107f9bd]
/lib64/libpthread.so.0(+0x7ea5)[0x7f29b411dea5]
/lib64/libc.so.6(clone+0x6d)[0x7f29b2bd78cd]

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0): Connection ID (thread ID): 0
Status: NOT_KILLED

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.
2019-10-22T08:16:22.061282Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2019-10-22T08:16:22.062892Z 0 [Note] /usr/sbin/mysqld (mysqld 5.7.27-log) starting as process 4554 ...
2019-10-22T08:16:22.067916Z 0 [Note] InnoDB: PUNCH HOLE support available
2019-10-22T08:16:22.067958Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2019-10-22T08:16:22.067967Z 0 [Note] InnoDB: Uses event mutexes
2019-10-22T08:16:22.067974Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2019-10-22T08:16:22.067982Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2019-10-22T08:16:22.068010Z 0 [Note] InnoDB: Using Linux native AIO
2019-10-22T08:16:22.068452Z 0 [Note] InnoDB: Number of pools: 1
2019-10-22T08:16:22.068591Z 0 [Note] InnoDB: Using CPU crc32 instructions
2019-10-22T08:16:22.071360Z 0 [Note] InnoDB: Initializing buffer pool, total size = 4G, instances = 8, chunk size = 128M
2019-10-22T08:16:22.404026Z 0 [Note] InnoDB: Completed initialization of buffer pool
2019-10-22T08:16:22.434968Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2019-10-22T08:16:22.450016Z 0 [Note] InnoDB: Highest supported file format is Barracuda.
2019-10-22T08:16:22.470582Z 0 [Note] InnoDB: Log scan progressed past the checkpoint lsn 89665825
2019-10-22T08:16:22.470652Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 89665834
2019-10-22T08:16:22.470663Z 0 [Note] InnoDB: Database was not shutdown normally!
2019-10-22T08:16:22.470672Z 0 [Note] InnoDB: Starting crash recovery.
2019-10-22T08:16:22.491658Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=5] log sequence number 89667292 is in the future! Current system log sequence number 89665843.
2019-10-22T08:16:22.491717Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2019-10-22T08:16:22.515804Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=219] log sequence number 89666290 is in the future! Current system log sequence number 89665843.
2019-10-22T08:16:22.515831Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2019-10-22T08:16:22.516168Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=488] log sequence number 89666290 is in the future! Current system log sequence number 89665843.
2019-10-22T08:16:22.516187Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2019-10-22T08:16:22.516417Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=220] log sequence number 89666791 is in the future! Current system log sequence number 89665843.
2019-10-22T08:16:22.516434Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2019-10-22T08:16:22.516719Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=480] log sequence number 89666791 is in the future! Current system log sequence number 89665843.
2019-10-22T08:16:22.516764Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2019-10-22T08:16:22.516963Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=221] log sequence number 89667292 is in the future! Current system log sequence number 89665843.
2019-10-22T08:16:22.516980Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2019-10-22T08:16:22.588628Z 0 [Note] InnoDB: Last MySQL binlog file position 0 15488347, file name mysql_binary_log.000006
2019-10-22T08:16:22.698664Z 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
2019-10-22T08:16:22.698754Z 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2019-10-22T08:16:22.698829Z 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2019-10-22T08:16:22.721298Z 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
2019-10-22T08:16:22.722774Z 0 [Note] InnoDB: 96 redo rollback segment(s) found. 96 redo rollback segment(s) are active.
2019-10-22T08:16:22.722803Z 0 [Note] InnoDB: 32 non-redo rollback segment(s) are active.
2019-10-22T08:16:22.723161Z 0 [Note] InnoDB: Waiting for purge to start
2019-10-22 01:16:22 0x7fc6d2a74700  InnoDB: Assertion failure in thread 140491914430208 in file fut0lst.ic line 85
InnoDB: Failing assertion: addr.page == FIL_NULL || addr.boffset >= FIL_PAGE_DATA
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.7/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
08:16:22 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.
Attempting to collect some information that could help diagnose the problem.
As this is a crash and something is definitely wrong, the information
collection process might fail.

key_buffer_size=8388608
read_buffer_size=2097152
max_used_connections=0
max_threads=151
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 = 1556452 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x7fc6b40008c0
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 = 7fc6d2a73db0 thread_stack 0x40000
/usr/sbin/mysqld(my_print_stacktrace+0x3b)[0xf080bb]
/usr/sbin/mysqld(handle_fatal_signal+0x461)[0x7b9ce1]
/lib64/libpthread.so.0(+0xf630)[0x7fc7f2004630]
/lib64/libc.so.6(gsignal+0x37)[0x7fc7f09ee377]
/lib64/libc.so.6(abort+0x148)[0x7fc7f09efa68]
/usr/sbin/mysqld[0x789ff8]
/usr/sbin/mysqld[0x789b08]
/usr/sbin/mysqld[0x10a2a95]
/usr/sbin/mysqld[0x10a4b98]
/usr/sbin/mysqld(_Z9trx_purgemmb+0x3c9)[0x10a7399]
/usr/sbin/mysqld(srv_purge_coordinator_thread+0xded)[0x107f9bd]
/lib64/libpthread.so.0(+0x7ea5)[0x7fc7f1ffcea5]
/lib64/libc.so.6(clone+0x6d)[0x7fc7f0ab68cd]

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0): Connection ID (thread ID): 0
Status: NOT_KILLED

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.
2019-10-22T08:16:23.979482Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2019-10-22T08:16:23.981548Z 0 [Note] /usr/sbin/mysqld (mysqld 5.7.27-log) starting as process 4604 ...
2019-10-22T08:16:23.986203Z 0 [Note] InnoDB: PUNCH HOLE support available
2019-10-22T08:16:23.986245Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2019-10-22T08:16:23.986253Z 0 [Note] InnoDB: Uses event mutexes
2019-10-22T08:16:23.986261Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2019-10-22T08:16:23.986268Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2019-10-22T08:16:23.986293Z 0 [Note] InnoDB: Using Linux native AIO
2019-10-22T08:16:23.986743Z 0 [Note] InnoDB: Number of pools: 1
2019-10-22T08:16:23.986912Z 0 [Note] InnoDB: Using CPU crc32 instructions
2019-10-22T08:16:23.989815Z 0 [Note] InnoDB: Initializing buffer pool, total size = 4G, instances = 8, chunk size = 128M
2019-10-22T08:16:24.312957Z 0 [Note] InnoDB: Completed initialization of buffer pool
2019-10-22T08:16:24.345238Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2019-10-22T08:16:24.360809Z 0 [Note] InnoDB: Highest supported file format is Barracuda.
2019-10-22T08:16:24.380647Z 0 [Note] InnoDB: Log scan progressed past the checkpoint lsn 89665825
2019-10-22T08:16:24.380720Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 89665834
2019-10-22T08:16:24.380731Z 0 [Note] InnoDB: Database was not shutdown normally!
2019-10-22T08:16:24.380740Z 0 [Note] InnoDB: Starting crash recovery.
2019-10-22T08:16:24.401521Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=5] log sequence number 89667292 is in the future! Current system log sequence number 89665843.
2019-10-22T08:16:24.401560Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2019-10-22T08:16:24.425762Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=219] log sequence number 89666290 is in the future! Current system log sequence number 89665843.
2019-10-22T08:16:24.425813Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2019-10-22T08:16:24.426153Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=488] log sequence number 89666290 is in the future! Current system log sequence number 89665843.
2019-10-22T08:16:24.426182Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2019-10-22T08:16:24.426369Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=220] log sequence number 89666791 is in the future! Current system log sequence number 89665843.
2019-10-22T08:16:24.426385Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2019-10-22T08:16:24.426694Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=480] log sequence number 89666791 is in the future! Current system log sequence number 89665843.
2019-10-22T08:16:24.426711Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2019-10-22T08:16:24.426893Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=221] log sequence number 89667292 is in the future! Current system log sequence number 89665843.
2019-10-22T08:16:24.426909Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2019-10-22T08:16:24.497394Z 0 [Note] InnoDB: Last MySQL binlog file position 0 15488347, file name mysql_binary_log.000006
2019-10-22T08:16:24.606751Z 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
2019-10-22T08:16:24.606796Z 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2019-10-22T08:16:24.606896Z 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2019-10-22T08:16:24.629873Z 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
2019-10-22T08:16:24.631104Z 0 [Note] InnoDB: 96 redo rollback segment(s) found. 96 redo rollback segment(s) are active.
2019-10-22T08:16:24.631127Z 0 [Note] InnoDB: 32 non-redo rollback segment(s) are active.
2019-10-22T08:16:24.631616Z 0 [Note] InnoDB: Waiting for purge to start
2019-10-22 01:16:24 0x7f215b583700  InnoDB: Assertion failure in thread 139781243156224 in file fut0lst.ic line 85
InnoDB: Failing assertion: addr.page == FIL_NULL || addr.boffset >= FIL_PAGE_DATA
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.7/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
08:16:24 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.
Attempting to collect some information that could help diagnose the problem.
As this is a crash and something is definitely wrong, the information
collection process might fail.

key_buffer_size=8388608
read_buffer_size=2097152
max_used_connections=0
max_threads=151
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 = 1556452 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x7f213c0008c0
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 = 7f215b582db0 thread_stack 0x40000
/usr/sbin/mysqld(my_print_stacktrace+0x3b)[0xf080bb]
/usr/sbin/mysqld(handle_fatal_signal+0x461)[0x7b9ce1]
/lib64/libpthread.so.0(+0xf630)[0x7f227a66b630]
/lib64/libc.so.6(gsignal+0x37)[0x7f2279055377]
/lib64/libc.so.6(abort+0x148)[0x7f2279056a68]
/usr/sbin/mysqld[0x789ff8]
/usr/sbin/mysqld[0x789b08]
/usr/sbin/mysqld[0x10a2a95]
/usr/sbin/mysqld[0x10a4b98]
/usr/sbin/mysqld(_Z9trx_purgemmb+0x3c9)[0x10a7399]
/usr/sbin/mysqld(srv_purge_coordinator_thread+0xded)[0x107f9bd]
/lib64/libpthread.so.0(+0x7ea5)[0x7f227a663ea5]
/lib64/libc.so.6(clone+0x6d)[0x7f227911d8cd]

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0): Connection ID (thread ID): 0
Status: NOT_KILLED

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.
2019-10-22T08:16:25.979566Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2019-10-22T08:16:25.981212Z 0 [Note] /usr/sbin/mysqld (mysqld 5.7.27-log) starting as process 4654 ...
2019-10-22T08:16:25.986224Z 0 [Note] InnoDB: PUNCH HOLE support available
2019-10-22T08:16:25.986294Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2019-10-22T08:16:25.986304Z 0 [Note] InnoDB: Uses event mutexes
2019-10-22T08:16:25.986313Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2019-10-22T08:16:25.986321Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2019-10-22T08:16:25.986338Z 0 [Note] InnoDB: Using Linux native AIO
2019-10-22T08:16:25.986809Z 0 [Note] InnoDB: Number of pools: 1
2019-10-22T08:16:25.986955Z 0 [Note] InnoDB: Using CPU crc32 instructions
2019-10-22T08:16:25.989736Z 0 [Note] InnoDB: Initializing buffer pool, total size = 4G, instances = 8, chunk size = 128M
2019-10-22T08:16:26.298298Z 0 [Note] InnoDB: Completed initialization of buffer pool
2019-10-22T08:16:26.330087Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2019-10-22T08:16:26.345346Z 0 [Note] InnoDB: Highest supported file format is Barracuda.
2019-10-22T08:16:26.366211Z 0 [Note] InnoDB: Log scan progressed past the checkpoint lsn 89665825
2019-10-22T08:16:26.366296Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 89665834
2019-10-22T08:16:26.366323Z 0 [Note] InnoDB: Database was not shutdown normally!
2019-10-22T08:16:26.366333Z 0 [Note] InnoDB: Starting crash recovery.
2019-10-22T08:16:26.387591Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=5] log sequence number 89667292 is in the future! Current system log sequence number 89665843.
2019-10-22T08:16:26.387636Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2019-10-22T08:16:26.411036Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=219] log sequence number 89666290 is in the future! Current system log sequence number 89665843.
2019-10-22T08:16:26.411084Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2019-10-22T08:16:26.411426Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=488] log sequence number 89666290 is in the future! Current system log sequence number 89665843.
2019-10-22T08:16:26.411452Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2019-10-22T08:16:26.411648Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=220] log sequence number 89666791 is in the future! Current system log sequence number 89665843.
2019-10-22T08:16:26.411665Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2019-10-22T08:16:26.411975Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=480] log sequence number 89666791 is in the future! Current system log sequence number 89665843.
2019-10-22T08:16:26.411991Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2019-10-22T08:16:26.412197Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=221] log sequence number 89667292 is in the future! Current system log sequence number 89665843.
2019-10-22T08:16:26.412214Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2019-10-22T08:16:26.483510Z 0 [Note] InnoDB: Last MySQL binlog file position 0 15488347, file name mysql_binary_log.000006
2019-10-22T08:16:26.593296Z 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
2019-10-22T08:16:26.593330Z 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2019-10-22T08:16:26.593407Z 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2019-10-22T08:16:26.616240Z 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
2019-10-22T08:16:26.617831Z 0 [Note] InnoDB: 96 redo rollback segment(s) found. 96 redo rollback segment(s) are active.
2019-10-22T08:16:26.617853Z 0 [Note] InnoDB: 32 non-redo rollback segment(s) are active.
2019-10-22T08:16:26.618200Z 0 [Note] InnoDB: Waiting for purge to start
2019-10-22 01:16:26 0x7f9c8a0b8700  InnoDB: Assertion failure in thread 140310307636992 in file fut0lst.ic line 85
InnoDB: Failing assertion: addr.page == FIL_NULL || addr.boffset >= FIL_PAGE_DATA
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.7/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
08:16:26 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.
Attempting to collect some information that could help diagnose the problem.
As this is a crash and something is definitely wrong, the information
collection process might fail.

key_buffer_size=8388608
read_buffer_size=2097152
max_used_connections=0
max_threads=151
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 = 1556452 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x7f9c6c0008c0
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 = 7f9c8a0b7db0 thread_stack 0x40000
/usr/sbin/mysqld(my_print_stacktrace+0x3b)[0xf080bb]
/usr/sbin/mysqld(handle_fatal_signal+0x461)[0x7b9ce1]
/lib64/libpthread.so.0(+0xf630)[0x7f9da9648630]
/lib64/libc.so.6(gsignal+0x37)[0x7f9da8032377]
/lib64/libc.so.6(abort+0x148)[0x7f9da8033a68]
/usr/sbin/mysqld[0x789ff8]
/usr/sbin/mysqld[0x789b08]
/usr/sbin/mysqld[0x10a2a95]
/usr/sbin/mysqld[0x10a4b98]
/usr/sbin/mysqld(_Z9trx_purgemmb+0x3c9)[0x10a7399]
/usr/sbin/mysqld(srv_purge_coordinator_thread+0xded)[0x107f9bd]
/lib64/libpthread.so.0(+0x7ea5)[0x7f9da9640ea5]
/lib64/libc.so.6(clone+0x6d)[0x7f9da80fa8cd]

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0): Connection ID (thread ID): 0
Status: NOT_KILLED

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.
2019-10-22T08:16:27.978722Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2019-10-22T08:16:27.980820Z 0 [Note] /usr/sbin/mysqld (mysqld 5.7.27-log) starting as process 4704 ...
2019-10-22T08:16:27.985367Z 0 [Note] InnoDB: PUNCH HOLE support available
2019-10-22T08:16:27.985424Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2019-10-22T08:16:27.985433Z 0 [Note] InnoDB: Uses event mutexes
2019-10-22T08:16:27.985441Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2019-10-22T08:16:27.985449Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2019-10-22T08:16:27.985462Z 0 [Note] InnoDB: Using Linux native AIO
2019-10-22T08:16:27.985845Z 0 [Note] InnoDB: Number of pools: 1
2019-10-22T08:16:27.986029Z 0 [Note] InnoDB: Using CPU crc32 instructions
2019-10-22T08:16:27.988657Z 0 [Note] InnoDB: Initializing buffer pool, total size = 4G, instances = 8, chunk size = 128M
2019-10-22T08:16:28.288104Z 0 [Note] InnoDB: Completed initialization of buffer pool
2019-10-22T08:16:28.320149Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2019-10-22T08:16:28.335270Z 0 [Note] InnoDB: Highest supported file format is Barracuda.
2019-10-22T08:16:28.356116Z 0 [Note] InnoDB: Log scan progressed past the checkpoint lsn 89665825
2019-10-22T08:16:28.356184Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 89665834
2019-10-22T08:16:28.356194Z 0 [Note] InnoDB: Database was not shutdown normally!
2019-10-22T08:16:28.356203Z 0 [Note] InnoDB: Starting crash recovery.
2019-10-22T08:16:28.375583Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=5] log sequence number 89667292 is in the future! Current system log sequence number 89665843.
2019-10-22T08:16:28.375627Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2019-10-22T08:16:28.400009Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=219] log sequence number 89666290 is in the future! Current system log sequence number 89665843.
2019-10-22T08:16:28.400034Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2019-10-22T08:16:28.400408Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=488] log sequence number 89666290 is in the future! Current system log sequence number 89665843.
2019-10-22T08:16:28.400428Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2019-10-22T08:16:28.400690Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=220] log sequence number 89666791 is in the future! Current system log sequence number 89665843.
2019-10-22T08:16:28.400709Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2019-10-22T08:16:28.401055Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=480] log sequence number 89666791 is in the future! Current system log sequence number 89665843.
2019-10-22T08:16:28.401073Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2019-10-22T08:16:28.401290Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=221] log sequence number 89667292 is in the future! Current system log sequence number 89665843.
2019-10-22T08:16:28.401308Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2019-10-22T08:16:28.510856Z 0 [Note] InnoDB: Last MySQL binlog file position 0 15488347, file name mysql_binary_log.000006
2019-10-22T08:16:28.620099Z 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
2019-10-22T08:16:28.620121Z 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2019-10-22T08:16:28.620190Z 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2019-10-22T08:16:28.641827Z 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
2019-10-22T08:16:28.642947Z 0 [Note] InnoDB: 96 redo rollback segment(s) found. 96 redo rollback segment(s) are active.
2019-10-22T08:16:28.642970Z 0 [Note] InnoDB: 32 non-redo rollback segment(s) are active.
2019-10-22T08:16:28.643414Z 0 [Note] InnoDB: Waiting for purge to start
2019-10-22 01:16:28 0x7f2134df1700  InnoDB: Assertion failure in thread 139780597683968 in file fut0lst.ic line 85
InnoDB: Failing assertion: addr.page == FIL_NULL || addr.boffset >= FIL_PAGE_DATA
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.7/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
08:16:28 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.
Attempting to collect some information that could help diagnose the problem.
As this is a crash and something is definitely wrong, the information
collection process might fail.

key_buffer_size=8388608
read_buffer_size=2097152
max_used_connections=0
max_threads=151
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 = 1556452 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x7f210c0008c0
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 = 7f2134df0db0 thread_stack 0x40000
/usr/sbin/mysqld(my_print_stacktrace+0x3b)[0xf080bb]
/usr/sbin/mysqld(handle_fatal_signal+0x461)[0x7b9ce1]
/lib64/libpthread.so.0(+0xf630)[0x7f2254381630]
/lib64/libc.so.6(gsignal+0x37)[0x7f2252d6b377]
/lib64/libc.so.6(abort+0x148)[0x7f2252d6ca68]
/usr/sbin/mysqld[0x789ff8]
/usr/sbin/mysqld[0x789b08]
/usr/sbin/mysqld[0x10a2a95]
/usr/sbin/mysqld[0x10a4b98]
/usr/sbin/mysqld(_Z9trx_purgemmb+0x3c9)[0x10a7399]
/usr/sbin/mysqld(srv_purge_coordinator_thread+0xded)[0x107f9bd]
/lib64/libpthread.so.0(+0x7ea5)[0x7f2254379ea5]
/lib64/libc.so.6(clone+0x6d)[0x7f2252e338cd]

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0): Connection ID (thread ID): 0
Status: NOT_KILLED

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.

关于这个问题的解法,上面的错误中已经给出提示了:
https://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html

需要启用参数: innodb_force_recovery

官方说明如下:

innodb_force_recovery is 0 by default (normal startup without forced recovery). The permissible nonzero values for innodb_force_recovery are 1 to 6. A larger value includes the functionality of lesser values.

可以看到:
默认情况下,该参数是[0],表示启动的时候,不做强制修复.
而在非零的情况下,该参数的值是从[1-6]

在数据库的配置文件中启用这个参数.

[root@mysql02 log]# cat /etc/my.cnf | head -n 13
[mysqld]

# If you want to recovery database from crash
#innodb_force_recovery = 1
innodb_force_recovery = 2

# running
pid-file=/mysql_data/run/mysqld/mysqld.pid
socket=/mysql_data/lib/mysql/mysql.sock

# log
log-error=/mysql_data/log/mysqld.log

[root@mysql02 log]# 

该参数的设置从小往大修改,[0 –> 6].
如果当前值还不能修复,则一步步的提升该参数的值.

从上面可以看到,我的该参数在【1】的时候还是无法启动数据库,提升到【2】的时候就好了.

修改参数后的操作记录具体如下:

[root@mysql02 log]# service mysqld start
Redirecting to /bin/systemctl start mysqld.service
[root@mysql02 log]# 
[root@mysql02 log]# service mysqld status
Redirecting to /bin/systemctl status mysqld.service
● mysqld.service - MySQL Server
   Loaded: loaded (/usr/lib/systemd/system/mysqld.service; disabled; vendor preset: disabled)
   Active: active (running) since Tue 2019-10-22 16:45:54 CST; 22min ago
     Docs: man:mysqld(8)
           http://dev.mysql.com/doc/refman/en/using-systemd.html
  Process: 5423 ExecStart=/usr/sbin/mysqld --daemonize --pid-file=/var/run/mysqld/mysqld.pid $MYSQLD_OPTS (code=exited, status=0/SUCCESS)
  Process: 5402 ExecStartPre=/usr/bin/mysqld_pre_systemd (code=exited, status=0/SUCCESS)
 Main PID: 5426 (mysqld)
   CGroup: /system.slice/mysqld.service
           └─5426 /usr/sbin/mysqld --daemonize --pid-file=/var/run/mysqld/mysqld.pid

Oct 22 16:45:51 mysql02.adamhuan.com systemd[1]: Starting MySQL Server...
Oct 22 16:45:54 mysql02.adamhuan.com systemd[1]: Started MySQL Server.
[root@mysql02 log]# 
[root@mysql02 log]# netstat -tupln | grep mysql
tcp6       0      0 :::3306                 :::*                    LISTEN      5426/mysqld         
[root@mysql02 log]# 

这个过程中的日志如下:

2019-10-22T08:45:52.989358Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2019-10-22T08:45:52.991599Z 0 [Note] /usr/sbin/mysqld (mysqld 5.7.27-log) starting as process 5426 ...
2019-10-22T08:45:52.997872Z 0 [Note] InnoDB: PUNCH HOLE support available
2019-10-22T08:45:52.997917Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2019-10-22T08:45:52.997927Z 0 [Note] InnoDB: Uses event mutexes
2019-10-22T08:45:52.997935Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2019-10-22T08:45:52.997998Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2019-10-22T08:45:52.998021Z 0 [Note] InnoDB: Using Linux native AIO
2019-10-22T08:45:52.998606Z 0 [Note] InnoDB: Number of pools: 1
2019-10-22T08:45:52.998778Z 0 [Note] InnoDB: Using CPU crc32 instructions
2019-10-22T08:45:53.001672Z 0 [Note] InnoDB: Initializing buffer pool, total size = 4G, instances = 8, chunk size = 128M
2019-10-22T08:45:53.313332Z 0 [Note] InnoDB: Completed initialization of buffer pool
2019-10-22T08:45:53.345126Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2019-10-22T08:45:53.361236Z 0 [Note] InnoDB: Highest supported file format is Barracuda.
2019-10-22T08:45:53.381577Z 0 [Note] InnoDB: Log scan progressed past the checkpoint lsn 89665825
2019-10-22T08:45:53.381646Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 89665834
2019-10-22T08:45:53.381657Z 0 [Note] InnoDB: Database was not shutdown normally!
2019-10-22T08:45:53.381666Z 0 [Note] InnoDB: Starting crash recovery.
2019-10-22T08:45:53.401732Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=5] log sequence number 89667292 is in the future! Current system log sequence number 89665843.
2019-10-22T08:45:53.401775Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2019-10-22T08:45:53.425198Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=219] log sequence number 89666290 is in the future! Current system log sequence number 89665843.
2019-10-22T08:45:53.425245Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2019-10-22T08:45:53.425533Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=488] log sequence number 89666290 is in the future! Current system log sequence number 89665843.
2019-10-22T08:45:53.425550Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2019-10-22T08:45:53.425737Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=220] log sequence number 89666791 is in the future! Current system log sequence number 89665843.
2019-10-22T08:45:53.425753Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2019-10-22T08:45:53.426916Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=480] log sequence number 89666791 is in the future! Current system log sequence number 89665843.
2019-10-22T08:45:53.426936Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2019-10-22T08:45:53.427143Z 0 [ERROR] InnoDB: Page [page id: space=0, page number=221] log sequence number 89667292 is in the future! Current system log sequence number 89665843.
2019-10-22T08:45:53.427160Z 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.
2019-10-22T08:45:53.498737Z 0 [Note] InnoDB: Last MySQL binlog file position 0 15488347, file name mysql_binary_log.000006
2019-10-22T08:45:53.605596Z 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
2019-10-22T08:45:53.605616Z 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2019-10-22T08:45:53.605674Z 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2019-10-22T08:45:53.629360Z 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
2019-10-22T08:45:53.630419Z 0 [Note] InnoDB: 96 redo rollback segment(s) found. 96 redo rollback segment(s) are active.
2019-10-22T08:45:53.630438Z 0 [Note] InnoDB: 32 non-redo rollback segment(s) are active.
2019-10-22T08:45:53.631011Z 0 [Note] InnoDB: 5.7.27 started; log sequence number 89665834
2019-10-22T08:45:53.631032Z 0 [Note] InnoDB: !!! innodb_force_recovery is set to 2 !!!
2019-10-22T08:45:53.631436Z 0 [Note] Plugin 'FEDERATED' is disabled.
2019-10-22T08:45:53.632069Z 0 [Note] InnoDB: Loading buffer pool(s) from /mysql_data/data/ib_buffer_pool
2019-10-22T08:45:53.742808Z 0 [Note] Recovering after a crash using /mysql_data/lib/mysql/mysql_binary_log
2019-10-22T08:45:53.965807Z 0 [Note] Starting crash recovery...
2019-10-22T08:45:53.965918Z 0 [Note] Crash recovery finished.
2019-10-22T08:45:54.095396Z 0 [Note] Found ca.pem, server-cert.pem and server-key.pem in data directory. Trying to enable SSL support using them.
2019-10-22T08:45:54.111020Z 0 [Warning] CA certificate ca.pem is self signed.
2019-10-22T08:45:54.112835Z 0 [Note] Server hostname (bind-address): '*'; port: 3306
2019-10-22T08:45:54.112907Z 0 [Note] IPv6 is available.
2019-10-22T08:45:54.112928Z 0 [Note]   - '::' resolves to '::';
2019-10-22T08:45:54.112961Z 0 [Note] Server socket created on IP: '::'.
2019-10-22T08:45:54.173897Z 0 [Note] Failed to start slave threads for channel ''
2019-10-22T08:45:54.248402Z 0 [Note] Event Scheduler: Loaded 0 events
2019-10-22T08:45:54.248832Z 0 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.7.27-log'  socket: '/mysql_data/lib/mysql/mysql.sock'  port: 3306  MySQL Community Server (GPL)
2019-10-22T08:45:55.396070Z 0 [Note] InnoDB: Buffer pool(s) load completed at 191022  1:45:55

注意,上面只是以【innodb_forced_recovery=2】的方式将数据库启动了,并不是表示数据库被修复了。

导出数据库全库:

[root@mysql02 log]# cd /mysql_data/backup/
[root@mysql02 backup]# ls -litr
total 0
[root@mysql02 backup]# 
[root@mysql02 backup]# mysqldump -uroot -p --events --all-databases > MySQL_all_db.dmp  Enter password: 
[root@mysql02 backup]# 
[root@mysql02 backup]# ll
total 36144
-rw-r--r-- 1 root root 37007420 Oct 22 22:13 MySQL_all_db.dmp
[root@mysql02 backup]# 
[root@mysql02 backup]# du -sh *
36M     MySQL_all_db.dmp
[root@mysql02 backup]# 

可以看到,MySQL的数据被全库导出了,总共【36 MB】

删除MySQL数据目录中的ib_logfile文件:

[root@mysql02 backup]# cat /etc/my.cnf | grep datadir
datadir=/mysql_data/data
[root@mysql02 backup]# 
[root@mysql02 log]# ls -ltr /mysql_data/data/ib*
-rw-r----- 1 mysql mysql      5921 Oct 22 22:24 /mysql_data/data/ib_buffer_pool
-rw-r----- 1 mysql mysql  79691776 Oct 22 22:24 /mysql_data/data/ibdata1
-rw-r----- 1 mysql mysql 536870912 Oct 22 22:26 /mysql_data/data/ib_logfile1
-rw-r----- 1 mysql mysql 536870912 Oct 22 22:29 /mysql_data/data/ib_logfile0
-rw-r----- 1 mysql mysql  12582912 Oct 22 22:29 /mysql_data/data/ibtmp1
[root@mysql02 log]# 
[root@mysql02 log]# rm -rf /mysql_data/data/ib_logfile*
[root@mysql02 log]# rm -rf /mysql_data/data/ibdata1 
[root@mysql02 log]# 
[root@mysql02 log]# ls -ltr /mysql_data/data/ib*       
-rw-r----- 1 mysql mysql     5921 Oct 22 22:24 /mysql_data/data/ib_buffer_pool
-rw-r----- 1 mysql mysql 12582912 Oct 22 22:29 /mysql_data/data/ibtmp1
[root@mysql02 log]# 

修改innodb_force_recovery参数的值,还原为默认的【0】

[root@mysql02 backup]# cat /etc/my.cnf | grep innodb_force
#innodb_force_recovery = 1
innodb_force_recovery = 2
[root@mysql02 backup]# 
[root@mysql02 backup]# sed -i '/innodb_force_recovery/s/2/0/g' /etc/my.cnf
[root@mysql02 backup]# 
[root@mysql02 backup]# cat /etc/my.cnf | grep innodb_force                
#innodb_force_recovery = 1
innodb_force_recovery = 0
[root@mysql02 backup]# 

然后,重启MySQL数据库服务:

[root@mysql02 log]# cat mysqld.log | tail -n 8

===========================
===========================
===========================
===========================
===========================


[root@mysql02 log]# 
[root@mysql02 log]# service mysqld status
Redirecting to /bin/systemctl status mysqld.service
● mysqld.service - MySQL Server
   Loaded: loaded (/usr/lib/systemd/system/mysqld.service; disabled; vendor preset: disabled)
   Active: failed (Result: start-limit) since Tue 2019-10-22 22:29:41 CST; 4min 21s ago
     Docs: man:mysqld(8)
           http://dev.mysql.com/doc/refman/en/using-systemd.html
  Process: 11036 ExecStart=/usr/sbin/mysqld --daemonize --pid-file=/var/run/mysqld/mysqld.pid $MYSQLD_OPTS (code=exited, status=1/FAILURE)
  Process: 11015 ExecStartPre=/usr/bin/mysqld_pre_systemd (code=exited, status=0/SUCCESS)

Oct 22 22:29:41 mysql02.adamhuan.com systemd[1]: mysqld.service: control process exi...1
Oct 22 22:29:41 mysql02.adamhuan.com systemd[1]: Failed to start MySQL Server.
Oct 22 22:29:41 mysql02.adamhuan.com systemd[1]: Unit mysqld.service entered failed ....
Oct 22 22:29:41 mysql02.adamhuan.com systemd[1]: mysqld.service failed.
Oct 22 22:29:41 mysql02.adamhuan.com systemd[1]: mysqld.service holdoff time over, s....
Oct 22 22:29:41 mysql02.adamhuan.com systemd[1]: Stopped MySQL Server.
Oct 22 22:29:41 mysql02.adamhuan.com systemd[1]: start request repeated too quickly ...e
Oct 22 22:29:41 mysql02.adamhuan.com systemd[1]: Failed to start MySQL Server.
Oct 22 22:29:41 mysql02.adamhuan.com systemd[1]: Unit mysqld.service entered failed ....
Oct 22 22:29:41 mysql02.adamhuan.com systemd[1]: mysqld.service failed.
Hint: Some lines were ellipsized, use -l to show in full.
[root@mysql02 log]# 
[root@mysql02 log]# ps -ef | grep mysql
root      11125   1679  0 22:34 pts/0    00:00:00 grep --color=auto mysql
[root@mysql02 log]# 
[root@mysql02 log]# service mysqld start
Redirecting to /bin/systemctl start mysqld.service
[root@mysql02 log]# 

可以看到,服务已经启动成功了。

登录数据库看看具体的情况:

[root@mysql02 log]# mysql -u root -p
Enter password: 
Welcome to the MySQL monitor.  Commands end with ; or \g.
Your MySQL connection id is 2
Server version: 5.7.27-log MySQL Community Server (GPL)

Copyright (c) 2000, 2019, Oracle and/or its affiliates. All rights reserved.

Oracle is a registered trademark of Oracle Corporation and/or its
affiliates. Other names may be trademarks of their respective
owners.

Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.

mysql> 
mysql> show variables like 'innodb_force%'
    -> ;
+-----------------------------+-------+
| Variable_name               | Value |
+-----------------------------+-------+
| innodb_force_load_corrupted | OFF   |
| innodb_force_recovery       | 0     |
+-----------------------------+-------+
2 rows in set (0.00 sec)

mysql> 
mysql> exit;
Bye
[root@mysql02 log]# 

可以看到,当前已经恢复到了按照正常的方式启动。

这个过程中的日志如下:【/mysql_data/log/mysqld.log】

2019-10-22T14:34:12.562402Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2019-10-22T14:34:12.564807Z 0 [Note] /usr/sbin/mysqld (mysqld 5.7.27-log) starting as process 11166 ...
2019-10-22T14:34:12.570987Z 0 [Note] InnoDB: PUNCH HOLE support available
2019-10-22T14:34:12.571037Z 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2019-10-22T14:34:12.571049Z 0 [Note] InnoDB: Uses event mutexes
2019-10-22T14:34:12.571058Z 0 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2019-10-22T14:34:12.571089Z 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2019-10-22T14:34:12.571105Z 0 [Note] InnoDB: Using Linux native AIO
2019-10-22T14:34:12.571655Z 0 [Note] InnoDB: Number of pools: 1
2019-10-22T14:34:12.571996Z 0 [Note] InnoDB: Using CPU crc32 instructions
2019-10-22T14:34:12.574871Z 0 [Note] InnoDB: Initializing buffer pool, total size = 4G, instances = 8, chunk size = 128M
2019-10-22T14:34:12.899950Z 0 [Note] InnoDB: Completed initialization of buffer pool
2019-10-22T14:34:12.933012Z 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2019-10-22T14:34:12.943682Z 0 [Note] InnoDB: The first innodb_system data file 'ibdata1' did not exist. A new tablespace will be created!
2019-10-22T14:34:12.944256Z 0 [Note] InnoDB: Setting file './ibdata1' size to 12 MB. Physically writing the file full; Please wait ...
2019-10-22T14:34:12.966784Z 0 [Note] InnoDB: File './ibdata1' size is now 12 MB.
2019-10-22T14:34:12.967303Z 0 [Note] InnoDB: Setting log file ./ib_logfile101 size to 512 MB
2019-10-22T14:34:12.967392Z 0 [Note] InnoDB: Progress in MB:
 100 200 300 400 500
2019-10-22T14:34:14.099173Z 0 [Note] InnoDB: Setting log file ./ib_logfile1 size to 512 MB
2019-10-22T14:34:14.099470Z 0 [Note] InnoDB: Progress in MB:
 100 200 300 400 500
2019-10-22T14:34:15.268714Z 0 [Note] InnoDB: Renaming log file ./ib_logfile101 to ./ib_logfile0
2019-10-22T14:34:15.268841Z 0 [Warning] InnoDB: New log files created, LSN=45790
2019-10-22T14:34:15.268948Z 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
2019-10-22T14:34:15.268963Z 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2019-10-22T14:34:15.269026Z 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2019-10-22T14:34:15.285172Z 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
2019-10-22T14:34:15.285455Z 0 [Note] InnoDB: Doublewrite buffer not found: creating new
2019-10-22T14:34:15.314390Z 0 [Note] InnoDB: Doublewrite buffer created
2019-10-22T14:34:15.323020Z 0 [Note] InnoDB: 96 redo rollback segment(s) found. 96 redo rollback segment(s) are active.
2019-10-22T14:34:15.323042Z 0 [Note] InnoDB: 32 non-redo rollback segment(s) are active.
2019-10-22T14:34:15.323604Z 0 [Warning] InnoDB: Creating foreign key constraint system tables.
2019-10-22T14:34:15.326519Z 0 [Note] InnoDB: Foreign key constraint system tables created
2019-10-22T14:34:15.326555Z 0 [Note] InnoDB: Creating tablespace and datafile system tables.
2019-10-22T14:34:15.326792Z 0 [Note] InnoDB: Tablespace and datafile system tables created.
2019-10-22T14:34:15.326816Z 0 [Note] InnoDB: Creating sys_virtual system tables.
2019-10-22T14:34:15.327025Z 0 [Note] InnoDB: sys_virtual table created
2019-10-22T14:34:15.327717Z 0 [Note] InnoDB: Waiting for purge to start
2019-10-22T14:34:15.378147Z 0 [Note] InnoDB: 5.7.27 started; log sequence number 0
2019-10-22T14:34:15.379071Z 0 [Note] Plugin 'FEDERATED' is disabled.
2019-10-22T14:34:15.383267Z 0 [Warning] InnoDB: Cannot open table mysql/plugin from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue.
mysqld: Table 'mysql.plugin' doesn't exist
2019-10-22T14:34:15.383320Z 0 [ERROR] Can't open the mysql.plugin table. Please run mysql_upgrade to create it.
2019-10-22T14:34:15.386416Z 0 [Warning] InnoDB: Cannot open table mysql/gtid_executed from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue.
mysqld: Table 'mysql.gtid_executed' doesn't exist
2019-10-22T14:34:15.386448Z 0 [Warning] Gtid table is not ready to be used. Table 'mysql.gtid_executed' cannot be opened.
2019-10-22T14:34:15.387130Z 0 [Note] Found ca.pem, server-cert.pem and server-key.pem in data directory. Trying to enable SSL support using them.
2019-10-22T14:34:15.387519Z 0 [Warning] CA certificate ca.pem is self signed.
2019-10-22T14:34:15.389006Z 0 [Note] Server hostname (bind-address): '*'; port: 3306
2019-10-22T14:34:15.389076Z 0 [Note] IPv6 is available.
2019-10-22T14:34:15.389093Z 0 [Note]   - '::' resolves to '::';
2019-10-22T14:34:15.389133Z 0 [Note] Server socket created on IP: '::'.
2019-10-22T14:34:15.390136Z 0 [Warning] InnoDB: Cannot open table mysql/server_cost from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue.
2019-10-22T14:34:15.390176Z 0 [Warning] Failed to open optimizer cost constant tables

2019-10-22T14:34:15.391310Z 0 [Warning] InnoDB: Cannot open table mysql/time_zone_leap_second from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue.
2019-10-22T14:34:15.391394Z 0 [Warning] Can't open and lock time zone table: Table 'mysql.time_zone_leap_second' doesn't exist trying to live without them
2019-10-22T14:34:15.392184Z 0 [Warning] InnoDB: Cannot open table mysql/servers from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue.
2019-10-22T14:34:15.392207Z 0 [ERROR] Can't open and lock privilege tables: Table 'mysql.servers' doesn't exist
2019-10-22T14:34:15.392594Z 0 [Warning] InnoDB: Cannot open table mysql/slave_master_info from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue.
2019-10-22T14:34:15.392828Z 0 [Warning] InnoDB: Cannot open table mysql/slave_relay_log_info from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue.
2019-10-22T14:34:15.392953Z 0 [Warning] InnoDB: Cannot open table mysql/slave_master_info from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue.
2019-10-22T14:34:15.392979Z 0 [Warning] Info table is not ready to be used. Table 'mysql.slave_master_info' cannot be opened.
2019-10-22T14:34:15.393112Z 0 [Warning] InnoDB: Cannot open table mysql/slave_worker_info from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue.
2019-10-22T14:34:15.393242Z 0 [Warning] InnoDB: Cannot open table mysql/slave_relay_log_info from the internal data dictionary of InnoDB though the .frm file for the table exists. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue.
2019-10-22T14:34:15.393267Z 0 [Warning] Info table is not ready to be used. Table 'mysql.slave_relay_log_info' cannot be opened.
2019-10-22T14:34:15.393345Z 0 [Note] Failed to start slave threads for channel ''
2019-10-22T14:34:15.402198Z 0 [Note] Event Scheduler: Loaded 0 events
2019-10-22T14:34:15.402377Z 0 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.7.27-log'  socket: '/mysql_data/lib/mysql/mysql.sock'  port: 3306  MySQL Community Server (GPL)

可以看到,虽然数据库按照Normal的方式起来了,但是还是有一些warning;
这些也是要修复的。

把前面通过mysqldump导出的文件,重新导入数据库:

[root@mysql02 ~]# cd /mysql_data/backup/
[root@mysql02 backup]# ls -ltr
total 36144
-rw-r--r-- 1 root root 37007420 Oct 22 22:13 MySQL_all_db.dmp
[root@mysql02 backup]# 
[root@mysql02 backup]# du -sh *
36M     MySQL_all_db.dmp
[root@mysql02 backup]# 
[root@mysql02 backup]# mysql -u root -p < MySQL_all_db.dmp 
Enter password: 
ERROR 1813 (HY000) at line 189: Tablespace '`cloudera_rman`.`RMAN_SCHEMA_VERSION`' exists.
[root@mysql02 backup]# 

因为,前面有过备份,所以,现在,先把现有的库都删掉:

[root@mysql02 mysql_data]# mysql -u root -p
Enter password: 
Welcome to the MySQL monitor.  Commands end with ; or \g.
Your MySQL connection id is 7
Server version: 5.7.27-log MySQL Community Server (GPL)

Copyright (c) 2000, 2019, Oracle and/or its affiliates. All rights reserved.

Oracle is a registered trademark of Oracle Corporation and/or its
affiliates. Other names may be trademarks of their respective
owners.

Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.

mysql> 
mysql> show databases;
+---------------------+
| Database            |
+---------------------+
| information_schema  |
| adamhuan_dev        |
| cloudera5_amon      |
| cloudera5_cmf       |
| cloudera5_metastore |
| cloudera5_nav       |
| cloudera5_navms     |
| cloudera5_rman      |
| cloudera5_sentry    |
| cloudera_amon       |
| cloudera_cmf        |
| cloudera_metastore  |
| cloudera_nav        |
| cloudera_navms      |
| cloudera_rman       |
| cloudera_sentry     |
| cmf                 |
| mysql               |
| performance_schema  |
| sys                 |
+---------------------+
20 rows in set (0.00 sec)

mysql> 
mysql> drop database adamhuan_dev;
Query OK, 0 rows affected (0.00 sec)

mysql> drop database cloudera5_amon;
Query OK, 0 rows affected (0.01 sec)

mysql> drop database cloudera5_cmf;
Query OK, 0 rows affected (0.01 sec)

mysql> drop database cloudera5_metastore; 
Query OK, 0 rows affected (0.01 sec)

mysql> drop database cloudera5_nav;
Query OK, 0 rows affected (0.00 sec)

mysql> drop database cloudera5_navms;
Query OK, 0 rows affected (0.00 sec)

mysql> drop database cloudera5_rman;
Query OK, 0 rows affected (0.00 sec)

mysql> drop database cloudera5_sentry;
Query OK, 0 rows affected (0.01 sec)

mysql> drop database cloudera_amon;
Query OK, 0 rows affected (0.01 sec)

mysql> drop database cloudera_cmf;
Query OK, 0 rows affected (0.00 sec)

mysql> drop database cloudera_metastore;
Query OK, 0 rows affected (0.00 sec)

mysql> drop database cloudera_nav;
Query OK, 0 rows affected (0.00 sec)

mysql> drop database cloudera_navms;
Query OK, 0 rows affected (0.00 sec)

mysql> drop database cloudera_rman;
ERROR 1010 (HY000): Error dropping database (can't rmdir './cloudera_rman', errno: 39)
mysql> 
mysql> show databases;
+--------------------+
| Database           |
+--------------------+
| information_schema |
| cloudera_rman      |
| cloudera_sentry    |
| cmf                |
| mysql              |
| performance_schema |
| sys                |
+--------------------+
7 rows in set (0.00 sec)

mysql> drop database cloudera_sentry;
Query OK, 0 rows affected (0.01 sec)

mysql> drop database cmf;
ERROR 1010 (HY000): Error dropping database (can't rmdir './cmf', errno: 39)
mysql> 
mysql> show databases;
+--------------------+
| Database           |
+--------------------+
| information_schema |
| cloudera_rman      |
| cmf                |
| mysql              |
| performance_schema |
| sys                |
+--------------------+
6 rows in set (0.00 sec)

mysql> 
mysql> exit
Bye
[root@mysql02 mysql_data]# 

可以看到,上面有两个库删除的时候有问题,在导入的时候,也是它们有问题。

停掉数据库服务,然后去数据目录删除对应的SCHEMA目录,然后再拉起数据库服务:

[root@mysql02 mysql_data]# service mysqld status
Redirecting to /bin/systemctl status mysqld.service
● mysqld.service - MySQL Server
   Loaded: loaded (/usr/lib/systemd/system/mysqld.service; disabled; vendor preset: disabled)
   Active: active (running) since Tue 2019-10-22 22:34:15 CST; 23min ago
     Docs: man:mysqld(8)
           http://dev.mysql.com/doc/refman/en/using-systemd.html
  Process: 11163 ExecStart=/usr/sbin/mysqld --daemonize --pid-file=/var/run/mysqld/mysqld.pid $MYSQLD_OPTS (code=exited, status=0/SUCCESS)
  Process: 11142 ExecStartPre=/usr/bin/mysqld_pre_systemd (code=exited, status=0/SUCCESS)
 Main PID: 11166 (mysqld)
   CGroup: /system.slice/mysqld.service
           └─11166 /usr/sbin/mysqld --daemonize --pid-file=/var/run/mysqld/mysqld.pid

Oct 22 22:34:11 mysql02.adamhuan.com systemd[1]: Starting MySQL Server...
Oct 22 22:34:15 mysql02.adamhuan.com systemd[1]: Started MySQL Server.
[root@mysql02 mysql_data]# 
[root@mysql02 mysql_data]# service mysqld stop
Redirecting to /bin/systemctl stop mysqld.service
[root@mysql02 mysql_data]# 
[root@mysql02 mysql_data]# ls -ltr
total 24
drwxr-xr-x  3 mysql mysql 4096 Oct 11 15:16 run
drwxr-xr-x  3 mysql mysql 4096 Oct 11 15:16 lib
drwxr-xr-x  2 mysql mysql 4096 Oct 22 22:13 backup
drwxr-xr-x  2 mysql mysql 4096 Oct 22 22:30 log
drwxr-xr-x 21 root  root  4096 Oct 22 22:53 data_orig_backup
drwxr-xr-x  7 mysql mysql 4096 Oct 22 22:57 data
[root@mysql02 mysql_data]# 
[root@mysql02 mysql_data]# cd data
[root@mysql02 data]# ls
auto.cnf    client-cert.pem  cmf             ib_logfile0  performance_schema  server-cert.pem
ca-key.pem  client-key.pem   ib_buffer_pool  ib_logfile1  private_key.pem     server-key.pem
ca.pem      cloudera_rman    ibdata1         mysql        public_key.pem      sys
[root@mysql02 data]# 
[root@mysql02 data]# rm -rf cloudera_rman/
[root@mysql02 data]# 
[root@mysql02 data]# rm -rf cmf
[root@mysql02 data]# 
[root@mysql02 data]# service mysqld start
Redirecting to /bin/systemctl start mysqld.service
[root@mysql02 data]# 

再进数据库看看当前的状态:

[root@mysql02 data]# mysql -u root -p
Enter password: 
Welcome to the MySQL monitor.  Commands end with ; or \g.
Your MySQL connection id is 2
Server version: 5.7.27-log MySQL Community Server (GPL)

Copyright (c) 2000, 2019, Oracle and/or its affiliates. All rights reserved.

Oracle is a registered trademark of Oracle Corporation and/or its
affiliates. Other names may be trademarks of their respective
owners.

Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.

mysql> 
mysql> show databases;
+--------------------+
| Database           |
+--------------------+
| information_schema |
| mysql              |
| performance_schema |
| sys                |
+--------------------+
4 rows in set (0.00 sec)

mysql> 
mysql> exit
Bye
[root@mysql02 data]# 

再做导入:

[root@mysql02 backup]# mysql -u root -p < MySQL_all_db.dmp 
[root@mysql02 backup]# 

这样,就没问题了。

————————

innodb_force_recovery,各个数字的意义:

1(SRV_FORCE_IGNORE_CORRUPT):忽略检查到的corrupt页。
2(SRV_FORCE_NO_BACKGROUND):阻止主线程的运行,如主线程需要执行full purge操作,会导致crash。
3(SRV_FORCE_NO_TRX_UNDO):不执行事务回滚操作。
4(SRV_FORCE_NO_IBUF_MERGE):不执行插入缓冲的合并操作。
5(SRV_FORCE_NO_UNDO_LOG_SCAN):不查看重做日志,InnoDB存储引擎会将未提交的事务视为已提交。
6(SRV_FORCE_NO_LOG_REDO):不执行前滚的操作。
————————————————

Finished。

说点什么

avatar

此站点使用Akismet来减少垃圾评论。了解我们如何处理您的评论数据

  Subscribe  
提醒
隐藏
变装