Initial prep of full backup ./full-01-04-2019_01-00-02/
xtrabackup version 2.3.10 based on MySQL server 5.6.24 Linux (x86_64) (revision id: bd0d4403f36)
xtrabackup: cd to /test/mysql/restore/full-01-04-2019_01-00-02/
xtrabackup: This target seems to be not prepared yet.
xtrabackup: xtrabackup_logfile detected: size=2097152, start_lsn=(188615798266)
xtrabackup: using the following InnoDB configuration for recovery:
xtrabackup:   innodb_data_home_dir = ./
xtrabackup:   innodb_data_file_path = ibdata1:12M:autoextend
xtrabackup:   innodb_log_group_home_dir = ./
xtrabackup:   innodb_log_files_in_group = 1
xtrabackup:   innodb_log_file_size = 2097152
xtrabackup: using the following InnoDB configuration for recovery:
xtrabackup:   innodb_data_home_dir = ./
xtrabackup:   innodb_data_file_path = ibdata1:12M:autoextend
xtrabackup:   innodb_log_group_home_dir = ./
xtrabackup:   innodb_log_files_in_group = 1
xtrabackup:   innodb_log_file_size = 2097152
xtrabackup: Starting InnoDB instance for recovery.
xtrabackup: Using 104857600 bytes for buffer pool (set by --use-memory parameter)
InnoDB: Using atomics to ref count buffer pool pages
InnoDB: The InnoDB memory heap is disabled
InnoDB: Mutexes and rw_locks use GCC atomic builtins
InnoDB: Memory barrier is not used
InnoDB: Compressed tables use zlib 1.2.7
InnoDB: Using CPU crc32 instructions
InnoDB: Initializing buffer pool, size = 100.0M
InnoDB: Completed initialization of buffer pool
InnoDB: Highest supported file format is Barracuda.
InnoDB: Log scan progressed past the checkpoint lsn 188615798266
InnoDB: Database was not shutdown normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages 
InnoDB: from the doublewrite buffer...
InnoDB: Doing recovery: scanned up to log sequence number 188615903995 (5%)
InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percent: 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 
InnoDB: Apply batch completed
xtrabackup: Last MySQL binlog file position 120, file name mysql-bin.000004

xtrabackup: Recovered WSREP position: ef13aab9-0065-11e9-86d3-7a7566e319b0:212300
xtrabackup: starting shutdown with innodb_fast_shutdown = 1
InnoDB: Starting shutdown...
InnoDB: Shutdown completed; log sequence number 188615903995
190104 18:48:01 completed OK!
Applying incremental backup ./incremental-01-04-2019_09-00-02/ to ./full-01-04-2019_01-00-02/
xtrabackup version 2.3.10 based on MySQL server 5.6.24 Linux (x86_64) (revision id: bd0d4403f36)
incremental backup from 188615903324 is enabled.
xtrabackup: cd to /test/mysql/restore/full-01-04-2019_01-00-02/
xtrabackup: This target seems to be already prepared with --apply-log-only.
xtrabackup: xtrabackup_logfile detected: size=2097152, start_lsn=(188624027560)
xtrabackup: using the following InnoDB configuration for recovery:
xtrabackup:   innodb_data_home_dir = ./
xtrabackup:   innodb_data_file_path = ibdata1:12M:autoextend
xtrabackup:   innodb_log_group_home_dir = /test/mysql/restore/incremental-01-04-2019_09-00-02/
xtrabackup:   innodb_log_files_in_group = 1
xtrabackup:   innodb_log_file_size = 2097152
xtrabackup: Generating a list of tablespaces
xtrabackup: page size for /test/mysql/restore/incremental-01-04-2019_09-00-02//ibdata1.delta is 16384 bytes
Applying /test/mysql/restore/incremental-01-04-2019_09-00-02//ibdata1.delta to ./ibdata1...
xtrabackup: page size for /test/mysql/restore/incremental-01-04-2019_09-00-02//mysql/slave_relay_log_info.ibd.delta is 16384 bytes
Applying /test/mysql/restore/incremental-01-04-2019_09-00-02//mysql/slave_relay_log_info.ibd.delta to ./mysql/slave_relay_log_info.ibd...
xtrabackup: page size for /test/mysql/restore/incremental-01-04-2019_09-00-02//mysql/innodb_index_stats.ibd.delta is 16384 bytes
Applying /test/mysql/restore/incremental-01-04-2019_09-00-02//mysql/innodb_index_stats.ibd.delta to ./mysql/innodb_index_stats.ibd...
xtrabackup: page size for /test/mysql/restore/incremental-01-04-2019_09-00-02//mysql/slave_master_info.ibd.delta is 16384 bytes
Applying /test/mysql/restore/incremental-01-04-2019_09-00-02//mysql/slave_master_info.ibd.delta to ./mysql/slave_master_info.ibd...
xtrabackup: page size for /test/mysql/restore/incremental-01-04-2019_09-00-02//mysql/innodb_table_stats.ibd.delta is 16384 bytes
Applying /test/mysql/restore/incremental-01-04-2019_09-00-02//mysql/innodb_table_stats.ibd.delta to ./mysql/innodb_table_stats.ibd...
xtrabackup: page size for /test/mysql/restore/incremental-01-04-2019_09-00-02//mysql/slave_worker_info.ibd.delta is 16384 bytes
Applying /test/mysql/restore/incremental-01-04-2019_09-00-02//mysql/slave_worker_info.ibd.delta to ./mysql/slave_worker_info.ibd...
xtrabackup: page size for /test/mysql/restore/incremental-01-04-2019_09-00-02//erp_apex/nift_branchwise_summary.ibd.delta is 16384 bytes
Applying /test/mysql/restore/incremental-01-04-2019_09-00-02//erp_apex/nift_branchwise_summary.ibd.delta to ./erp_apex/nift_branchwise_summary.ibd...
xtrabackup: using the following InnoDB configuration for recovery:
xtrabackup:   innodb_data_home_dir = ./
xtrabackup:   innodb_data_file_path = ibdata1:12M:autoextend
xtrabackup:   innodb_log_group_home_dir = /test/mysql/restore/incremental-01-04-2019_09-00-02/
xtrabackup:   innodb_log_files_in_group = 1
xtrabackup:   innodb_log_file_size = 2097152
xtrabackup: Starting InnoDB instance for recovery.
xtrabackup: Using 104857600 bytes for buffer pool (set by --use-memory parameter)
InnoDB: Using atomics to ref count buffer pool pages
InnoDB: The InnoDB memory heap is disabled
InnoDB: Mutexes and rw_locks use GCC atomic builtins
InnoDB: Memory barrier is not used
InnoDB: Compressed tables use zlib 1.2.7
InnoDB: Using CPU crc32 instructions
InnoDB: Initializing buffer pool, size = 100.0M
InnoDB: Completed initialization of buffer pool
InnoDB: Highest supported file format is Barracuda.
InnoDB: Log scan progressed past the checkpoint lsn 188624027560
InnoDB: Database was not shutdown normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages 
InnoDB: from the doublewrite buffer...
InnoDB: Doing recovery: scanned up to log sequence number 188624236118 (11%)
InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percent: 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 
InnoDB: Apply batch completed
xtrabackup: Last MySQL binlog file position 120, file name mysql-bin.000004

