Akonadi Server Self-Test Report
===============================

Test 1:  SUCCESS
--------

Database driver found.
Details: The QtSQL driver 'QMYSQL' is required by your current Akonadi server configuration and was found on your system.

File content of '/home/ryszard/.config/akonadi/akonadiserverrc':
[%General]
Driver=QMYSQL

[QMYSQL]
Name=akonadi
Host=
Options="UNIX_SOCKET=/tmp/akonadi-ryszard.VevqAR/mysql.socket"
ServerPath=/usr/sbin/mysqld
StartServer=true

[Debug]
Tracer=null


Test 2:  SUCCESS
--------

Akonadi is not running as root
Details: Akonadi is not running as a root/administrator user, which is the recommended setup for a secure system.

Test 3:  SUCCESS
--------

MySQL server found.
Details: You have currently configured Akonadi to use the MySQL server '/usr/sbin/mysqld'.
Make sure you have the MySQL server installed, set the correct path and ensure you have the necessary read and execution rights on the server executable. The server executable is typically called 'mysqld'; its location varies depending on the distribution.

Test 4:  SUCCESS
--------

MySQL server is executable.
Details: MySQL server found: 170928 15:31:53 [Note] /usr/sbin/mysqld (mysqld 10.0.32-MariaDB) starting as process 22871 ...
/usr/sbin/mysqld  Ver 10.0.32-MariaDB for Linux on x86_64 (Mageia MariaDB Server)


Test 5:  ERROR
--------

MySQL server log contains errors.
Details: The MySQL server error log file &apos;<a href='/home/ryszard/.local/share/akonadi/db_data/mysql.err'>/home/ryszard/.local/share/akonadi/db_data/mysql.err</a>&apos; contains errors.

File content of '/home/ryszard/.local/share/akonadi/db_data/mysql.err':
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
170928 15:31:52 [Note] InnoDB: innodb_empty_free_list_algorithm has been changed to legacy because of small buffer pool size. In order to use backoff, increase buffer pool at least up to 20MB.

