[Draft] 10.1.10 : InnoDB: Failing assertion: addr.page == FIL_NULL || addr.boffset >= FIL_PAGE_DATA

2017-08-31 05:06:27 7f4c9012c7c0  InnoDB: Assertion failure in thread 139966811391936 in file fut0lst.ic line 83

InnoDB: Failing assertion: addr.page == FIL_NULL || addr.boffset >= FIL_PAGE_DATA

InnoDB: We intentionally generate a memory trap.

InnoDB: Submit a detailed bug report to http://bugs.mysql.com.

InnoDB: If you get repeated assertion failures or crashes, even

InnoDB: immediately after the mysqld startup, there may be

InnoDB: corruption in the InnoDB tablespace. Please refer to

InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html

InnoDB: about forcing recovery.

170831  5:06:27 [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 http://kb.askmonty.org/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.1.10-MariaDB-log

key_buffer_size=134217728

read_buffer_size=131072

max_used_connections=0

max_threads=153

thread_count=0

It is possible that mysqld could use up to 

key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 467105 K  bytes of memory

Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0x0

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

mysys/stacktrace.c:247(my_print_stacktrace)[0x564a9807542b]

sql/signal_handler.cc:160(handle_fatal_signal)[0x564a97bd6b05]

/lib/x86_64-linux-gnu/libpthread.so.0(+0x10330)[0x7f4c8f29a330]

/lib/x86_64-linux-gnu/libc.so.6(gsignal+0x37)[0x7f4c8e8edc37]

/lib/x86_64-linux-gnu/libc.so.6(abort+0x148)[0x7f4c8e8f1028]

include/mem0mem.ic:559(trx_undo_mem_create_at_db_start)[0x564a97e3d056]

trx/trx0rseg.cc:212(trx_rseg_mem_create)[0x564a97e2f6e3]

trx/trx0rseg.cc:289(trx_rseg_create_instance)[0x564a97e303b5]

trx/trx0sys.cc:660(trx_sys_init_at_db_start())[0x564a97e31986]

srv/srv0start.cc:2566(innobase_start_or_create_for_mysql())[0x564a97e17e8b]

handler/ha_innodb.cc:4157(innobase_init)[0x564a97d3d84d]

sql/handler.cc:513(ha_initialize_handlerton(st_plugin_int*))[0x564a97bd9068]

sql/sql_plugin.cc:1408(plugin_initialize)[0x564a97a7a0a5]

sql/sql_plugin.cc:1685(plugin_init(int*, char**, int))[0x564a97a7b052]

sql/mysqld.cc:5201(init_server_components)[0x564a979dbee2]

sql/mysqld.cc:5821(mysqld_main(int, char**))[0x564a979de90b]

/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5)[0x7f4c8e8d8f45]

/home/travis/build/elenst/mariadb-tests/old/bin/mysqld(+0x3b7f9d)[0x564a979d2f9d]

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.

Writing a core file

Aborted (core dumped)

BROKEN: block: 32281 checkpoint: 10 05106c5e c43ad2d4

BROKEN: block: 32281 checkpoint: 10 05106c5e c43ad2d4

InnoDB: Log block no 32281 at lsn 16527360 has

InnoDB: ok header, but checksum field contains 3292189396, should be 84962398

2017-08-31  5:06:27 139966811391936 [ERROR] InnoDB: We scanned the log up to 16527360. A checkpoint was at 16527379 and the maximum LSN on a database page was 0. It is possible that the database is now corrupt!

2017-08-31 05:06:27 7f4c9012c7c0 InnoDB: Error: page 5 log sequence number 22754386

InnoDB: is in the future! Current system log sequence number 16527379.

InnoDB: Your database may be corrupt or you may have copied the InnoDB

InnoDB: tablespace but not the InnoDB log files. See

InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html

InnoDB: for more information.

2017-08-31 05:06:27 7f4c9012c7c0 InnoDB: Error: page 6 log sequence number 21943099

InnoDB: is in the future! Current system log sequence number 16527379.

InnoDB: Your database may be corrupt or you may have copied the InnoDB

InnoDB: tablespace but not the InnoDB log files. See

InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html

InnoDB: for more information.