xtrabackup: Recovered WSREP position: ef13aab9-0065-11e9-86d3-7a7566e319b0:215728
xtrabackup: starting shutdown with innodb_fast_shutdown = 1
InnoDB: Starting shutdown...
InnoDB: Shutdown completed; log sequence number 188624236118


190104 18:48:08 completed OK!
Applying incremental backup ./incremental-01-04-2019_12-00-02/ to ./full-01-04-2019_01-00-02/
xtrabackup version 2.3.10 based on MySQL server 5.6.24 Linux (x86_64) (revision id: bd0d4403f36)
incremental backup from 188624236112 is enabled.
xtrabackup: cd to /test/mysql/restore/full-01-04-2019_01-00-02/
xtrabackup: This target seems to be already prepared with --apply-log-only.
xtrabackup: xtrabackup_logfile detected: size=2097152, start_lsn=(188650000674)
xtrabackup: using the following InnoDB configuration for recovery:
xtrabackup:   innodb_data_home_dir = ./
xtrabackup:   innodb_data_file_path = ibdata1:12M:autoextend
xtrabackup:   innodb_log_group_home_dir = /test/mysql/restore/incremental-01-04-2019_12-00-02/
xtrabackup:   innodb_log_files_in_group = 1
xtrabackup:   innodb_log_file_size = 2097152
xtrabackup: Generating a list of tablespaces
xtrabackup: page size for /test/mysql/restore/incremental-01-04-2019_12-00-02//ibdata1.delta is 16384 bytes
Applying /test/mysql/restore/incremental-01-04-2019_12-00-02//ibdata1.delta to ./ibdata1...
xtrabackup: page size for /test/mysql/restore/incremental-01-04-2019_12-00-02//mysql/slave_relay_log_info.ibd.delta is 16384 bytes
Applying /test/mysql/restore/incremental-01-04-2019_12-00-02//mysql/slave_relay_log_info.ibd.delta to ./mysql/slave_relay_log_info.ibd...
xtrabackup: page size for /test/mysql/restore/incremental-01-04-2019_12-00-02//mysql/innodb_index_stats.ibd.delta is 16384 bytes
Applying /test/mysql/restore/incremental-01-04-2019_12-00-02//mysql/innodb_index_stats.ibd.delta to ./mysql/innodb_index_stats.ibd...
xtrabackup: page size for /test/mysql/restore/incremental-01-04-2019_12-00-02//mysql/slave_master_info.ibd.delta is 16384 bytes
Applying /test/mysql/restore/incremental-01-04-2019_12-00-02//mysql/slave_master_info.ibd.delta to ./mysql/slave_master_info.ibd...
xtrabackup: page size for /test/mysql/restore/incremental-01-04-2019_12-00-02//mysql/innodb_table_stats.ibd.delta is 16384 bytes
Applying /test/mysql/restore/incremental-01-04-2019_12-00-02//mysql/innodb_table_stats.ibd.delta to ./mysql/innodb_table_stats.ibd...
xtrabackup: page size for /test/mysql/restore/incremental-01-04-2019_12-00-02//mysql/slave_worker_info.ibd.delta is 16384 bytes
Applying /test/mysql/restore/incremental-01-04-2019_12-00-02//mysql/slave_worker_info.ibd.delta to ./mysql/slave_worker_info.ibd...
xtrabackup: page size for /test/mysql/restore/incremental-01-04-2019_12-00-02//erp_apex/nift_branchwise_summary.ibd.delta is 16384 bytes
Applying /test/mysql/restore/incremental-01-04-2019_12-00-02//erp_apex/nift_branchwise_summary.ibd.delta to ./erp_apex/nift_branchwise_summary.ibd...
xtrabackup: using the following InnoDB configuration for recovery:
xtrabackup:   innodb_data_home_dir = ./
xtrabackup:   innodb_data_file_path = ibdata1:12M:autoextend
xtrabackup:   innodb_log_group_home_dir = /test/mysql/restore/incremental-01-04-2019_12-00-02/
xtrabackup:   innodb_log_files_in_group = 1
xtrabackup:   innodb_log_file_size = 2097152
xtrabackup: Starting InnoDB instance for recovery.
xtrabackup: Using 104857600 bytes for buffer pool (set by --use-memory parameter)
InnoDB: Using atomics to ref count buffer pool pages
InnoDB: The InnoDB memory heap is disabled
InnoDB: Mutexes and rw_locks use GCC atomic builtins
InnoDB: Memory barrier is not used
InnoDB: Compressed tables use zlib 1.2.7
InnoDB: Using CPU crc32 instructions
InnoDB: Initializing buffer pool, size = 100.0M
InnoDB: Completed initialization of buffer pool
InnoDB: Highest supported file format is Barracuda.
InnoDB: Log scan progressed past the checkpoint lsn 188650000674
InnoDB: Database was not shutdown normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages 
InnoDB: from the doublewrite buffer...
InnoDB: Doing recovery: scanned up to log sequence number 188650005178 (0%)
InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percent: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 
InnoDB: Apply batch completed
xtrabackup: Last MySQL binlog file position 120, file name mysql-bin.000004

xtrabackup: Recovered WSREP position: ef13aab9-0065-11e9-86d3-7a7566e319b0:218592
xtrabackup: starting shutdown with innodb_fast_shutdown = 1
InnoDB: Starting shutdown...
InnoDB: Shutdown completed; log sequence number 188650005178