170928 15:31:52 [Note] InnoDB: Using mutexes to ref count buffer pool pages
170928 15:31:52 [Note] InnoDB: The InnoDB memory heap is disabled
170928 15:31:52 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
170928 15:31:52 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
170928 15:31:52 [Note] InnoDB: Compressed tables use zlib 1.2.8
170928 15:31:52 [Note] InnoDB: Using Linux native AIO
170928 15:31:52 [Note] InnoDB: Using CPU crc32 instructions
170928 15:31:52 [Note] InnoDB: Initializing buffer pool, size = 80.0M
170928 15:31:52 [Note] InnoDB: Completed initialization of buffer pool
170928 15:31:52 [Note] InnoDB: Highest supported file format is Barracuda.
170928 15:31:52 [Note] InnoDB: The log sequence numbers 1069941039 and 1069941039 in ibdata files do not match the log sequence number 1069941260 in the ib_logfiles!
170928 15:31:52 [Note] InnoDB: Restoring possible half-written data pages from the doublewrite buffer...
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 2 log sequence number 1237027915
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 4 log sequence number 1229663946
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 0 log sequence number 1237583985
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 5 log sequence number 1237606149
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 6 log sequence number 1237492143
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 420 log sequence number 1237492143
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 618 log sequence number 1233793112
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 45 log sequence number 1237492446
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 392 log sequence number 1237492446
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 526 log sequence number 1233793928
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 46 log sequence number 1237493480
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 543 log sequence number 1237493480
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 541 log sequence number 1233794742
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 47 log sequence number 1237493783
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 394 log sequence number 1237493783
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 617 log sequence number 1233795540
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 48 log sequence number 1237494070
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 493 log sequence number 1237494070
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 560 log sequence number 1233796354
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 49 log sequence number 1237494373
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 496 log sequence number 1237494373
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 591 log sequence number 1233797205
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 50 log sequence number 1237494660
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 313 log sequence number 1233798024
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 448 log sequence number 1237494660
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 51 log sequence number 1237494963
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 574 log sequence number 1237494963
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 485 log sequence number 1233802482
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 52 log sequence number 1237495250
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 314 log sequence number 1233803314
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 395 log sequence number 1237495250
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 53 log sequence number 1237495553
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 315 log sequence number 1233804218
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 322 log sequence number 1237495553
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 54 log sequence number 1237498330
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 316 log sequence number 1233805032
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 327 log sequence number 1237498330
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 55 log sequence number 1237498633
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 317 log sequence number 1233805867
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 429 log sequence number 1237498633
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 56 log sequence number 1237498936
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 476 log sequence number 1237498936
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 484 log sequence number 1233806665
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 57 log sequence number 1237499223
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 498 log sequence number 1237499223
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 391 log sequence number 1233807479
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 58 log sequence number 1237500257
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 318 log sequence number 1233808287
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 544 log sequence number 1237500257
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 59 log sequence number 1237500560
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 319 log sequence number 1233809122
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 328 log sequence number 1237500560
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 60 log sequence number 1237500847
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 421 log sequence number 1237500847
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 531 log sequence number 1233809936
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 61 log sequence number 1237501150
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 321 log sequence number 1233810733
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 452 log sequence number 1237501150
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 62 log sequence number 1237501452
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 529 log sequence number 1237501452
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 355 log sequence number 1233811547
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 63 log sequence number 1237504166
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 408 log sequence number 1233812345
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 364 log sequence number 1237504166
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 192 log sequence number 1237506383
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 500 log sequence number 1237506383
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 596 log sequence number 1233813162
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 193 log sequence number 1237506690
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 324 log sequence number 1233813963
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 365 log sequence number 1237506690
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 194 log sequence number 1237507835
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 325 log sequence number 1233817134
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 545 log sequence number 1237507835
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 195 log sequence number 1237508142
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 326 log sequence number 1233817974
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 447 log sequence number 1237508142
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 196 log sequence number 1237508433
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 611 log sequence number 1237508433
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 590 log sequence number 1233818812
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 197 log sequence number 1237508740
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 613 log sequence number 1237508740
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 444 log sequence number 1233819613
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 198 log sequence number 1237515707
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 464 log sequence number 1233821201
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 398 log sequence number 1237515707
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 199 log sequence number 1237516014
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 329 log sequence number 1237516014
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 357 log sequence number 1233822002
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 200 log sequence number 1237516321
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 331 log sequence number 1233822819
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 368 log sequence number 1237516321
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 201 log sequence number 1237516612
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 463 log sequence number 1237516612
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 634 log sequence number 1233823641
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 202 log sequence number 1237516919
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 333 log sequence number 1233824458
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 330 log sequence number 1237516919
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 203 log sequence number 1237519160
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 334 log sequence number 1233827550
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 204 log sequence number 1237517535
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 335 log sequence number 1233830141
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 527 log sequence number 1237517535
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 205 log sequence number 1237517842
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 336 log sequence number 1233830976
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 522 log sequence number 1237517842
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 206 log sequence number 1237518133
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 523 log sequence number 1237518133
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 414 log sequence number 1233831798
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 207 log sequence number 1237518440
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 401 log sequence number 1237518440
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 433 log sequence number 1233833370
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 208 log sequence number 1237518741
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 524 log sequence number 1237518741
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 467 log sequence number 1233834187
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 209 log sequence number 1237519202
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 623 log sequence number 1237519202
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 437 log sequence number 1233835025
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 210 log sequence number 1237519508
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 341 log sequence number 1233838987
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 532 log sequence number 1237519508
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 211 log sequence number 1237519815
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 342 log sequence number 1233843278
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 338 log sequence number 1237519815
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 212 log sequence number 1237520122
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 372 log sequence number 1237520122
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 474 log sequence number 1233844365
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 213 log sequence number 1237532817
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 507 log sequence number 1233845431
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 442 log sequence number 1237532817
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 214 log sequence number 1237533108
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 501 log sequence number 1237533108
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 435 log sequence number 1233846536
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 215 log sequence number 1237533415
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 593 log sequence number 1233847623
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 373 log sequence number 1237533415
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 216 log sequence number 1237533722
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 465 log sequence number 1237533722
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 589 log sequence number 1233848689
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 217 log sequence number 1237534013
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 468 log sequence number 1237534013
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 416 log sequence number 1233849775
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 218 log sequence number 1237534320
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 347 log sequence number 1233850841
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 443 log sequence number 1237534320
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 219 log sequence number 1237534611
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 348 log sequence number 1233851923
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 375 log sequence number 1237534611
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 220 log sequence number 1237534918
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 340 log sequence number 1237534918
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 636 log sequence number 1233852989
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 221 log sequence number 1237535209
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 350 log sequence number 1233854076
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 502 log sequence number 1237535209
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 222 log sequence number 1237535516
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 351 log sequence number 1233855142
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 469 log sequence number 1237535516
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 223 log sequence number 1237535823
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 352 log sequence number 1233856090
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 402 log sequence number 1237535823
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 224 log sequence number 1237538076
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 404 log sequence number 1237538076
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 575 log sequence number 1233857040
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 225 log sequence number 1237538383
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 503 log sequence number 1237538383
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 598 log sequence number 1233861683
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 226 log sequence number 1237538674
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 345 log sequence number 1237538674
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 487 log sequence number 1233862523
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 227 log sequence number 1237538981
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 422 log sequence number 1237538981
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 520 log sequence number 1233863340
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 228 log sequence number 1237539272
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 405 log sequence number 1237539272
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 320 log sequence number 1233864162
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 229 log sequence number 1237539579
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 616 log sequence number 1233865000
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 628 log sequence number 1237539579
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 230 log sequence number 1237539886
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 477 log sequence number 1233865817
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 470 log sequence number 1237539886
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 231 log sequence number 1237540177
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 423 log sequence number 1237540177
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 601 log sequence number 1233866639
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 232 log sequence number 1237540484
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 377 log sequence number 1237540484
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 466 log sequence number 1233867455
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 233 log sequence number 1237540775
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 424 log sequence number 1237540775
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 610 log sequence number 1233868277
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 234 log sequence number 1237544703
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 349 log sequence number 1237544703
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 358 log sequence number 1233869115
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 235 log sequence number 1237545010
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 406 log sequence number 1237545010
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 519 log sequence number 1233869932
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 236 log sequence number 1237545301
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 415 log sequence number 1233873293
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 473 log sequence number 1237545301
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 237 log sequence number 1237545608
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 366 log sequence number 1233874138
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 378 log sequence number 1237545608
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 238 log sequence number 1237545899
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 430 log sequence number 1233874939
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 475 log sequence number 1237545899
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 239 log sequence number 1237546206
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 379 log sequence number 1237546206
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 309 log sequence number 1233875756
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 240 log sequence number 1237546513
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 380 log sequence number 1237546513
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 530 log sequence number 1233876594
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 241 log sequence number 1237546804
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 511 log sequence number 1233877416
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 410 log sequence number 1237546804
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 242 log sequence number 1237547111
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 505 log sequence number 1237547111
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 535 log sequence number 1233878233
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 244 log sequence number 1237583857
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 397 log sequence number 1233879071
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 245 log sequence number 1237455647
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 353 log sequence number 1237455647
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 370 log sequence number 1233879872
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 246 log sequence number 1237551981
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 382 log sequence number 1237551981
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 344 log sequence number 1233880710
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 247 log sequence number 1237553910
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 412 log sequence number 1237553910
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 413 log sequence number 1233884997
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 248 log sequence number 1237554424
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 440 log sequence number 1233885832
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 432 log sequence number 1237554424
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 249 log sequence number 1237556002
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 506 log sequence number 1237556002
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 603 log sequence number 1233886651
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 250 log sequence number 1237556516
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 441 log sequence number 1233887468
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 508 log sequence number 1237556516
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 251 log sequence number 1237569008
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 478 log sequence number 1237569008
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 533 log sequence number 1233888285
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 252 log sequence number 1237569517
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 509 log sequence number 1237569517
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 399 log sequence number 1233889086
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 253 log sequence number 1237570357
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 510 log sequence number 1237570357
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 614 log sequence number 1233889903
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 254 log sequence number 1237486247
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 367 log sequence number 1233890704
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 255 log sequence number 1237460718
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 525 log sequence number 1237460718
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 592 log sequence number 1233891521
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 256 log sequence number 1237583745
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 417 log sequence number 1237583745
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 396 log sequence number 1237583745
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 257 log sequence number 1237571374
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 537 log sequence number 1237571374
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 606 log sequence number 1233747533
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 258 log sequence number 1237583985
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 580 log sequence number 1233748355
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 259 log sequence number 1237584202
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 450 log sequence number 1237584202
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 584 log sequence number 1233749193
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 260 log sequence number 1237584435
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 479 log sequence number 1237584435
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 337 log sequence number 1233751821
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 261 log sequence number 1237584652
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 451 log sequence number 1237584652
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 462 log sequence number 1233752677
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 262 log sequence number 1237585240
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 512 log sequence number 1237585240
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 445 log sequence number 1233753478
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 263 log sequence number 1237463860
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 594 log sequence number 1237463860
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 622 log sequence number 1233754316
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 264 log sequence number 1237585804
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 446 log sequence number 1237585804
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 632 log sequence number 1233755164
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 265 log sequence number 1237586049
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 376 log sequence number 1233755967
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 434 log sequence number 1237586049
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 266 log sequence number 1237587377
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 425 log sequence number 1237587377
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 374 log sequence number 1233756805
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 267 log sequence number 1237598533
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 609 log sequence number 1237598533
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 360 log sequence number 1237598533
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 268 log sequence number 1237598778
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 513 log sequence number 1237598778
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 393 log sequence number 1233758577
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 269 log sequence number 1237599012
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 542 log sequence number 1237599012
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 472 log sequence number 1233759394
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 270 log sequence number 1237599257
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 638 log sequence number 1237599257
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 536 log sequence number 1233760216
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 271 log sequence number 1237599474
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 418 log sequence number 1237599474
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 597 log sequence number 1233761054
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 272 log sequence number 1237600114
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 438 log sequence number 1237600114
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 528 log sequence number 1233761871
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 273 log sequence number 1237467600
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 454 log sequence number 1237467600
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 599 log sequence number 1233762672
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 274 log sequence number 1237600724
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 381 log sequence number 1233763489
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 384 log sequence number 1237600724
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 275 log sequence number 1237600969
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 427 log sequence number 1237600969
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 471 log sequence number 1233764311
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 276 log sequence number 1237601351
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 385 log sequence number 1237601351
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 411 log sequence number 1233765149
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 277 log sequence number 1237605469
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 480 log sequence number 1237605469
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 407 log sequence number 1233765966
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 278 log sequence number 1237605776
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 386 log sequence number 1237605776
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 403 log sequence number 1233766788
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 279 log sequence number 1237606099
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 455 log sequence number 1237606099
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 538 log sequence number 1233767605
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 280 log sequence number 1237473562
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 457 log sequence number 1237473562
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 460 log sequence number 1233768406
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 281 log sequence number 1237473869
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 387 log sequence number 1237473869
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 619 log sequence number 1233769244
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 282 log sequence number 1237474160
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 514 log sequence number 1238319022
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 572 log sequence number 1236531766
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 332 log sequence number 1233770061
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 283 log sequence number 1237474467
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 301 log sequence number 1237474467
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 371 log sequence number 1233770862
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 284 log sequence number 1237474758
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 439 log sequence number 1237474758
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 431 log sequence number 1233771679
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 285 log sequence number 1237475065
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 483 log sequence number 1237475065
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 588 log sequence number 1233772480
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 286 log sequence number 1237475372
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 486 log sequence number 1237475372
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 626 log sequence number 1233773297
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 287 log sequence number 1237475663
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 306 log sequence number 1237475663
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 539 log sequence number 1233774135
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 288 log sequence number 1237475970
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 419 log sequence number 1237475970
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 540 log sequence number 1233774936
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 289 log sequence number 1237484637
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 488 log sequence number 1237484637
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 400 log sequence number 1233775774
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 290 log sequence number 1237484927
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 515 log sequence number 1237484927
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 553 log sequence number 1233776575
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 291 log sequence number 1237485233
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 491 log sequence number 1237485233
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 534 log sequence number 1233781102
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 292 log sequence number 1237485523
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 517 log sequence number 1237485523
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 426 log sequence number 1233781958
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 293 log sequence number 1237486579
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 428 log sequence number 1237486579
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 504 log sequence number 1233782796
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 294 log sequence number 1237486637
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 569 log sequence number 1237486637
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 612 log sequence number 1233783618
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 295 log sequence number 1237486679
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 458 log sequence number 1237486679
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 608 log sequence number 1233784435
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 296 log sequence number 1237490648
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 363 log sequence number 1237490648
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 456 log sequence number 1233785235
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 297 log sequence number 1237490954
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 518 log sequence number 1237490954
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 490 log sequence number 1233786073
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 298 log sequence number 1237491260
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 311 log sequence number 1237491260
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 453 log sequence number 1233786874
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 299 log sequence number 1237491550
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 388 log sequence number 1237491550
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 390 log sequence number 1233787712
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 300 log sequence number 1237491856
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 389 log sequence number 1237491856
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
2017-09-28 15:31:52 7f3352ed8780 InnoDB: Error: page 436 log sequence number 1233788529
InnoDB: is in the future! Current system log sequence number 1069941260.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but 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: 1 transaction(s) which must be rolled back or cleaned up
InnoDB: in total 0 row operations to undo
InnoDB: Trx id counter is 4076288
InnoDB: Cleaning up trx with id 4075830
2017-09-28 15:31:52 7f3352ed8780  InnoDB: Assertion failure in thread 139858411358080 in file trx0trx.cc line 462
InnoDB: Failing assertion: trx->update_undo == NULL
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
170928 15:31:52 [ERROR] 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.