2017-08-31 05:06:27 7f4c9012c7c0 InnoDB: Error: page 301 log sequence number 28609071

InnoDB: is in the future! Current system log sequence number 16527379.

InnoDB: Your database may be corrupt or you may have copied the InnoDB

InnoDB: tablespace but not the InnoDB log files. See

InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html

InnoDB: for more information.

2017-08-31 05:06:27 7f4c9012c7c0 InnoDB: Error: page 408 log sequence number 21943099

InnoDB: is in the future! Current system log sequence number 16527379.

InnoDB: Your database may be corrupt or you may have copied the InnoDB

InnoDB: tablespace but not the InnoDB log files. See

InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html

InnoDB: for more information.

2017-08-31 05:06:27 7f4c9012c7c0 InnoDB: Error: page 45 log sequence number 28076008

InnoDB: is in the future! Current system log sequence number 16527379.

InnoDB: Your database may be corrupt or you may have copied the InnoDB

InnoDB: tablespace but not the InnoDB log files. See

InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html

InnoDB: for more information.

2017-08-31 05:06:27 7f4c9012c7c0 InnoDB: Error: page 410 log sequence number 22390699

InnoDB: is in the future! Current system log sequence number 16527379.

InnoDB: Your database may be corrupt or you may have copied the InnoDB

InnoDB: tablespace but not the InnoDB log files. See

InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html

InnoDB: for more information.

2017-08-31 05:06:27 7f4c9012c7c0 InnoDB: Error: page 552 log sequence number 23370532

InnoDB: is in the future! Current system log sequence number 16527379.

InnoDB: Your database may be corrupt or you may have copied the InnoDB

InnoDB: tablespace but not the InnoDB log files. See

InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html

InnoDB: for more information.

2017-08-31 05:06:27 7f4c9012c7c0 InnoDB: Error: page 309 log sequence number 29211640

InnoDB: is in the future! Current system log sequence number 16527379.

InnoDB: Your database may be corrupt or you may have copied the InnoDB

InnoDB: tablespace but not the InnoDB log files. See

InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html

InnoDB: for more information.

2017-08-31 05:06:27 7f4c9012c7c0 InnoDB: Error: page 474 log sequence number 27011973

InnoDB: is in the future! Current system log sequence number 16527379.

InnoDB: Your database may be corrupt or you may have copied the InnoDB

InnoDB: tablespace but not the InnoDB log files. See

InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html

InnoDB: for more information.

2017-08-31 05:06:27 7f4c9012c7c0 InnoDB: Error: page 310 log sequence number 20727980

InnoDB: is in the future! Current system log sequence number 16527379.

InnoDB: Your database may be corrupt or you may have copied the InnoDB

InnoDB: tablespace but not the InnoDB log files. See

InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html

InnoDB: for more information.

2017-08-31 05:06:27 7f4c9012c7c0 InnoDB: Error: page 475 log sequence number 27275525

InnoDB: is in the future! Current system log sequence number 16527379.

InnoDB: Your database may be corrupt or you may have copied the InnoDB

InnoDB: tablespace but not the InnoDB log files. See

InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html

InnoDB: for more information.

2017-08-31 05:06:27 7f4c9012c7c0 InnoDB: Error: page 617 log sequence number 22748331

InnoDB: is in the future! Current system log sequence number 16527379.

InnoDB: Your database may be corrupt or you may have copied the InnoDB

InnoDB: tablespace but not the InnoDB log files. See

InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html

InnoDB: for more information.

2017-08-31 05:06:27 7f4c9012c7c0 InnoDB: Error: page 311 log sequence number 29211914

InnoDB: is in the future! Current system log sequence number 16527379.

InnoDB: Your database may be corrupt or you may have copied the InnoDB

InnoDB: tablespace but not the InnoDB log files. See

InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html

InnoDB: for more information.

2017-08-31 05:06:27 7f4c9012c7c0 InnoDB: Error: page 582 log sequence number 28703498

InnoDB: is in the future! Current system log sequence number 16527379.

InnoDB: Your database may be corrupt or you may have copied the InnoDB

InnoDB: tablespace but not the InnoDB log files. See

InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html

InnoDB: for more information.