190104 18:48:19 completed OK!
Applying incremental backup ./incremental-01-04-2019_15-00-02/ to ./full-01-04-2019_01-00-02/
xtrabackup version 2.3.10 based on MySQL server 5.6.24 Linux (x86_64) (revision id: bd0d4403f36)
incremental backup from 188650005172 is enabled.
xtrabackup: cd to /test/mysql/restore/full-01-04-2019_01-00-02/
xtrabackup: This target seems to be already prepared with --apply-log-only.
xtrabackup: xtrabackup_logfile detected: size=2097152, start_lsn=(188673122998)
xtrabackup: using the following InnoDB configuration for recovery:
xtrabackup:   innodb_data_home_dir = ./
xtrabackup:   innodb_data_file_path = ibdata1:12M:autoextend
xtrabackup:   innodb_log_group_home_dir = /test/mysql/restore/incremental-01-04-2019_15-00-02/
xtrabackup:   innodb_log_files_in_group = 1
xtrabackup:   innodb_log_file_size = 2097152
xtrabackup: Generating a list of tablespaces
xtrabackup: page size for /test/mysql/restore/incremental-01-04-2019_15-00-02//ibdata1.delta is 16384 bytes
Applying /test/mysql/restore/incremental-01-04-2019_15-00-02//ibdata1.delta to ./ibdata1...
xtrabackup: page size for /test/mysql/restore/incremental-01-04-2019_15-00-02//mysql/slave_relay_log_info.ibd.delta is 16384 bytes
Applying /test/mysql/restore/incremental-01-04-2019_15-00-02//mysql/slave_relay_log_info.ibd.delta to ./mysql/slave_relay_log_info.ibd...
xtrabackup: page size for /test/mysql/restore/incremental-01-04-2019_15-00-02//mysql/innodb_index_stats.ibd.delta is 16384 bytes
Applying /test/mysql/restore/incremental-01-04-2019_15-00-02//mysql/innodb_index_stats.ibd.delta to ./mysql/innodb_index_stats.ibd...
xtrabackup: page size for /test/mysql/restore/incremental-01-04-2019_15-00-02//mysql/slave_master_info.ibd.delta is 16384 bytes
Applying /test/mysql/restore/incremental-01-04-2019_15-00-02//mysql/slave_master_info.ibd.delta to ./mysql/slave_master_info.ibd...
xtrabackup: page size for /test/mysql/restore/incremental-01-04-2019_15-00-02//mysql/innodb_table_stats.ibd.delta is 16384 bytes
Applying /test/mysql/restore/incremental-01-04-2019_15-00-02//mysql/innodb_table_stats.ibd.delta to ./mysql/innodb_table_stats.ibd...
xtrabackup: page size for /test/mysql/restore/incremental-01-04-2019_15-00-02//mysql/slave_worker_info.ibd.delta is 16384 bytes
Applying /test/mysql/restore/incremental-01-04-2019_15-00-02//mysql/slave_worker_info.ibd.delta to ./mysql/slave_worker_info.ibd...
xtrabackup: page size for /test/mysql/restore/incremental-01-04-2019_15-00-02//erp_apex/nift_branchwise_summary.ibd.delta is 16384 bytes
Applying /test/mysql/restore/incremental-01-04-2019_15-00-02//erp_apex/nift_branchwise_summary.ibd.delta to ./erp_apex/nift_branchwise_summary.ibd...
xtrabackup: using the following InnoDB configuration for recovery:
xtrabackup:   innodb_data_home_dir = ./
xtrabackup:   innodb_data_file_path = ibdata1:12M:autoextend
xtrabackup:   innodb_log_group_home_dir = /test/mysql/restore/incremental-01-04-2019_15-00-02/
xtrabackup:   innodb_log_files_in_group = 1
xtrabackup:   innodb_log_file_size = 2097152
xtrabackup: Starting InnoDB instance for recovery.
xtrabackup: Using 104857600 bytes for buffer pool (set by --use-memory parameter)
InnoDB: Using atomics to ref count buffer pool pages
InnoDB: The InnoDB memory heap is disabled
InnoDB: Mutexes and rw_locks use GCC atomic builtins
InnoDB: Memory barrier is not used
InnoDB: Compressed tables use zlib 1.2.7
InnoDB: Using CPU crc32 instructions
InnoDB: Initializing buffer pool, size = 100.0M
InnoDB: Completed initialization of buffer pool
InnoDB: Highest supported file format is Barracuda.
InnoDB: Log scan progressed past the checkpoint lsn 188673122998
InnoDB: Database was not shutdown normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages 
InnoDB: from the doublewrite buffer...
InnoDB: Doing recovery: scanned up to log sequence number 188673415238 (15%)
InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percent: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 
InnoDB: Apply batch completed
xtrabackup: Last MySQL binlog file position 120, file name mysql-bin.000004

xtrabackup: Recovered WSREP position: ef13aab9-0065-11e9-86d3-7a7566e319b0:221844
xtrabackup: starting shutdown with innodb_fast_shutdown = 1
InnoDB: Starting shutdown...
InnoDB: Shutdown completed; log sequence number 188673415238