To report this bug, see https://mariadb.com/kb/en/reporting-bugs

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.

Server version: 10.0.32-MariaDB
key_buffer_size=16384
read_buffer_size=131072
max_used_connections=0
max_threads=258
thread_count=0
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 566521 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 = 0x0 thread_stack 0x48000
/usr/sbin/mysqld(my_print_stacktrace+0x3c)[0xb83e4c]
/usr/sbin/mysqld(handle_fatal_signal+0x2d5)[0x724f65]
/lib64/libpthread.so.0(+0x10180)[0x7f3351dac180]
/lib64/libc.so.6(gsignal+0x37)[0x7f3350aef547]
/lib64/libc.so.6(abort+0x16a)[0x7f3350af0cda]
/usr/sbin/mysqld[0x9b1167]
/usr/sbin/mysqld[0x9a997f]
/usr/sbin/mysqld[0x920a84]
/usr/sbin/mysqld[0x997be5]
/usr/sbin/mysqld[0x8da364]
/usr/sbin/mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x75)[0x727bc5]
/usr/sbin/mysqld[0x5cb1d3]
/usr/sbin/mysqld(_Z11plugin_initPiPPci+0x590)[0x5cbe20]
/usr/sbin/mysqld[0x52fd43]
/usr/sbin/mysqld(_Z11mysqld_mainiPPc+0x596)[0x5349d6]
/lib64/libc.so.6(__libc_start_main+0xf0)[0x7f3350adc050]
/usr/sbin/mysqld[0x528af5]
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.