2017-08-31 05:06:27 7f4c9012c7c0 InnoDB: Error: page 312 log sequence number 29188686

InnoDB: is in the future! Current system log sequence number 16527379.

InnoDB: Your database may be corrupt or you may have copied the InnoDB

InnoDB: tablespace but not the InnoDB log files. See

InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html

InnoDB: for more information.

2017-08-31 05:06:27 7f4c9012c7c0 InnoDB: Error: page 623 log sequence number 26119943

InnoDB: is in the future! Current system log sequence number 16527379.

InnoDB: Your database may be corrupt or you may have copied the InnoDB

InnoDB: tablespace but not the InnoDB log files. See

InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html

InnoDB: for more information.

2017-08-31 05:06:27 7f4c9012c7c0 InnoDB: Error: page 624 log sequence number 24769756

InnoDB: is in the future! Current system log sequence number 16527379.

InnoDB: Your database may be corrupt or you may have copied the InnoDB

InnoDB: tablespace but not the InnoDB log files. See

InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html

InnoDB: for more information.

2017-08-31 05:06:27 7f4c9012c7c0 InnoDB: Error: page 313 log sequence number 29230424

InnoDB: is in the future! Current system log sequence number 16527379.

InnoDB: Your database may be corrupt or you may have copied the InnoDB

InnoDB: tablespace but not the InnoDB log files. See

InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html

InnoDB: for more information.

2017-08-31 05:06:27 7f4c9012c7c0 InnoDB: Error: page 411 log sequence number 24256803

InnoDB: is in the future! Current system log sequence number 16527379.

InnoDB: Your database may be corrupt or you may have copied the InnoDB

InnoDB: tablespace but not the InnoDB log files. See

InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html

InnoDB: for more information.

2017-08-31 05:06:27 7f4c9012c7c0 InnoDB: Error: page 314 log sequence number 29212334

InnoDB: is in the future! Current system log sequence number 16527379.

InnoDB: Your database may be corrupt or you may have copied the InnoDB

InnoDB: tablespace but not the InnoDB log files. See

InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html

InnoDB: for more information.

2017-08-31 05:06:27 7f4c9012c7c0 InnoDB: Error: page 412 log sequence number 23935477

InnoDB: is in the future! Current system log sequence number 16527379.

InnoDB: Your database may be corrupt or you may have copied the InnoDB

InnoDB: tablespace but not the InnoDB log files. See

InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html

InnoDB: for more information.

2017-08-31 05:06:27 7f4c9012c7c0 InnoDB: Error: page 315 log sequence number 26220229

InnoDB: is in the future! Current system log sequence number 16527379.

InnoDB: Your database may be corrupt or you may have copied the InnoDB

InnoDB: tablespace but not the InnoDB log files. See

InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html

InnoDB: for more information.

2017-08-31 05:06:27 7f4c9012c7c0 InnoDB: Error: page 600 log sequence number 29681793

InnoDB: is in the future! Current system log sequence number 16527379.

InnoDB: Your database may be corrupt or you may have copied the InnoDB

InnoDB: tablespace but not the InnoDB log files. See

InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html

InnoDB: for more information.

2017-08-31 05:06:27 7f4c9012c7c0 InnoDB: Error: page 316 log sequence number 27796434

InnoDB: is in the future! Current system log sequence number 16527379.

InnoDB: Your database may be corrupt or you may have copied the InnoDB

InnoDB: tablespace but not the InnoDB log files. See

InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html

InnoDB: for more information.

2017-08-31 05:06:27 7f4c9012c7c0 InnoDB: Error: page 530 log sequence number 19294861

InnoDB: is in the future! Current system log sequence number 16527379.

InnoDB: Your database may be corrupt or you may have copied the InnoDB

InnoDB: tablespace but not the InnoDB log files. See

InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html

InnoDB: for more information.

2017-08-31 05:06:27 7f4c9012c7c0 InnoDB: Error: page 54 log sequence number 28035648

InnoDB: is in the future! Current system log sequence number 16527379.

InnoDB: Your database may be corrupt or you may have copied the InnoDB

InnoDB: tablespace but not the InnoDB log files. See

InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html

InnoDB: for more information.