190104 18:48:29 completed OK!
Applying incremental backup ./incremental-01-04-2019_17-38-23/ to ./full-01-04-2019_01-00-02/
xtrabackup version 2.3.10 based on MySQL server 5.6.24 Linux (x86_64) (revision id: bd0d4403f36)
incremental backup from 188673415238 is enabled.
xtrabackup: cd to /test/mysql/restore/full-01-04-2019_01-00-02/
xtrabackup: This target seems to be already prepared with --apply-log-only.
xtrabackup: xtrabackup_logfile detected: size=2097152, start_lsn=(188689984288)
xtrabackup: using the following InnoDB configuration for recovery:
xtrabackup:   innodb_data_home_dir = ./
xtrabackup:   innodb_data_file_path = ibdata1:12M:autoextend
xtrabackup:   innodb_log_group_home_dir = /test/mysql/restore/incremental-01-04-2019_17-38-23/
xtrabackup:   innodb_log_files_in_group = 1
xtrabackup:   innodb_log_file_size = 2097152
xtrabackup: Generating a list of tablespaces
xtrabackup: page size for /test/mysql/restore/incremental-01-04-2019_17-38-23//ibdata1.delta is 16384 bytes
Applying /test/mysql/restore/incremental-01-04-2019_17-38-23//ibdata1.delta to ./ibdata1...
xtrabackup: page size for /test/mysql/restore/incremental-01-04-2019_17-38-23//mysql/slave_relay_log_info.ibd.delta is 16384 bytes
Applying /test/mysql/restore/incremental-01-04-2019_17-38-23//mysql/slave_relay_log_info.ibd.delta to ./mysql/slave_relay_log_info.ibd...
xtrabackup: page size for /test/mysql/restore/incremental-01-04-2019_17-38-23//mysql/innodb_index_stats.ibd.delta is 16384 bytes
Applying /test/mysql/restore/incremental-01-04-2019_17-38-23//mysql/innodb_index_stats.ibd.delta to ./mysql/innodb_index_stats.ibd...
xtrabackup: page size for /test/mysql/restore/incremental-01-04-2019_17-38-23//mysql/slave_master_info.ibd.delta is 16384 bytes
Applying /test/mysql/restore/incremental-01-04-2019_17-38-23//mysql/slave_master_info.ibd.delta to ./mysql/slave_master_info.ibd...
xtrabackup: page size for /test/mysql/restore/incremental-01-04-2019_17-38-23//mysql/innodb_table_stats.ibd.delta is 16384 bytes
Applying /test/mysql/restore/incremental-01-04-2019_17-38-23//mysql/innodb_table_stats.ibd.delta to ./mysql/innodb_table_stats.ibd...
xtrabackup: page size for /test/mysql/restore/incremental-01-04-2019_17-38-23//mysql/slave_worker_info.ibd.delta is 16384 bytes
Applying /test/mysql/restore/incremental-01-04-2019_17-38-23//mysql/slave_worker_info.ibd.delta to ./mysql/slave_worker_info.ibd...
xtrabackup: page size for /test/mysql/restore/incremental-01-04-2019_17-38-23//erp_apex/nift_branchwise_summary.ibd.delta is 16384 bytes
Applying /test/mysql/restore/incremental-01-04-2019_17-38-23//erp_apex/nift_branchwise_summary.ibd.delta to ./erp_apex/nift_branchwise_summary.ibd...
xtrabackup: using the following InnoDB configuration for recovery:
xtrabackup:   innodb_data_home_dir = ./
xtrabackup:   innodb_data_file_path = ibdata1:12M:autoextend
xtrabackup:   innodb_log_group_home_dir = /test/mysql/restore/incremental-01-04-2019_17-38-23/
xtrabackup:   innodb_log_files_in_group = 1
xtrabackup:   innodb_log_file_size = 2097152
xtrabackup: Starting InnoDB instance for recovery.
xtrabackup: Using 104857600 bytes for buffer pool (set by --use-memory parameter)
InnoDB: Using atomics to ref count buffer pool pages
InnoDB: The InnoDB memory heap is disabled
InnoDB: Mutexes and rw_locks use GCC atomic builtins
InnoDB: Memory barrier is not used
InnoDB: Compressed tables use zlib 1.2.7
InnoDB: Using CPU crc32 instructions
InnoDB: Initializing buffer pool, size = 100.0M
InnoDB: Completed initialization of buffer pool
InnoDB: Highest supported file format is Barracuda.
InnoDB: Log scan progressed past the checkpoint lsn 188689984288
InnoDB: Database was not shutdown normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages 
InnoDB: from the doublewrite buffer...
InnoDB: Doing recovery: scanned up to log sequence number 188690040171 (3%)
2019-01-04 18:48:34 7efca8677880  InnoDB: Assertion failure in thread 139623622211712 in file fut0lst.ic line 83
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.6/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
13:48:34 UTC - xtrabackup got signal 6 ;
This could be because you hit a bug or data is corrupted.
This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help
diagnose the problem, but since we have already crashed, 
something is definitely wrong and this may fail.

Thread pointer: 0x0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = 0 thread_stack 0x10000
xtrabackup(my_print_stacktrace+0x2e) [0x97420e]
xtrabackup(handle_fatal_signal+0x262) [0x726862]
/lib64/libpthread.so.0(+0xf6d0) [0x7efca825c6d0]
/lib64/libc.so.6(gsignal+0x37) [0x7efca62eb277]
/lib64/libc.so.6(abort+0x148) [0x7efca62ec968]
xtrabackup() [0x574df5]
xtrabackup(trx_undo_lists_init(trx_rseg_t*)+0x8e5) [0x6ac4b5]
xtrabackup() [0x9e56da]
xtrabackup(trx_rseg_array_init(unsigned char*, ib_bh_t*, mtr_t*)+0x75) [0x9e6225]
xtrabackup(trx_sys_init_at_db_start()+0x2bf) [0x63feff]
xtrabackup(innobase_start_or_create_for_mysql()+0x18bb) [0x71db9b]
xtrabackup() [0x5978f9]
xtrabackup(main+0x127d) [0x582e3d]
/lib64/libc.so.6(__libc_start_main+0xf5) [0x7efca62d7445]
xtrabackup() [0x59628e]