Test 6:  SUCCESS
--------

MySQL server default configuration found.
Details: The default configuration for the MySQL server was found and is readable at <a href='/etc/akonadi/mysql-global.conf'>/etc/akonadi/mysql-global.conf</a>.

File content of '/etc/akonadi/mysql-global.conf':
#
# Global Akonadi MySQL server settings,
# These settings can be adjusted using $HOME/.config/akonadi/mysql-local.conf
#
# Based on advice by Kris Köhntopp <kris@mysql.com>
#
[mysqld]

# strict query parsing/interpretation
# TODO: make Akonadi work with those settings enabled
# sql_mode=strict_trans_tables,strict_all_tables,strict_error_for_division_by_zero,no_auto_create_user,no_auto_value_on_zero,no_engine_substitution,no_zero_date,no_zero_in_date,only_full_group_by,pipes_as_concat
# sql_mode=strict_trans_tables

# DEBUGGING:
# log all queries, useful for debugging but generates an enormous amount of data
# log=mysql.full
# log queries slower than n seconds, log file name relative to datadir (for debugging only)
# log_slow_queries=mysql.slow
# long_query_time=1
# log queries not using indices, debug only, disable for production use
# log_queries_not_using_indexes=1
#
# mesure database size and adjust innodb_buffer_pool_size
# SELECT sum(data_length) as bla, sum(index_length) as blub FROM information_schema.tables WHERE table_schema not in ("mysql", "information_schema");

