180131 16:57:16 mysqld_safe Starting mysqld daemon with databases from /data/mysql_data 2018-01-31 16:57:17 15947 [Note] Plugin 'FEDERATED' is disabled. 2018-01-31 16:57:17 15947 [Note] InnoDB: Using atomics to ref count buffer pool pages 2018-01-31 16:57:17 15947 [Note] InnoDB: The InnoDB memory heap is disabled 2018-01-31 16:57:17 15947 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 2018-01-31 16:57:17 15947 [Note] InnoDB: Memory barrier is not used 2018-01-31 16:57:17 15947 [Note] InnoDB: Compressed tables use zlib 1.2.3 2018-01-31 16:57:17 15947 [Note] InnoDB: Using CPU crc32 instructions 2018-01-31 16:57:17 15947 [Note] InnoDB: Initializing buffer pool, size = 512.0M 2018-01-31 16:57:17 15947 [Note] InnoDB: Completed initialization of buffer pool 2018-01-31 16:57:17 15947 [Note] InnoDB: Highest supported file format is Barracuda. 2018-01-31 16:57:17 15947 [Note] InnoDB: The log sequence numbers 129638848168 and 129638848168 in ibdata files do not match the log sequence number 129638848524 in the ib_logfiles! 2018-01-31 16:57:17 15947 [Note] InnoDB: Database was not shutdown normally! 2018-01-31 16:57:17 15947 [Note] InnoDB: Starting crash recovery. 2018-01-31 16:57:17 15947 [Note] InnoDB: Reading tablespace information from the .ibd files... 2018-01-31 16:57:17 15947 [Note] InnoDB: Restoring possible half-written data pages 2018-01-31 16:57:17 15947 [Note] InnoDB: from the doublewrite buffer... 2018-01-31 16:57:17 7fee6965f7e0 InnoDB: Error: page 2 log sequence number 130193712410 InnoDB: is in the future! Current system log sequence number 129638848524. 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. 2018-01-31 16:57:17 7fee6965f7e0 InnoDB: Error: page 4 log sequence number 130348902317 InnoDB: is in the future! Current system log sequence number 129638848524. 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. 2018-01-31 16:57:17 7fee6965f7e0 InnoDB: Error: page 5 log sequence number 130352473100 InnoDB: is in the future! Current system log sequence number 129638848524. 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. 2018-01-31 16:57:17 7fee6965f7e0 InnoDB: Error: page 6 log sequence number 129895977079 InnoDB: is in the future! Current system log sequence number 129638848524. 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. 2018-01-31 16:57:17 7fee6965f7e0 InnoDB: Error: page 5264 log sequence number 129895977079 InnoDB: is in the future! Current system log sequence number 129638848524. 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. 2018-01-31 16:57:17 7fee6965f7e0 InnoDB: Error: page 452 log sequence number 129888397462 InnoDB: is in the future! Current system log sequence number 129638848524. 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. 2018-01-31 16:57:17 7fee6965f7e0 InnoDB: Error: page 45 log sequence number 129896120351 InnoDB: is in the future! Current system log sequence number 129638848524. 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. 2018-01-31 16:57:17 7fee6965f7e0 InnoDB: Error: page 4373 log sequence number 129889094029 InnoDB: is in the future! Current system log sequence number 129638848524. 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. 2018-01-31 16:57:17 7fee6965f7e0 InnoDB: Error: page 46 log sequence number 129893833327 InnoDB: is in the future! Current system log sequence number 129638848524. 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. 2018-01-31 16:57:17 7fee6965f7e0 InnoDB: Error: page 7358 log sequence number 129893833327 InnoDB: is in the future! Current system log sequence number 129638848524. 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. 2018-01-31 16:57:17 7fee6965f7e0 InnoDB: Error: page 5187 log sequence number 129888397817 InnoDB: is in the future! Current system log sequence number 129638848524. 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. 2018-01-31 16:57:17 7fee6965f7e0 InnoDB: Error: page 47 log sequence number 129896120462 InnoDB: is in the future! Current system log sequence number 129638848524. 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. 2018-01-31 16:57:17 7fee6965f7e0 InnoDB: Error: page 7590 log sequence number 129889469386 InnoDB: is in the future! Current system log sequence number 129638848524. 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. 2018-01-31 16:57:17 7fee6965f7e0 InnoDB: Error: page 48 log sequence number 129895488319 InnoDB: is in the future! Current system log sequence number 129638848524. 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. 2018-01-31 16:57:17 7fee6965f7e0 InnoDB: Error: page 49198 log sequence number 129895488319 InnoDB: is in the future! Current system log sequence number 129638848524. 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. 2018-01-31 16:57:17 7fee6965f7e0 InnoDB: Error: page 49207 log sequence number 129889495361 InnoDB: is in the future! Current system log sequence number 129638848524. 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. 2018-01-31 16:57:17 7fee6965f7e0 InnoDB: Error: page 49 log sequence number 129895266010 InnoDB: is in the future! Current system log sequence number 129638848524. 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. 2018-01-31 16:57:17 7fee6965f7e0 InnoDB: Error: page 7556 log sequence number 129889495794 InnoDB: is in the future! Current system log sequence number 129638848524. 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. 2018-01-31 16:57:17 7fee6965f7e0 InnoDB: Error: page 50 log sequence number 129895266121 InnoDB: is in the future! Current system log sequence number 129638848524. 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. 2018-01-31 16:57:17 7fee6965f7e0 InnoDB: Error: page 49205 log sequence number 129895266121 InnoDB: is in the future! Current system log sequence number 129638848524. 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. 2018-01-31 16:57:17 7fee6965f7e0 InnoDB: Error: page 4365 log sequence number 129888336910 InnoDB: is in the future! Current system log sequence number 129638848524. 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. 2018-01-31 16:57:17 7fee6965f7e0 InnoDB: Error: page 51 log sequence number 129894489816 InnoDB: is in the future! Current system log sequence number 129638848524. 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. 2018-01-31 16:57:17 7fee6965f7e0 InnoDB: Error: page 573 log sequence number 129888338105 InnoDB: is in the future! Current system log sequence number 129638848524. 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. 2018-01-31 16:57:17 7fee6965f7e0 InnoDB: Error: page 52 log sequence number 129889952793 InnoDB: is in the future! Current system log sequence number 129638848524. 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. 2018-01-31 16:57:17 7fee6965f7e0 InnoDB: Error: page 5199 log sequence number 129889952793 InnoDB: is in the future! Current system log sequence number 129638848524. 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. 2018-01-31 16:57:17 7fee6965f7e0 InnoDB: Error: page 74791 log sequence number 129888338582 InnoDB: is in the future! Current system log sequence number 129638848524. 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. 2018-01-31 16:57:17 7fee6965f7e0 InnoDB: Error: page 53 log sequence number 129893615087 InnoDB: is in the future! Current system log sequence number 129638848524. 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. 2018-01-31 16:57:17 7fee6965f7e0 InnoDB: Error: page 49155 log sequence number 129893615087 InnoDB: is in the future! Current system log sequence number 129638848524. 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. 2018-01-31 16:57:17 7fee6965f7e0 InnoDB: Error: page 5208 log sequence number 129888339542 InnoDB: is in the future! Current system log sequence number 129638848524. 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. 2018-01-31 16:57:17 7fee6965f7e0 InnoDB: Error: page 54 log sequence number 129895365693 InnoDB: is in the future! Current system log sequence number 129638848524. 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. 2018-01-31 16:57:17 7fee6965f7e0 InnoDB: Error: page 49154 log sequence number 129895365693 InnoDB: is in the future! Current system log sequence number 129638848524. 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. 2018-01-31 16:57:17 7fee6965f7e0 InnoDB: Error: page 523 log sequence number 129888339909 InnoDB: is in the future! Current system log sequence number 129638848524. 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. 2018-01-31 16:57:17 7fee6965f7e0 InnoDB: Error: page 55 log sequence number 129895266232 InnoDB: is in the future! Current system log sequence number 129638848524. 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. 2018-01-31 16:57:17 7fee6965f7e0 InnoDB: Error: page 49193 log sequence number 129895266232 InnoDB: is in the future! Current system log sequence number 129638848524. 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. 2018-01-31 16:57:17 7fee6965f7e0 InnoDB: Error: page 7612 log sequence number 129888340279 InnoDB: is in the future! Current system log sequence number 129638848524. 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. 2018-01-31 16:57:17 7fee6965f7e0 InnoDB: Error: page 56 log sequence number 130153328450 InnoDB: is in the future! Current system log sequence number 129638848524. 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. 2018-01-31 16:57:17 7fee6965f7e0 InnoDB: Error: page 49206 log sequence number 130153328450 InnoDB: is in the future! Current system log sequence number 129638848524. 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. 2018-01-31 16:57:17 7fee6965f7e0 InnoDB: Error: page 478 log sequence number 129888341481 InnoDB: is in the future! Current system log sequence number 129638848524. 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. 2018-01-31 16:57:17 7fee6965f7e0 InnoDB: Error: page 57 log sequence number 130153311785 InnoDB: is in the future! Current system log sequence number 129638848524. 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. 2018-01-31 16:57:17 7fee6965f7e0 InnoDB: Error: page 74802 log sequence number 129888341958 InnoDB: is in the future! Current system log sequence number 129638848524. 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. 2018-01-31 16:57:17 7fee6965f7e0 InnoDB: Error: page 49162 log sequence number 130153311785 InnoDB: is in the future! Current system log sequence number 129638848524. 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. 2018-01-31 16:57:17 7fee6965f7e0 InnoDB: Error: page 58 log sequence number 129896120573 InnoDB: is in the future! Current system log sequence number 129638848524. 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. 2018-01-31 16:57:17 7fee6965f7e0 InnoDB: Error: page 49175 log sequence number 129888342925 InnoDB: is in the future! Current system log sequence number 129638848524. 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. 2018-01-31 16:57:17 7fee6965f7e0 InnoDB: Error: page 59 log sequence number 129895830989 InnoDB: is in the future! Current system log sequence number 129638848524. 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. 2018-01-31 16:57:17 7fee6965f7e0 InnoDB: Error: page 5258 log sequence number 129895830989 InnoDB: is in the future! Current system log sequence number 129638848524. 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. 2018-01-31 16:57:17 7fee6965f7e0 InnoDB: Error: page 1655 log sequence number 129888343307 InnoDB: is in the future! Current system log sequence number 129638848524. 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. 2018-01-31 16:57:17 7fee6965f7e0 InnoDB: Error: page 60 log sequence number 129895661003 InnoDB: is in the future! Current system log sequence number 129638848524. 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. 2018-01-31 16:57:17 7fee6965f7e0 InnoDB: Error: page 493 log sequence number 129888343677 InnoDB: is in the future! Current system log sequence number 129638848524. 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. 2018-01-31 16:57:17 7fee6965f7e0 InnoDB: Error: page 61 log sequence number 129895657949 InnoDB: is in the future! Current system log sequence number 129638848524. 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. 2018-01-31 16:57:17 7fee6965f7e0 InnoDB: Error: page 12259 log sequence number 129888344825 InnoDB: is in the future! Current system log sequence number 129638848524. 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. 2018-01-31 16:57:17 7fee6965f7e0 InnoDB: Error: page 49167 log sequence number 129895657949 InnoDB: is in the future! Current system log sequence number 129638848524. 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. 2018-01-31 16:57:17 7fee6965f7e0 InnoDB: Error: page 62 log sequence number 129895510219 InnoDB: is in the future! Current system log sequence number 129638848524. 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. 2018-01-31 16:57:17 7fee6965f7e0 InnoDB: Error: page 5296 log sequence number 129888289082 InnoDB: is in the future! Current system log sequence number 129638848524. 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. 2018-01-31 16:57:17 7fee6965f7e0 InnoDB: Error: page 49159 log sequence number 129895510219 InnoDB: is in the future! Current system log sequence number 129638848524. 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. 2018-01-31 16:57:17 7fee6965f7e0 InnoDB: Error: page 63 log sequence number 129893835735 InnoDB: is in the future! Current system log sequence number 129638848524. 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. 2018-01-31 16:57:17 7fee6965f7e0 InnoDB: Error: page 49160 log sequence number 129893835735 InnoDB: is in the future! Current system log sequence number 129638848524. 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. 2018-01-31 16:57:17 7fee6965f7e0 InnoDB: Error: page 65576 log sequence number 129888289559 InnoDB: is in the future! Current system log sequence number 129638848524. 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. 2018-01-31 16:57:17 7fee6965f7e0 InnoDB: Error: page 192 log sequence number 129896000325 InnoDB: is in the future! Current system log sequence number 129638848524. 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. 2018-01-31 16:57:17 7fee6965f7e0 InnoDB: Error: page 49156 log sequence number 129896000325 InnoDB: is in the future! Current system log sequence number 129638848524. 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. 2018-01-31 16:57:17 7fee6965f7e0 InnoDB: Error: page 5245 log sequence number 129888290761 InnoDB: is in the future! Current system log sequence number 129638848524. 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. 2018-01-31 16:57:17 7fee6965f7e0 InnoDB: Error: page 193 log sequence number 129895998808 InnoDB: is in the future! Current system log sequence number 129638848524. 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. 2018-01-31 16:57:17 7fee6965f7e0 InnoDB: Error: page 7328 log sequence number 129893665717 InnoDB: is in the future! Current system log sequence number 129638848524. 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. 2018-01-31 16:57:17 7fee6965f7e0 InnoDB: Error: page 5243 log sequence number 129895998808 InnoDB: is in the future! Current system log sequence number 129638848524. 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. 2018-01-31 16:57:17 7fee6965f7e0 InnoDB: Error: page 194 log sequence number 129895635807 InnoDB: is in the future! Current system log sequence number 129638848524. 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. 2018-01-31 16:57:17 7fee6965f7e0 InnoDB: Error: page 21406 log sequence number 129888345669 InnoDB: is in the future! Current system log sequence number 129638848524. 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. 2018-01-31 16:57:17 7fee6965f7e0 InnoDB: Error: page 195 log sequence number 129895533384 InnoDB: is in the future! Current system log sequence number 129638848524. 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. 2018-01-31 16:57:17 7fee6965f7e0 InnoDB: Error: page 7577 log sequence number 129895533384 InnoDB: is in the future! Current system log sequence number 129638848524. 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. 2018-01-31 16:57:17 7fee6965f7e0 InnoDB: Error: page 14996 log sequence number 129888292808 InnoDB: is in the future! Current system log sequence number 129638848524. 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. 2018-01-31 16:57:17 7fee6965f7e0 InnoDB: Error: page 196 log sequence number 129894854048 InnoDB: is in the future! Current system log sequence number 129638848524. 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. 2018-01-31 16:57:17 7fee6965f7e0 InnoDB: Error: page 49194 log sequence number 129894854048 InnoDB: is in the future! Current system log sequence number 129638848524. 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. 2018-01-31 16:57:17 7fee6965f7e0 InnoDB: Error: page 7943 log sequence number 129888293273 InnoDB: is in the future! Current system log sequence number 129638848524. 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. 2018-01-31 16:57:17 7fee6965f7e0 InnoDB: Error: page 197 log sequence number 129895855708 InnoDB: is in the future! Current system log sequence number 129638848524. 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. 2018-01-31 16:57:17 7fee6965f7e0 InnoDB: Error: page 5260 log sequence number 129895855708 InnoDB: is in the future! Current system log sequence number 129638848524. 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. 2018-01-31 16:57:17 7fee6965f7e0 InnoDB: Error: page 7993 log sequence number 129888294228 InnoDB: is in the future! Current system log sequence number 129638848524. 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. 2018-01-31 16:57:17 7fee6965f7e0 InnoDB: Error: page 198 log sequence number 129895854401 InnoDB: is in the future! Current system log sequence number 129638848524. 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. 2018-01-31 16:57:17 7fee6965f7e0 InnoDB: Error: page 5259 log sequence number 129895854401 InnoDB: is in the future! Current system log sequence number 129638848524. 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. 2018-01-31 16:57:17 7fee6965f7e0 InnoDB: Error: page 12244 log sequence number 129888294610 InnoDB: is in the future! Current system log sequence number 129638848524. 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. 2018-01-31 16:57:17 7fee6965f7e0 InnoDB: Error: page 199 log sequence number 129894442616 InnoDB: is in the future! Current system log sequence number 129638848524. 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. 2018-01-31 16:57:17 7fee6965f7e0 InnoDB: Error: page 7991 log sequence number 129894442616 InnoDB: is in the future! Current system log sequence number 129638848524. 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. 2018-01-31 16:57:17 7fee6965f7e0 InnoDB: Error: page 20671 log sequence number 129888294992 InnoDB: is in the future! Current system log sequence number 129638848524. 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. 2018-01-31 16:57:17 7fee6965f7e0 InnoDB: Error: page 200 log sequence number 129895266691 InnoDB: is in the future! Current system log sequence number 129638848524. 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. 2018-01-31 16:57:17 7fee6965f7e0 InnoDB: Error: page 49200 log sequence number 129895266691 InnoDB: is in the future! Current system log sequence number 129638848524. 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. 2018-01-31 16:57:17 7fee6965f7e0 InnoDB: Error: page 545 log sequence number 129888296226 InnoDB: is in the future! Current system log sequence number 129638848524. 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. 2018-01-31 16:57:17 7fee6965f7e0 InnoDB: Error: page 201 log sequence number 129894852498 InnoDB: is in the future! Current system log sequence number 129638848524. 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. 2018-01-31 16:57:17 7fee6965f7e0 InnoDB: Error: page 49188 log sequence number 129894852498 InnoDB: is in the future! Current system log sequence number 129638848524. 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. 2018-01-31 16:57:17 7fee6965f7e0 InnoDB: Error: page 7947 log sequence number 129888226182 InnoDB: is in the future! Current system log sequence number 129638848524. 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. 2018-01-31 16:57:17 7fee6965f7e0 InnoDB: Error: page 202 log sequence number 129895266806 InnoDB: is in the future! Current system log sequence number 129638848524. 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. 2018-01-31 16:57:17 7fee6965f7e0 InnoDB: Error: page 553 log sequence number 129893144706 InnoDB: is in the future! Current system log sequence number 129638848524. 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. 2018-01-31 16:57:17 7fee6965f7e0 InnoDB: Error: page 203 log sequence number 129895266937 InnoDB: is in the future! Current system log sequence number 129638848524. 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. 2018-01-31 16:57:17 7fee6965f7e0 InnoDB: Error: page 49208 log sequence number 129895266937 InnoDB: is in the future! Current system log sequence number 129638848524. 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. 2018-01-31 16:57:17 7fee6965f7e0 InnoDB: Error: page 4375 log sequence number 129888347424 InnoDB: is in the future! Current system log sequence number 129638848524. 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. 2018-01-31 16:57:17 7fee6965f7e0 InnoDB: Error: page 204 log sequence number 129894659061 InnoDB: is in the future! Current system log sequence number 129638848524. 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. 2018-01-31 16:57:17 7fee6965f7e0 InnoDB: Error: page 65547 log sequence number 129888347819 InnoDB: is in the future! Current system log sequence number 129638848524. 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. 2018-01-31 16:57:17 7fee6965f7e0 InnoDB: Error: page 49189 log sequence number 129894659061 InnoDB: is in the future! Current system log sequence number 129638848524. 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. 2018-01-31 16:57:17 7fee6965f7e0 InnoDB: Error: page 205 log sequence number 129893022875 InnoDB: is in the future! Current system log sequence number 129638848524. 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. 2018-01-31 16:57:17 7fee6965f7e0 InnoDB: Error: page 7982 log sequence number 129893022875 InnoDB: is in the future! Current system log sequence number 129638848524. 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. 2018-01-31 16:57:17 7fee6965f7e0 InnoDB: Error: page 65548 log sequence number 129888298017 InnoDB: is in the future! Current system log sequence number 129638848524. 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. 2018-01-31 16:57:17 7fee6965f7e0 InnoDB: Error: page 206 log sequence number 129894489928 InnoDB: is in the future! Current system log sequence number 129638848524. 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. 2018-01-31 16:57:17 7fee6965f7e0 InnoDB: Error: page 15020 log sequence number 129888348189 InnoDB: is in the future! Current system log sequence number 129638848524. 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. 2018-01-31 16:57:17 7fee6965f7e0 InnoDB: Error: page 207 log sequence number 129896024477 InnoDB: is in the future! Current system log sequence number 129638848524. 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. 2018-01-31 16:57:17 7fee6965f7e0 InnoDB: Error: page 5267 log sequence number 129896024477 InnoDB: is in the future! Current system log sequence number 129638848524. 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. 2018-01-31 16:57:17 7fee6965f7e0 InnoDB: Error: page 5222 log sequence number 129888349323 InnoDB: is in the future! Current system log sequence number 129638848524. 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. 2018-01-31 16:57:17 7fee6965f7e0 InnoDB: Error: page 208 log sequence number 129894490040 InnoDB: is in the future! Current system log sequence number 129638848524. 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. 2018-01-31 16:57:17 7fee6965f7e0 InnoDB: Error: page 49183 log sequence number 129894490040 InnoDB: is in the future! Current system log sequence number 129638848524. 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. 2018-01-31 16:57:17 7fee6965f7e0 InnoDB: Error: page 5211 log sequence number 129888229204 InnoDB: is in the future! Current system log sequence number 129638848524. 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. 2018-01-31 16:57:17 7fee6965f7e0 InnoDB: Error: page 209 log sequence number 129896022540 InnoDB: is in the future! Current system log sequence number 129638848524. 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. 2018-01-31 16:57:17 7fee6965f7e0 InnoDB: Error: page 49182 log sequence number 129896022540 InnoDB: is in the future! Current system log sequence number 129638848524. 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. 2018-01-31 16:57:17 7fee6965f7e0 InnoDB: Error: page 7593 log sequence number 129889273099 InnoDB: is in the future! Current system log sequence number 129638848524. 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. 2018-01-31 16:57:17 7fee6965f7e0 InnoDB: Error: page 210 log sequence number 129895389885 InnoDB: is in the future! Current system log sequence number 129638848524. 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. 2018-01-31 16:57:17 7fee6965f7e0 InnoDB: Error: page 49184 log sequence number 129895389885 InnoDB: is in the future! Current system log sequence number 129638848524. 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. 2018-01-31 16:57:17 7fee6965f7e0 InnoDB: Error: page 4412 log sequence number 129892357206 InnoDB: is in the future! Current system log sequence number 129638848524. 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. 2018-01-31 16:57:17 7fee6965f7e0 InnoDB: Error: page 211 log sequence number 129895685737 InnoDB: is in the future! Current system log sequence number 129638848524. 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. 2018-01-31 16:57:17 7fee6965f7e0 InnoDB: Error: page 5250 log sequence number 129895685737 InnoDB: is in the future! Current system log sequence number 129638848524. 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. 2018-01-31 16:57:17 7fee6965f7e0 InnoDB: Error: page 5309 log sequence number 129892541357 InnoDB: is in the future! Current system log sequence number 129638848524. 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. 2018-01-31 16:57:17 7fee6965f7e0 InnoDB: Error: page 212 log sequence number 129896241370 InnoDB: is in the future! Current system log sequence number 129638848524. 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. 2018-01-31 16:57:17 7fee6965f7e0 InnoDB: Error: page 5251 log sequence number 129896241370 InnoDB: is in the future! Current system log sequence number 129638848524. 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. 2018-01-31 16:57:17 7fee6965f7e0 InnoDB: Error: page 49181 log sequence number 129893145054 InnoDB: is in the future! Current system log sequence number 129638848524. 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. 2018-01-31 16:57:17 7fee6965f7e0 InnoDB: Error: page 213 log sequence number 130193709457 InnoDB: is in the future! Current system log sequence number 129638848524. 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. 2018-01-31 16:57:17 7fee6965f7e0 InnoDB: Error: page 4355 log sequence number 129888351687 InnoDB: is in the future! Current system log sequence number 129638848524. 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. 2018-01-31 16:57:17 7fee6965f7e0 InnoDB: Error: page 214 log sequence number 129895265901 InnoDB: is in the future! Current system log sequence number 129638848524. 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. 2018-01-31 16:57:17 7fee6965f7e0 InnoDB: Error: page 7950 log sequence number 129895265901 InnoDB: is in the future! Current system log sequence number 129638848524. 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. 2018-01-31 16:57:17 7fee6965f7e0 InnoDB: Error: page 21390 log sequence number 129888352655 InnoDB: is in the future! Current system log sequence number 129638848524. 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. 2018-01-31 16:57:17 7fee6965f7e0 InnoDB: Error: page 215 log sequence number 129893640098 InnoDB: is in the future! Current system log sequence number 129638848524. 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. 2018-01-31 16:57:17 7fee6965f7e0 InnoDB: Error: page 7951 log sequence number 129893640098 InnoDB: is in the future! Current system log sequence number 129638848524. 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. 2018-01-31 16:57:17 7fee6965f7e0 InnoDB: Error: page 7999 log sequence number 129893145894 InnoDB: is in the future! Current system log sequence number 129638848524. 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. 2018-01-31 16:57:17 7fee6965f7e0 InnoDB: Error: page 216 log sequence number 129896120688 InnoDB: is in the future! Current system log sequence number 129638848524. 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. 2018-01-31 16:57:17 7fee6965f7e0 InnoDB: Error: page 7572 log sequence number 129893146312 InnoDB: is in the future! Current system log sequence number 129638848524. 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. 2018-01-31 16:57:17 7fee6965f7e0 InnoDB: Error: page 217 log sequence number 129896047094 InnoDB: is in the future! Current system log sequence number 129638848524. 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. 2018-01-31 16:57:17 7fee6965f7e0 InnoDB: Error: page 7944 log sequence number 129896047094 InnoDB: is in the future! Current system log sequence number 129638848524. 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. 2018-01-31 16:57:17 7fee6965f7e0 InnoDB: Error: page 5302 log sequence number 129892359287 InnoDB: is in the future! Current system log sequence number 129638848524. 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. 2018-01-31 16:57:17 7fee6965f7e0 InnoDB: Error: page 218 log sequence number 129895267052 InnoDB: is in the future! Current system log sequence number 129638848524. 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. 2018-01-31 16:57:17 7fee6965f7e0 InnoDB: Error: page 32796 log sequence number 129888353955 InnoDB: is in the future! Current system log sequence number 129638848524. 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. 2018-01-31 16:57:17 7fee6965f7e0 InnoDB: Error: page 219 log sequence number 129895267169 InnoDB: is in the future! Current system log sequence number 129638848524. 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. 2018-01-31 16:57:17 7fee6965f7e0 InnoDB: Error: page 21416 log sequence number 129888354422 InnoDB: is in the future! Current system log sequence number 129638848524. 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. 2018-01-31 16:57:17 7fee6965f7e0 InnoDB: Error: page 220 log sequence number 129895877935 InnoDB: is in the future! Current system log sequence number 129638848524. 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. 2018-01-31 16:57:17 7fee6965f7e0 InnoDB: Error: page 5261 log sequence number 129895877935 InnoDB: is in the future! Current system log sequence number 129638848524. 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. 2018-01-31 16:57:17 7fee6965f7e0 InnoDB: Error: page 4376 log sequence number 129892390584 InnoDB: is in the future! Current system log sequence number 129638848524. 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. 2018-01-31 16:57:17 7fee6965f7e0 InnoDB: Error: page 221 log sequence number 130193709633 InnoDB: is in the future! Current system log sequence number 129638848524. 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. 2018-01-31 16:57:17 7fee6965f7e0 InnoDB: Error: page 14986 log sequence number 129893146711 InnoDB: is in the future! Current system log sequence number 129638848524. 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. 2018-01-31 16:57:17 7fee6965f7e0 InnoDB: Error: page 222 log sequence number 129896265883 InnoDB: is in the future! Current system log sequence number 129638848524. 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. 2018-01-31 16:57:17 7fee6965f7e0 InnoDB: Error: page 5271 log sequence number 129896265883 InnoDB: is in the future! Current system log sequence number 129638848524. 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. 2018-01-31 16:57:17 7fee6965f7e0 InnoDB: Error: page 5206 log sequence number 129889274383 InnoDB: is in the future! Current system log sequence number 129638848524. 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. 2018-01-31 16:57:17 7fee6965f7e0 InnoDB: Error: page 223 log sequence number 129895636053 InnoDB: is in the future! Current system log sequence number 129638848524. 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. 2018-01-31 16:57:17 7fee6965f7e0 InnoDB: Error: page 5212 log sequence number 129888357033 InnoDB: is in the future! Current system log sequence number 129638848524. 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. 2018-01-31 16:57:17 7fee6965f7e0 InnoDB: Error: page 224 log sequence number 130035194317 InnoDB: is in the future! Current system log sequence number 129638848524. 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. 2018-01-31 16:57:17 7fee6965f7e0 InnoDB: Error: page 49210 log sequence number 130035194317 InnoDB: is in the future! Current system log sequence number 129638848524. 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. 2018-01-31 16:57:17 7fee6965f7e0 InnoDB: Error: page 15012 log sequence number 129888357425 InnoDB: is in the future! Current system log sequence number 129638848524. 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. 2018-01-31 16:57:17 7fee6965f7e0 InnoDB: Error: page 225 log sequence number 130352473100 InnoDB: is in the future! Current system log sequence number 129638848524. 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. 2018-01-31 16:57:17 7fee6965f7e0 InnoDB: Error: page 4352 log sequence number 130035212478 InnoDB: is in the future! Current system log sequence number 129638848524. 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. InnoDB: Error: trying to access page number 1902106604 in space 0, InnoDB: space name /data/mysql_data/ibdata1, InnoDB: which is outside the tablespace bounds. InnoDB: Byte offset 0, len 16384, i/o type 10. InnoDB: If you get this error at mysqld startup, please check that InnoDB: your my.cnf matches the ibdata files that you have in the InnoDB: MySQL server. 2018-01-31 16:57:17 7fee6965f7e0 InnoDB: Assertion failure in thread 140661947234272 in file fil0fil.cc line 5594 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. 08:57:17 UTC - mysqld got signal 6 ; This could be because you hit a bug. It is also possible that this binary or one of the libraries it was linked against is corrupt, improperly built, or misconfigured. This error can also be caused by malfunctioning hardware. We will try our best to scrape up some info that will hopefully help diagnose the problem, but since we have already crashed, something is definitely wrong and this may fail. key_buffer_size=67108864 read_buffer_size=1048576 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 = 376849 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x0 Attempting backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong... stack_bottom = 0 thread_stack 0x40000 /home/wenba/mysql-latest/bin/mysqld(my_print_stacktrace+0x35)[0x8e7c25] /home/wenba/mysql-latest/bin/mysqld(handle_fatal_signal+0x41b)[0x65582b] /lib64/libpthread.so.0(+0xf710)[0x7fee69245710] /lib64/libc.so.6(gsignal+0x35)[0x7fee6788a625] /lib64/libc.so.6(abort+0x175)[0x7fee6788be05] /home/wenba/mysql-latest/bin/mysqld[0xa85c37] /home/wenba/mysql-latest/bin/mysqld[0xa56e7a] /home/wenba/mysql-latest/bin/mysqld[0xa57597] /home/wenba/mysql-latest/bin/mysqld[0xa458b5] /home/wenba/mysql-latest/bin/mysqld[0xa1412e] /home/wenba/mysql-latest/bin/mysqld[0xa09416] /home/wenba/mysql-latest/bin/mysqld[0xa097a2] /home/wenba/mysql-latest/bin/mysqld[0xa0bb3e] /home/wenba/mysql-latest/bin/mysqld[0x9f6605] /home/wenba/mysql-latest/bin/mysqld[0x9458b7] /home/wenba/mysql-latest/bin/mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x48)[0x592218] /home/wenba/mysql-latest/bin/mysqld[0x6e7646] /home/wenba/mysql-latest/bin/mysqld(_Z11plugin_initPiPPci+0xb3e)[0x6eae7e] /home/wenba/mysql-latest/bin/mysqld[0x585ef5] /home/wenba/mysql-latest/bin/mysqld(_Z11mysqld_mainiPPc+0x4ec)[0x58a8dc] /lib64/libc.so.6(__libc_start_main+0xfd)[0x7fee67876d5d] /home/wenba/mysql-latest/bin/mysqld[0x57c589] 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. 180131 16:57:17 mysqld_safe mysqld from pid file /data/mysql_data/ooo-test.pid ended
数据文件损坏，修改my.cnf：innodb_force_recovery=6
先恢复启动，然后导出数据再重建。
http://blog.itpub.net/22664653/viewspace-1441389/
https://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html