Please report a bug at https://bugs.launchpad.net/percona-xtrabackup
Applying incremental backup ./incremental-01-04-2019_18-00-08/ to ./full-01-04-2019_01-00-02/
xtrabackup version 2.3.10 based on MySQL server 5.6.24 Linux (x86_64) (revision id: bd0d4403f36)
incremental backup from 188690040171 is enabled.
xtrabackup: cd to /test/mysql/restore/full-01-04-2019_01-00-02/
xtrabackup: This target seems to be already prepared with --apply-log-only.
xtrabackup: error: This incremental backup seems not to be proper for the target.
xtrabackup:  Check 'to_lsn' of the target and 'from_lsn' of the incremental.
Applying final logs to full backup ./full-01-04-2019_01-00-02/
xtrabackup version 2.3.10 based on MySQL server 5.6.24 Linux (x86_64) (revision id: bd0d4403f36)
xtrabackup: cd to /test/mysql/restore/full-01-04-2019_01-00-02/
xtrabackup: This target seems to be already prepared with --apply-log-only.
xtrabackup: notice: xtrabackup_logfile was already used to '--prepare'.
xtrabackup: using the following InnoDB configuration for recovery:
xtrabackup:   innodb_data_home_dir = ./
xtrabackup:   innodb_data_file_path = ibdata1:12M:autoextend
xtrabackup:   innodb_log_group_home_dir = ./
xtrabackup:   innodb_log_files_in_group = 2
xtrabackup:   innodb_log_file_size = 2147483648
xtrabackup: using the following InnoDB configuration for recovery:
xtrabackup:   innodb_data_home_dir = ./
xtrabackup:   innodb_data_file_path = ibdata1:12M:autoextend
xtrabackup:   innodb_log_group_home_dir = ./
xtrabackup:   innodb_log_files_in_group = 2
xtrabackup:   innodb_log_file_size = 2147483648
xtrabackup: Starting InnoDB instance for recovery.
xtrabackup: Using 104857600 bytes for buffer pool (set by --use-memory parameter)
InnoDB: Using atomics to ref count buffer pool pages
InnoDB: The InnoDB memory heap is disabled
InnoDB: Mutexes and rw_locks use GCC atomic builtins
InnoDB: Memory barrier is not used
InnoDB: Compressed tables use zlib 1.2.7
InnoDB: Using CPU crc32 instructions
InnoDB: Initializing buffer pool, size = 100.0M
InnoDB: Completed initialization of buffer pool
InnoDB: Setting log file ./ib_logfile101 size to 2048 MB
InnoDB: Progress in MB: 100 200 300 400 500 600 700 800 900 1000 1100 1200 1300 1400 1500 1600 1700 1800 1900 2000
InnoDB: Setting log file ./ib_logfile1 size to 2048 MB
InnoDB: Progress in MB: 100 200 300 400 500 600 700 800 900 1000 1100 1200 1300 1400 1500 1600 1700 1800 1900 2000
InnoDB: Renaming log file ./ib_logfile101 to ./ib_logfile0
InnoDB: New log files created, LSN=187096071126
InnoDB: Highest supported file format is Barracuda.
2019-01-04 18:49:03 7ff5fd2cb880 InnoDB: Error: page 7 log sequence number 188116266764
InnoDB: is in the future! Current system log sequence number 187096071180.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2019-01-04 18:49:03 7ff5fd2cb880 InnoDB: Error: page 1 log sequence number 188686872930
InnoDB: is in the future! Current system log sequence number 187096071180.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2019-01-04 18:49:03 7ff5fd2cb880 InnoDB: Error: page 3 log sequence number 188657250253
InnoDB: is in the future! Current system log sequence number 187096071180.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2019-01-04 18:49:03 7ff5fd2cb880 InnoDB: Error: page 2 log sequence number 188657250253
InnoDB: is in the future! Current system log sequence number 187096071180.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2019-01-04 18:49:03 7ff5fd2cb880 InnoDB: Error: page 4 log sequence number 188688506387
InnoDB: is in the future! Current system log sequence number 187096071180.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2019-01-04 18:49:03 7ff5fd2cb880 InnoDB: Error: page 5 log sequence number 188689984288
InnoDB: is in the future! Current system log sequence number 187096071180.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2019-01-04 18:49:03 7ff5fd2cb880 InnoDB: Error: page 6 log sequence number 188684502947
InnoDB: is in the future! Current system log sequence number 187096071180.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2019-01-04 18:49:03 7ff5fd2cb880 InnoDB: Error: page 1156060 log sequence number 188684502947
InnoDB: is in the future! Current system log sequence number 187096071180.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2019-01-04 18:49:03 7ff5fd2cb880 InnoDB: Error: page 1146881 log sequence number 188688498782
InnoDB: is in the future! Current system log sequence number 187096071180.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2019-01-04 18:49:03 7ff5fd2cb880 InnoDB: Error: page 1436000 log sequence number 188689944366
InnoDB: is in the future! Current system log sequence number 187096071180.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2019-01-04 18:49:03 7ff5fd2cb880 InnoDB: Error: page 1425409 log sequence number 188689883596
InnoDB: is in the future! Current system log sequence number 187096071180.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2019-01-04 18:49:03 7ff5fd2cb880 InnoDB: Error: page 45 log sequence number 188684373520
InnoDB: is in the future! Current system log sequence number 187096071180.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2019-01-04 18:49:03 7ff5fd2cb880 InnoDB: Error: page 1394945 log sequence number 188689944948
InnoDB: is in the future! Current system log sequence number 187096071180.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2019-01-04 18:49:03 7ff5fd2cb880 InnoDB: Error: page 1392641 log sequence number 188688012140
InnoDB: is in the future! Current system log sequence number 187096071180.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2019-01-04 18:49:03 7ff5fd2cb880 InnoDB: Error: page 1435986 log sequence number 188684373520
InnoDB: is in the future! Current system log sequence number 187096071180.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2019-01-04 18:49:03 7ff5fd2cb880 InnoDB: Error: page 46 log sequence number 188684504163
InnoDB: is in the future! Current system log sequence number 187096071180.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2019-01-04 18:49:03 7ff5fd2cb880 InnoDB: Error: page 1436008 log sequence number 188689945663
InnoDB: is in the future! Current system log sequence number 187096071180.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2019-01-04 18:49:03 7ff5fd2cb880 InnoDB: Error: page 1156061 log sequence number 188684504163
InnoDB: is in the future! Current system log sequence number 187096071180.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2019-01-04 18:49:03 7ff5fd2cb880 InnoDB: Error: page 47 log sequence number 188689949586
InnoDB: is in the future! Current system log sequence number 187096071180.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2019-01-04 18:49:03 7ff5fd2cb880 InnoDB: Error: page 1436016 log sequence number 188689949586
InnoDB: is in the future! Current system log sequence number 187096071180.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2019-01-04 18:49:03 7ff5fd2cb880 InnoDB: Error: page 1394724 log sequence number 188689949586
InnoDB: is in the future! Current system log sequence number 187096071180.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2019-01-04 18:49:03 7ff5fd2cb880 InnoDB: Error: page 48 log sequence number 188686690460
InnoDB: is in the future! Current system log sequence number 187096071180.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2019-01-04 18:49:03 7ff5fd2cb880 InnoDB: Error: page 1394969 log sequence number 188689950169
InnoDB: is in the future! Current system log sequence number 187096071180.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2019-01-04 18:49:03 7ff5fd2cb880 InnoDB: Error: page 1394715 log sequence number 188686690460
InnoDB: is in the future! Current system log sequence number 187096071180.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2019-01-04 18:49:03 7ff5fd2cb880 InnoDB: Error: page 49 log sequence number 188686501961
InnoDB: is in the future! Current system log sequence number 187096071180.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2019-01-04 18:49:03 7ff5fd2cb880 InnoDB: Error: page 1035142 log sequence number 188689950827
InnoDB: is in the future! Current system log sequence number 187096071180.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2019-01-04 18:49:03 7ff5fd2cb880 InnoDB: Error: page 1032193 log sequence number 188688441290
InnoDB: is in the future! Current system log sequence number 187096071180.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2019-01-04 18:49:03 7ff5fd2cb880 InnoDB: Error: page 1523718 log sequence number 188686501961
InnoDB: is in the future! Current system log sequence number 187096071180.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2019-01-04 18:49:03 7ff5fd2cb880 InnoDB: Error: page 1523713 log sequence number 187589701808
InnoDB: is in the future! Current system log sequence number 187096071180.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2019-01-04 18:49:03 7ff5fd2cb880 InnoDB: Error: page 50 log sequence number 188686509929
InnoDB: is in the future! Current system log sequence number 187096071180.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2019-01-04 18:49:03 7ff5fd2cb880 InnoDB: Error: page 1436021 log sequence number 188689951418
InnoDB: is in the future! Current system log sequence number 187096071180.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2019-01-04 18:49:03 7ff5fd2cb880 InnoDB: Error: page 1394696 log sequence number 188686509929
InnoDB: is in the future! Current system log sequence number 187096071180.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2019-01-04 18:49:03 7ff5fd2cb880 InnoDB: Error: page 51 log sequence number 188689459410
InnoDB: is in the future! Current system log sequence number 187096071180.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2019-01-04 18:49:03 7ff5fd2cb880 InnoDB: Error: page 1394954 log sequence number 188689459410
InnoDB: is in the future! Current system log sequence number 187096071180.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2019-01-04 18:49:03 7ff5fd2cb880 InnoDB: Error: page 1409035 log sequence number 188689952123
InnoDB: is in the future! Current system log sequence number 187096071180.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2019-01-04 18:49:03 7ff5fd2cb880 InnoDB: Error: page 1409025 log sequence number 188689904360
InnoDB: is in the future! Current system log sequence number 187096071180.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2019-01-04 18:49:03 7ff5fd2cb880 InnoDB: Error: page 52 log sequence number 188689857619
InnoDB: is in the future! Current system log sequence number 187096071180.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2019-01-04 18:49:03 7ff5fd2cb880 InnoDB: Error: page 1436024 log sequence number 188689952704
InnoDB: is in the future! Current system log sequence number 187096071180.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2019-01-04 18:49:03 7ff5fd2cb880 InnoDB: Error: page 53 log sequence number 188689734622
InnoDB: is in the future! Current system log sequence number 187096071180.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2019-01-04 18:49:03 7ff5fd2cb880 InnoDB: Error: page 1395202 log sequence number 188689953419
InnoDB: is in the future! Current system log sequence number 187096071180.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2019-01-04 18:49:03 7ff5fd2cb880 InnoDB: Error: page 1277990 log sequence number 188689734622
InnoDB: is in the future! Current system log sequence number 187096071180.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2019-01-04 18:49:03 7ff5fd2cb880 InnoDB: Error: page 1277953 log sequence number 188688498782
InnoDB: is in the future! Current system log sequence number 187096071180.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2019-01-04 18:49:03 7ff5fd2cb880 InnoDB: Error: page 54 log sequence number 188689956530
InnoDB: is in the future! Current system log sequence number 187096071180.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2019-01-04 18:49:03 7ff5fd2cb880 InnoDB: Error: page 1392659 log sequence number 188689956530
InnoDB: is in the future! Current system log sequence number 187096071180.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2019-01-04 18:49:03 7ff5fd2cb880 InnoDB: Error: page 1436023 log sequence number 188689956530
InnoDB: is in the future! Current system log sequence number 187096071180.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2019-01-04 18:49:03 7ff5fd2cb880 InnoDB: Error: page 55 log sequence number 188689737268
InnoDB: is in the future! Current system log sequence number 187096071180.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2019-01-04 18:49:03 7ff5fd2cb880 InnoDB: Error: page 1322177 log sequence number 188689957113
InnoDB: is in the future! Current system log sequence number 187096071180.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2019-01-04 18:49:03 7ff5fd2cb880 InnoDB: Error: page 1310721 log sequence number 188689933999
InnoDB: is in the future! Current system log sequence number 187096071180.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2019-01-04 18:49:03 7ff5fd2cb880 InnoDB: Error: page 1605678 log sequence number 188689737268
InnoDB: is in the future! Current system log sequence number 187096071180.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2019-01-04 18:49:03 7ff5fd2cb880 InnoDB: Error: page 1605633 log sequence number 188524360901
InnoDB: is in the future! Current system log sequence number 187096071180.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2019-01-04 18:49:03 7ff5fd2cb880 InnoDB: Error: page 56 log sequence number 188684511890
InnoDB: is in the future! Current system log sequence number 187096071180.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2019-01-04 18:49:03 7ff5fd2cb880 InnoDB: Error: page 1394950 log sequence number 188689957755
InnoDB: is in the future! Current system log sequence number 187096071180.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2019-01-04 18:49:03 7ff5fd2cb880 InnoDB: Error: page 1605651 log sequence number 188684511890
InnoDB: is in the future! Current system log sequence number 187096071180.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2019-01-04 18:49:03 7ff5fd2cb880 InnoDB: Error: page 57 log sequence number 188689857773
InnoDB: is in the future! Current system log sequence number 187096071180.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2019-01-04 18:49:03 7ff5fd2cb880 InnoDB: Error: page 1436031 log sequence number 188689958346
InnoDB: is in the future! Current system log sequence number 187096071180.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2019-01-04 18:49:03 7ff5fd2cb880 InnoDB: Error: page 1394727 log sequence number 188689857773
InnoDB: is in the future! Current system log sequence number 187096071180.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2019-01-04 18:49:03 7ff5fd2cb880 InnoDB: Error: page 58 log sequence number 188689740473
InnoDB: is in the future! Current system log sequence number 187096071180.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2019-01-04 18:49:03 7ff5fd2cb880 InnoDB: Error: page 1186801 log sequence number 188689959067
InnoDB: is in the future! Current system log sequence number 187096071180.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2019-01-04 18:49:03 7ff5fd2cb880 InnoDB: Error: page 1179649 log sequence number 188688440871
InnoDB: is in the future! Current system log sequence number 187096071180.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2019-01-04 18:49:03 7ff5fd2cb880 InnoDB: Error: page 1394719 log sequence number 188689740473
InnoDB: is in the future! Current system log sequence number 187096071180.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2019-01-04 18:49:03 7ff5fd2cb880 InnoDB: Error: page 59 log sequence number 188689858108
InnoDB: is in the future! Current system log sequence number 187096071180.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2019-01-04 18:49:03 7ff5fd2cb880 InnoDB: Error: page 144841 log sequence number 188689959648
InnoDB: is in the future! Current system log sequence number 187096071180.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2019-01-04 18:49:03 7ff5fd2cb880 InnoDB: Error: page 131073 log sequence number 188654240160
InnoDB: is in the future! Current system log sequence number 187096071180.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2019-01-04 18:49:03 7ff5fd2cb880 InnoDB: Error: page 60 log sequence number 188689834306
InnoDB: is in the future! Current system log sequence number 187096071180.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2019-01-04 18:49:03 7ff5fd2cb880 InnoDB: Error: page 1295319 log sequence number 188689960347
InnoDB: is in the future! Current system log sequence number 187096071180.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2019-01-04 18:49:03 7ff5fd2cb880 InnoDB: Error: page 1294337 log sequence number 188688048060
InnoDB: is in the future! Current system log sequence number 187096071180.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2019-01-04 18:49:03 7ff5fd2cb880 InnoDB: Error: page 1278010 log sequence number 188689834306
InnoDB: is in the future! Current system log sequence number 187096071180.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2019-01-04 18:49:03 7ff5fd2cb880 InnoDB: Error: page 61 log sequence number 188689963458
InnoDB: is in the future! Current system log sequence number 187096071180.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2019-01-04 18:49:03 7ff5fd2cb880 InnoDB: Error: page 1350542 log sequence number 188689963458
InnoDB: is in the future! Current system log sequence number 187096071180.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2019-01-04 18:49:03 7ff5fd2cb880 InnoDB: Error: page 1343489 log sequence number 188679171390
InnoDB: is in the future! Current system log sequence number 187096071180.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2019-01-04 18:49:03 7ff5fd2cb880 InnoDB: Error: page 1035173 log sequence number 188689963458
InnoDB: is in the future! Current system log sequence number 187096071180.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2019-01-04 18:49:03 7ff5fd2cb880 InnoDB: Error: page 62 log sequence number 188684516799
InnoDB: is in the future! Current system log sequence number 187096071180.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2019-01-04 18:49:03 7ff5fd2cb880 InnoDB: Error: page 1035154 log sequence number 188689964057
InnoDB: is in the future! Current system log sequence number 187096071180.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2019-01-04 18:49:03 7ff5fd2cb880 InnoDB: Error: page 1277970 log sequence number 188684516799
InnoDB: is in the future! Current system log sequence number 187096071180.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2019-01-04 18:49:03 7ff5fd2cb880 InnoDB: Error: page 63 log sequence number 188686519451
InnoDB: is in the future! Current system log sequence number 187096071180.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2019-01-04 18:49:03 7ff5fd2cb880 InnoDB: Error: page 144858 log sequence number 188689964699
InnoDB: is in the future! Current system log sequence number 187096071180.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2019-01-04 18:49:03 7ff5fd2cb880 InnoDB: Error: page 1149760 log sequence number 188686519451
InnoDB: is in the future! Current system log sequence number 187096071180.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2019-01-04 18:49:03 7ff5fd2cb880 InnoDB: Error: page 192 log sequence number 188687468018
InnoDB: is in the future! Current system log sequence number 187096071180.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2019-01-04 18:49:03 7ff5fd2cb880 InnoDB: Error: page 1605642 log sequence number 188689965290
InnoDB: is in the future! Current system log sequence number 187096071180.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2019-01-04 18:49:03 7ff5fd2cb880 InnoDB: Error: page 1394723 log sequence number 188687468018
InnoDB: is in the future! Current system log sequence number 187096071180.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2019-01-04 18:49:03 7ff5fd2cb880 InnoDB: Error: page 193 log sequence number 188689838896
InnoDB: is in the future! Current system log sequence number 187096071180.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2019-01-04 18:49:03 7ff5fd2cb880 InnoDB: Error: page 1035156 log sequence number 188689965995
InnoDB: is in the future! Current system log sequence number 187096071180.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2019-01-04 18:49:03 7ff5fd2cb880 InnoDB: Error: page 1149794 log sequence number 188689838896
InnoDB: is in the future! Current system log sequence number 187096071180.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2019-01-04 18:49:03 7ff5fd2cb880 InnoDB: Error: page 194 log sequence number 188684390691
InnoDB: is in the future! Current system log sequence number 187096071180.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2019-01-04 18:49:03 7ff5fd2cb880 InnoDB: Error: page 1359781 log sequence number 188689966576
InnoDB: is in the future! Current system log sequence number 187096071180.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2019-01-04 18:49:03 7ff5fd2cb880 InnoDB: Error: page 1394697 log sequence number 188684390691
InnoDB: is in the future! Current system log sequence number 187096071180.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2019-01-04 18:49:03 7ff5fd2cb880 InnoDB: Error: page 195 log sequence number 188685659362
InnoDB: is in the future! Current system log sequence number 187096071180.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2019-01-04 18:49:03 7ff5fd2cb880 InnoDB: Error: page 1195689 log sequence number 188689967291
InnoDB: is in the future! Current system log sequence number 187096071180.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2019-01-04 18:49:03 7ff5fd2cb880 InnoDB: Error: page 1186795 log sequence number 188685659362
InnoDB: is in the future! Current system log sequence number 187096071180.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2019-01-04 18:49:03 7ff5fd2cb880 InnoDB: Error: page 196 log sequence number 188689970405
InnoDB: is in the future! Current system log sequence number 187096071180.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2019-01-04 18:49:03 7ff5fd2cb880 InnoDB: Error: page 1605644 log sequence number 188689970405
InnoDB: is in the future! Current system log sequence number 187096071180.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2019-01-04 18:49:03 7ff5fd2cb880 InnoDB: Error: page 1483469 log sequence number 188689970405
InnoDB: is in the future! Current system log sequence number 187096071180.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2019-01-04 18:49:03 7ff5fd2cb880 InnoDB: Error: page 1474561 log sequence number 188616515333
InnoDB: is in the future! Current system log sequence number 187096071180.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2019-01-04 18:49:03 7ff5fd2cb880 InnoDB: Error: page 197 log sequence number 188686708337
InnoDB: is in the future! Current system log sequence number 187096071180.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2019-01-04 18:49:03 7ff5fd2cb880 InnoDB: Error: page 1156065 log sequence number 188686708337
InnoDB: is in the future! Current system log sequence number 187096071180.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2019-01-04 18:49:03 7ff5fd2cb880 InnoDB: Error: page 1394688 log sequence number 188689970988
InnoDB: is in the future! Current system log sequence number 187096071180.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2019-01-04 18:49:03 7ff5fd2cb880 InnoDB: Error: page 198 log sequence number 188689843444
InnoDB: is in the future! Current system log sequence number 187096071180.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2019-01-04 18:49:03 7ff5fd2cb880 InnoDB: Error: page 1186777 log sequence number 188689971630
InnoDB: is in the future! Current system log sequence number 187096071180.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2019-01-04 18:49:03 7ff5fd2cb880 InnoDB: Error: page 1035168 log sequence number 188689843444
InnoDB: is in the future! Current system log sequence number 187096071180.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2019-01-04 18:49:03 7ff5fd2cb880 InnoDB: Error: page 199 log sequence number 188686709715
InnoDB: is in the future! Current system log sequence number 187096071180.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2019-01-04 18:49:03 7ff5fd2cb880 InnoDB: Error: page 1490954 log sequence number 188689972237
InnoDB: is in the future! Current system log sequence number 187096071180.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2019-01-04 18:49:03 7ff5fd2cb880 InnoDB: Error: page 1490945 log sequence number 188497128973
InnoDB: is in the future! Current system log sequence number 187096071180.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2019-01-04 18:49:03 7ff5fd2cb880 InnoDB: Error: page 1156072 log sequence number 188686709715
InnoDB: is in the future! Current system log sequence number 187096071180.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2019-01-04 18:49:03 7ff5fd2cb880 InnoDB: Error: page 200 log sequence number 188687650800
InnoDB: is in the future! Current system log sequence number 187096071180.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2019-01-04 18:49:03 7ff5fd2cb880 InnoDB: Error: page 1156044 log sequence number 188687650800
InnoDB: is in the future! Current system log sequence number 187096071180.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2019-01-04 18:49:03 7ff5fd2cb880 InnoDB: Error: page 1605640 log sequence number 188689972944
InnoDB: is in the future! Current system log sequence number 187096071180.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2019-01-04 18:49:03 7ff5fd2cb880 InnoDB: Error: page 201 log sequence number 188685665980
InnoDB: is in the future! Current system log sequence number 187096071180.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2019-01-04 18:49:03 7ff5fd2cb880 InnoDB: Error: page 1149764 log sequence number 188685665980
InnoDB: is in the future! Current system log sequence number 187096071180.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2019-01-04 18:49:03 7ff5fd2cb880 InnoDB: Error: page 1523740 log sequence number 188689973525
InnoDB: is in the future! Current system log sequence number 187096071180.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2019-01-04 18:49:03 7ff5fd2cb880 InnoDB: Error: page 202 log sequence number 188685666668
InnoDB: is in the future! Current system log sequence number 187096071180.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2019-01-04 18:49:03 7ff5fd2cb880 InnoDB: Error: page 1035159 log sequence number 188689974226
InnoDB: is in the future! Current system log sequence number 187096071180.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2019-01-04 18:49:03 7ff5fd2cb880 InnoDB: Error: page 1523746 log sequence number 188685666668
InnoDB: is in the future! Current system log sequence number 187096071180.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2019-01-04 18:49:03 7ff5fd2cb880 InnoDB: Error: page 203 log sequence number 188689977356
InnoDB: is in the future! Current system log sequence number 187096071180.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2019-01-04 18:49:03 7ff5fd2cb880 InnoDB: Error: page 1359788 log sequence number 188689977356
InnoDB: is in the future! Current system log sequence number 187096071180.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2019-01-04 18:49:03 7ff5fd2cb880 InnoDB: Error: page 1294358 log sequence number 188689977356
InnoDB: is in the future! Current system log sequence number 187096071180.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2019-01-04 18:49:03 7ff5fd2cb880 InnoDB: Error: page 204 log sequence number 188684526102
InnoDB: is in the future! Current system log sequence number 187096071180.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2019-01-04 18:49:03 7ff5fd2cb880 InnoDB: Error: page 1523757 log sequence number 188689977939
InnoDB: is in the future! Current system log sequence number 187096071180.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2019-01-04 18:49:03 7ff5fd2cb880 InnoDB: Error: page 1149802 log sequence number 188684526102
InnoDB: is in the future! Current system log sequence number 187096071180.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2019-01-04 18:49:03 7ff5fd2cb880 InnoDB: Error: page 205 log sequence number 188686659894
InnoDB: is in the future! Current system log sequence number 187096071180.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2019-01-04 18:49:03 7ff5fd2cb880 InnoDB: Error: page 144859 log sequence number 188689978581
InnoDB: is in the future! Current system log sequence number 187096071180.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2019-01-04 18:49:03 7ff5fd2cb880 InnoDB: Error: page 206 log sequence number 188689858228
InnoDB: is in the future! Current system log sequence number 187096071180.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2019-01-04 18:49:03 7ff5fd2cb880 InnoDB: Error: page 1435976 log sequence number 188689979172
InnoDB: is in the future! Current system log sequence number 187096071180.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2019-01-04 18:49:03 7ff5fd2cb880 InnoDB: Error: page 207 log sequence number 188672416935
InnoDB: is in the future! Current system log sequence number 187096071180.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2019-01-04 18:49:03 7ff5fd2cb880 InnoDB: Error: page 1186781 log sequence number 188685799574
InnoDB: is in the future! Current system log sequence number 187096071180.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2019-01-04 18:49:03 7ff5fd2cb880  InnoDB: Assertion failure in thread 140694491281536 in file fut0lst.ic line 83
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.6/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
13:49:03 UTC - xtrabackup got signal 6 ;
This could be because you hit a bug or data is corrupted.
This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help
diagnose the problem, but since we have already crashed, 
something is definitely wrong and this may fail.