# NOTES:
# Keep Innob_log_waits and keep Innodb_buffer_pool_wait_free small (see show global status like "inno%", show global variables)

#expire_logs_days=3

#sync_bin_log=0

# Use UTF-8 encoding for tables
character_set_server=utf8
collation_server=utf8_general_ci

# use InnoDB for transactions and better crash recovery
default_storage_engine=innodb

# memory pool InnoDB uses to store data dictionary information and other internal data structures (default:1M)
# Deprecated in MySQL >= 5.6.3
innodb_additional_mem_pool_size=1M

# memory buffer InnoDB uses to cache data and indexes of its tables (default:128M)
# Larger values means less I/O
innodb_buffer_pool_size=80M

# Create a .ibd file for each table (default:0)
innodb_file_per_table=1

# Write out the log buffer to the log file at each commit (default:1)
innodb_flush_log_at_trx_commit=2

# Buffer size used to write to the log files on disk (default:1M for builtin, 8M for plugin)
# larger values means less I/O
innodb_log_buffer_size=1M

# Size of each log file in a log group (default:5M) larger means less I/O but more time for recovery.
innodb_log_file_size=64M

# # error log file name, relative to datadir (default:hostname.err)
log_error=mysql.err

# print warnings and connection errors (default:1)
log_warnings=2

# Convert table named to lowercase
lower_case_table_names=1

# Maximum size of one packet or any generated/intermediate string. (default:1M)
max_allowed_packet=32M

# Maximum simultaneous connections allowed (default:100)
max_connections=256

# The two options below make no sense with prepared statements and/or transactions
# (make sense when having the same query multiple times)

# Memory allocated for caching query results (default:0 (disabled))
query_cache_size=0

# Do not cache results (default:1)
query_cache_type=0

# Do not use the privileges mechanisms
skip_grant_tables

# Do not listen for TCP/IP connections at all
skip_networking

# The number of open tables for all threads. (default:64)
table_open_cache=200

# How many threads the server should cache for reuse (default:0)
thread_cache_size=3

# wait 365d before dropping the DB connection (default:8h)
wait_timeout=31536000

# We use InnoDB, so don't let MyISAM eat up memory
key_buffer_size=16K

# KUBUNTU:
# Unset the export dir check as only the full mysql-server package creates it
secure_file_priv=

[client]
default-character-set=utf8


Test 7:  SKIP
--------

MySQL server custom configuration not available.
Details: The custom configuration for the MySQL server was not found but is optional.

Test 8:  SUCCESS
--------

MySQL server configuration is usable.
Details: The MySQL server configuration was found at <a href='/home/ryszard/.local/share/akonadi/mysql.conf'>/home/ryszard/.local/share/akonadi/mysql.conf</a> and is readable.

File content of '/home/ryszard/.local/share/akonadi/mysql.conf':
#
# Global Akonadi MySQL server settings,
# These settings can be adjusted using $HOME/.config/akonadi/mysql-local.conf
#
# Based on advice by Kris Köhntopp <kris@mysql.com>
#
[mysqld]

# strict query parsing/interpretation
# TODO: make Akonadi work with those settings enabled
# sql_mode=strict_trans_tables,strict_all_tables,strict_error_for_division_by_zero,no_auto_create_user,no_auto_value_on_zero,no_engine_substitution,no_zero_date,no_zero_in_date,only_full_group_by,pipes_as_concat
# sql_mode=strict_trans_tables

# DEBUGGING:
# log all queries, useful for debugging but generates an enormous amount of data
# log=mysql.full
# log queries slower than n seconds, log file name relative to datadir (for debugging only)
# log_slow_queries=mysql.slow
# long_query_time=1
# log queries not using indices, debug only, disable for production use
# log_queries_not_using_indexes=1
#
# mesure database size and adjust innodb_buffer_pool_size
# SELECT sum(data_length) as bla, sum(index_length) as blub FROM information_schema.tables WHERE table_schema not in ("mysql", "information_schema");

# NOTES:
# Keep Innob_log_waits and keep Innodb_buffer_pool_wait_free small (see show global status like "inno%", show global variables)

#expire_logs_days=3

#sync_bin_log=0

# Use UTF-8 encoding for tables
character_set_server=utf8
collation_server=utf8_general_ci

# use InnoDB for transactions and better crash recovery
default_storage_engine=innodb

# memory pool InnoDB uses to store data dictionary information and other internal data structures (default:1M)
# Deprecated in MySQL >= 5.6.3
innodb_additional_mem_pool_size=1M

# memory buffer InnoDB uses to cache data and indexes of its tables (default:128M)
# Larger values means less I/O
innodb_buffer_pool_size=80M

# Create a .ibd file for each table (default:0)
innodb_file_per_table=1

# Write out the log buffer to the log file at each commit (default:1)
innodb_flush_log_at_trx_commit=2

# Buffer size used to write to the log files on disk (default:1M for builtin, 8M for plugin)
# larger values means less I/O
innodb_log_buffer_size=1M

# Size of each log file in a log group (default:5M) larger means less I/O but more time for recovery.
innodb_log_file_size=64M

# # error log file name, relative to datadir (default:hostname.err)
log_error=mysql.err

# print warnings and connection errors (default:1)
log_warnings=2

# Convert table named to lowercase
lower_case_table_names=1

# Maximum size of one packet or any generated/intermediate string. (default:1M)
max_allowed_packet=32M

# Maximum simultaneous connections allowed (default:100)
max_connections=256

# The two options below make no sense with prepared statements and/or transactions
# (make sense when having the same query multiple times)

# Memory allocated for caching query results (default:0 (disabled))
query_cache_size=0

# Do not cache results (default:1)
query_cache_type=0

# Do not use the privileges mechanisms
skip_grant_tables

# Do not listen for TCP/IP connections at all
skip_networking

# The number of open tables for all threads. (default:64)
table_open_cache=200

# How many threads the server should cache for reuse (default:0)
thread_cache_size=3

# wait 365d before dropping the DB connection (default:8h)
wait_timeout=31536000

# We use InnoDB, so don't let MyISAM eat up memory
key_buffer_size=16K

# KUBUNTU:
# Unset the export dir check as only the full mysql-server package creates it
secure_file_priv=

[client]
default-character-set=utf8


Test 9:  SUCCESS
--------

akonadictl found and usable
Details: The program '/usr/bin/akonadictl' to control the Akonadi server was found and could be executed successfully.
Result:
Akonadi 1.13.0


Test 10:  ERROR
--------

Akonadi control process not registered at D-Bus.
Details: The Akonadi control process is not registered at D-Bus which typically means it was not started or encountered a fatal error during startup.

Test 11:  ERROR
--------

Akonadi server process not registered at D-Bus.
Details: The Akonadi server process is not registered at D-Bus which typically means it was not started or encountered a fatal error during startup.

Test 12:  SKIP
--------

Protocol version check not possible.
Details: Without a connection to the server it is not possible to check if the protocol version meets the requirements.

Test 13:  ERROR
--------

No resource agents found.
Details: No resource agents have been found, Akonadi is not usable without at least one. This usually means that no resource agents are installed or that there is a setup problem. The following paths have been searched: '/usr/share/akonadi/agents'. The XDG_DATA_DIRS environment variable is set to '/usr/share:/usr/share:/usr/local/share'; make sure this includes all paths where Akonadi agents are installed.