Thread pointer: 0x0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = 0 thread_stack 0x10000
xtrabackup(my_print_stacktrace+0x2e) [0x97420e]
xtrabackup(handle_fatal_signal+0x262) [0x726862]
/lib64/libpthread.so.0(+0xf6d0) [0x7ff5fceb06d0]
/lib64/libc.so.6(gsignal+0x37) [0x7ff5faf3f277]
/lib64/libc.so.6(abort+0x148) [0x7ff5faf40968]
xtrabackup() [0x574df5]
xtrabackup(trx_undo_lists_init(trx_rseg_t*)+0x8e5) [0x6ac4b5]
xtrabackup() [0x9e56da]
xtrabackup(trx_rseg_array_init(unsigned char*, ib_bh_t*, mtr_t*)+0x75) [0x9e6225]
xtrabackup(trx_sys_init_at_db_start()+0x2bf) [0x63feff]
xtrabackup(innobase_start_or_create_for_mysql()+0x18bb) [0x71db9b]
xtrabackup() [0x5978f9]
xtrabackup(main+0x127d) [0x582e3d]
/lib64/libc.so.6(__libc_start_main+0xf5) [0x7ff5faf2b445]
xtrabackup() [0x59628e]

Please report a bug at https://bugs.launchpad.net/percona-xtrabackup