Directory listing of '/usr/share/akonadi/agents':
akonadibalooindexingagent.desktop
akonadinepomukfeederagent.desktop
akonotesresource.desktop
archivemailagent.desktop
birthdaysresource.desktop
contactsresource.desktop
davgroupwareresource.desktop
facebookresource.desktop
folderarchiveagent.desktop
followupreminder.desktop
googlecalendarresource.desktop
googlecontactsresource.desktop
icaldirresource.desktop
icalresource.desktop
imapresource.desktop
invitationsagent.desktop
kabcresource.desktop
kalarmdirresource.desktop
kalarmresource.desktop
kcalresource.desktop
kdeaccountsresource.desktop
knutresource.desktop
kolabproxyresource.desktop
kolabresource.desktop
localbookmarksresource.desktop
maildirresource.desktop
maildispatcheragent.desktop
mailfilteragent.desktop
mboxresource.desktop
migrationagent.desktop
mixedmaildirresource.desktop
mtdummyresource.desktop
newmailnotifieragent.desktop
nntpresource.desktop
notesagent.desktop
notesresource.desktop
openxchangeresource.desktop
pop3resource.desktop
sendlateragent.desktop
skroogeakonadiresource.desktop
vcarddirresource.desktop
vcardresource.desktop

Environment variable XDG_DATA_DIRS is set to '/usr/share:/usr/share:/usr/local/share'

Test 14:  ERROR
--------

Current Akonadi server error log found.
Details: The Akonadi server reported errors during its current startup. The log can be found in <a href='/home/ryszard/.local/share/akonadi/akonadiserver.error'>/home/ryszard/.local/share/akonadi/akonadiserver.error</a>.

File content of '/home/ryszard/.local/share/akonadi/akonadiserver.error':
Database process exited unexpectedly during initial connection! 
executable: "/usr/sbin/mysqld" 
arguments: ("--defaults-file=/home/ryszard/.local/share/akonadi/mysql.conf", "--datadir=/home/ryszard/.local/share/akonadi/db_data/", "--socket=/tmp/akonadi-ryszard.VevqAR/mysql.socket") 
stdout: "" 
stderr: "170928 15:31:52 [Note] /usr/sbin/mysqld (mysqld 10.0.32-MariaDB) starting as process 22849 ...
" 
exit code: 1 
process error: "Unknown error" 
"[
0: akonadiserver(_Z11akBacktracev+0x39) [0x465949]
1: akonadiserver() [0x465bd9]
2: /lib64/libc.so.6(+0x335d0) [0x7f45ee5775d0]
3: /lib64/libc.so.6(gsignal+0x37) [0x7f45ee577547]
4: /lib64/libc.so.6(abort+0x16a) [0x7f45ee578cda]
5: /lib64/libQtCore.so.4(_Z17qt_message_output9QtMsgTypePKc+0x64) [0x7f45efd9cae4]
6: akonadiserver(_ZN15FileDebugStream9writeDataEPKcx+0xa0) [0x467e10]
7: /lib64/libQtCore.so.4(_ZN9QIODevice5writeEPKcx+0x8a) [0x7f45efe3727a]
8: /lib64/libQtCore.so.4(+0x11a25c) [0x7f45efe4625c]
9: /lib64/libQtCore.so.4(_ZN11QTextStreamD1Ev+0x31) [0x7f45efe4e5a1]
10: akonadiserver(_ZN6QDebugD1Ev+0x39) [0x45fc09]
11: akonadiserver(_ZN7Akonadi6Server13DbConfigMysql19startInternalServerEv+0x1da9) [0x4d7f49]
12: akonadiserver(_ZN7Akonadi6Server13AkonadiServer20startDatabaseProcessEv+0xe0) [0x468b60]
13: akonadiserver(_ZN7Akonadi6Server13AkonadiServer4initEv+0xbd) [0x46cead]
14: akonadiserver() [0x5414c9]
15: /lib64/libQtCore.so.4(_ZN7QObject5eventEP6QEvent+0x1c1) [0x7f45efebfd61]
16: /lib64/libQtCore.so.4(_ZN16QCoreApplication14notifyInternalEP7QObjectP6QEvent+0x6d) [0x7f45efea7cad]
17: /lib64/libQtCore.so.4(_ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData+0x201) [0x7f45efeaabe1]
18: /lib64/libQtCore.so.4(+0x1a8cae) [0x7f45efed4cae]
19: /lib64/libglib-2.0.so.0(g_main_context_dispatch+0x22d) [0x7f45edc34c6d]
20: /lib64/libglib-2.0.so.0(+0x48f18) [0x7f45edc34f18]
21: /lib64/libglib-2.0.so.0(g_main_context_iteration+0x2c) [0x7f45edc34fbc]
22: /lib64/libQtCore.so.4(_ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE+0x7e) [0x7f45efed4e1e]
23: /lib64/libQtCore.so.4(_ZN10QEventLoop13processEventsE6QFlagsINS_17ProcessEventsFlagEE+0x31) [0x7f45efea6931]
24: /lib64/libQtCore.so.4(_ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE+0x185) [0x7f45efea6c45]
25: /lib64/libQtCore.so.4(_ZN16QCoreApplication4execEv+0x89) [0x7f45efeabe59]
26: akonadiserver(main+0x1e6) [0x45edd6]
27: /lib64/libc.so.6(__libc_start_main+0xf0) [0x7f45ee564050]
28: akonadiserver() [0x45f83e]
]
" 


Test 15:  ERROR
--------

Previous Akonadi server error log found.
Details: The Akonadi server reported errors during its previous startup. The log can be found in <a href='/home/ryszard/.local/share/akonadi/akonadiserver.error.old'>/home/ryszard/.local/share/akonadi/akonadiserver.error.old</a>.

File content of '/home/ryszard/.local/share/akonadi/akonadiserver.error.old':
Database process exited unexpectedly during initial connection! 
executable: "/usr/sbin/mysqld" 
arguments: ("--defaults-file=/home/ryszard/.local/share/akonadi/mysql.conf", "--datadir=/home/ryszard/.local/share/akonadi/db_data/", "--socket=/tmp/akonadi-ryszard.VevqAR/mysql.socket") 
stdout: "" 
stderr: "170928 15:31:51 [Note] /usr/sbin/mysqld (mysqld 10.0.32-MariaDB) starting as process 22833 ...
" 
exit code: 1 
process error: "Unknown error" 
"[
0: akonadiserver(_Z11akBacktracev+0x39) [0x465949]
1: akonadiserver() [0x465bd9]
2: /lib64/libc.so.6(+0x335d0) [0x7ff2a87d75d0]
3: /lib64/libc.so.6(gsignal+0x37) [0x7ff2a87d7547]
4: /lib64/libc.so.6(abort+0x16a) [0x7ff2a87d8cda]
5: /lib64/libQtCore.so.4(_Z17qt_message_output9QtMsgTypePKc+0x64) [0x7ff2a9ffcae4]
6: akonadiserver(_ZN15FileDebugStream9writeDataEPKcx+0xa0) [0x467e10]
7: /lib64/libQtCore.so.4(_ZN9QIODevice5writeEPKcx+0x8a) [0x7ff2aa09727a]
8: /lib64/libQtCore.so.4(+0x11a25c) [0x7ff2aa0a625c]
9: /lib64/libQtCore.so.4(_ZN11QTextStreamD1Ev+0x31) [0x7ff2aa0ae5a1]
10: akonadiserver(_ZN6QDebugD1Ev+0x39) [0x45fc09]
11: akonadiserver(_ZN7Akonadi6Server13DbConfigMysql19startInternalServerEv+0x1da9) [0x4d7f49]
12: akonadiserver(_ZN7Akonadi6Server13AkonadiServer20startDatabaseProcessEv+0xe0) [0x468b60]
13: akonadiserver(_ZN7Akonadi6Server13AkonadiServer4initEv+0xbd) [0x46cead]
14: akonadiserver() [0x5414c9]
15: /lib64/libQtCore.so.4(_ZN7QObject5eventEP6QEvent+0x1c1) [0x7ff2aa11fd61]
16: /lib64/libQtCore.so.4(_ZN16QCoreApplication14notifyInternalEP7QObjectP6QEvent+0x6d) [0x7ff2aa107cad]
17: /lib64/libQtCore.so.4(_ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData+0x201) [0x7ff2aa10abe1]
18: /lib64/libQtCore.so.4(+0x1a8cae) [0x7ff2aa134cae]
19: /lib64/libglib-2.0.so.0(g_main_context_dispatch+0x22d) [0x7ff2a7e94c6d]
20: /lib64/libglib-2.0.so.0(+0x48f18) [0x7ff2a7e94f18]
21: /lib64/libglib-2.0.so.0(g_main_context_iteration+0x2c) [0x7ff2a7e94fbc]
22: /lib64/libQtCore.so.4(_ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE+0x7e) [0x7ff2aa134e1e]
23: /lib64/libQtCore.so.4(_ZN10QEventLoop13processEventsE6QFlagsINS_17ProcessEventsFlagEE+0x31) [0x7ff2aa106931]
24: /lib64/libQtCore.so.4(_ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE+0x185) [0x7ff2aa106c45]
25: /lib64/libQtCore.so.4(_ZN16QCoreApplication4execEv+0x89) [0x7ff2aa10be59]
26: akonadiserver(main+0x1e6) [0x45edd6]
27: /lib64/libc.so.6(__libc_start_main+0xf0) [0x7ff2a87c4050]
28: akonadiserver() [0x45f83e]
]
" 


Test 16:  SUCCESS
--------

No current Akonadi control error log found.
Details: The Akonadi control process did not report any errors during its current startup.

Test 17:  SUCCESS
--------

No previous Akonadi control error log found.
Details: The Akonadi control process did not report any errors during its previous startup.