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

Details

Type: Bug
Status: Closed (View Workflow)
Priority: Minor
Resolution: Cannot Reproduce
Affects Version/s: 10.1.10, 10.2.7
Fix Version/s: N/A
Component/s: Storage Engine - InnoDB
Labels:
None

Description

IMPORTANT NOTE: This was observed on 10.1.10, while the current latest release is 10.1.26. Unless it also happens on recent versions, there is nothing to be done here – many things have changed since 10.1.10, so the problem might be long gone. However, I want to have it filed, to make it searchable in case it's ever encountered again, in an old or a new version.

10.1.10 non-debug build
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)

Preceding errors in the log:

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.

Attachments

- Sort By Name
- Sort By Date
- Ascending
- Descending
- Thumbnails
- List
- Download All

error.log
4 kB
2020-02-09 16:46
error.log.3
31 kB
2020-02-12 18:09
data.7z
3.91 MB
2020-11-03 10:33
etc_mysql.tar.gz
4 kB
2020-11-07 15:49
error.log.1
785 kB
2020-11-07 15:49

Issue Links

relates to

MDEV-22341 Waiting for page_cleaner to finish flushing of buffer pool over 4 hours , InnoDB: Assertion failure in file innobase/include/fut0lst.ic line 85

Closed

Activity

Ascending order - Click to sort in descending order

Elena Stepanova created issue - 2017-08-31 10:13

Elena Stepanova made changes - 2017-08-31 10:17

Field	Original Value	New Value
Description	_IMPORTANT NOTE: This was observed on 10.1.10, while the current latest release is 10.1.26. Unless it also happens on recent versions, there is nothing to be done here -- many things have changed since 10.1.10, so the problem might be long gone. However, I want to have it filed, to make it searchable in case it's ever encountered again, in an old or a new version._ {noformat:title=10.1.0 non-debug build} 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) {noformat} Preceding errors in the log: {noformat} 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. {noformat}	_IMPORTANT NOTE: This was observed on 10.1.10, while the current latest release is 10.1.26. Unless it also happens on recent versions, there is nothing to be done here -- many things have changed since 10.1.10, so the problem might be long gone. However, I want to have it filed, to make it searchable in case it's ever encountered again, in an old or a new version._ {noformat:title=10.1.10 non-debug build} 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) {noformat} Preceding errors in the log: {noformat} 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. {noformat}

TAO ZHOU added a comment - 2017-10-23 23:34

I am running 10.2.7 and now getting this same error.

TAO ZHOU added a comment - 2017-10-23 23:34 I am running 10.2.7 and now getting this same error.

Elena Stepanova made changes - 2017-10-24 07:25

Affects Version/s

10.2 [ 14601 ]

Elena Stepanova made changes - 2017-10-24 07:25

Affects Version/s		10.2.7 [ 22543 ]
Affects Version/s	10.2 [ 14601 ]

Johnny Oskarsson added a comment - 2020-02-09 15:09

I just got this in 10.3.22 as well.

Also, how on earth is this a "Minor" bug? It crashes on startup for me, making MariaDB and all that depends on it (in my case: Nextcloud) completely unusable!

Any ideas on how to recover from this? I tried the InnoDB recovery modes without success.

Johnny Oskarsson added a comment - 2020-02-09 15:09 I just got this in 10.3.22 as well. Also, how on earth is this a "Minor" bug? It crashes on startup for me, making MariaDB and all that depends on it (in my case: Nextcloud) completely unusable! Any ideas on how to recover from this? I tried the InnoDB recovery modes without success.

Elena Stepanova added a comment - 2020-02-09 15:38

joskar, it was "Minor" on the reason explained at the very beginning of the description: it was only observed on very old versions and there was no indication it still existed. If you encountered it on 10.3.22, it will make a difference. Please attach the error log, stack traces from the coredump if you have it, and server config file(s). Thanks.

Elena Stepanova added a comment - 2020-02-09 15:38 joskar , it was "Minor" on the reason explained at the very beginning of the description: it was only observed on very old versions and there was no indication it still existed. If you encountered it on 10.3.22, it will make a difference. Please attach the error log, stack traces from the coredump if you have it, and server config file(s). Thanks.

Elena Stepanova made changes - 2020-02-09 15:39

Labels

need_feedback

Elena Stepanova added a comment - 2020-02-09 15:43 - edited

marko, do you have any advice on "how to recover from it" part?

Elena Stepanova added a comment - 2020-02-09 15:43 - edited marko , do you have any advice on "how to recover from it" part?

Johnny Oskarsson made changes - 2020-02-09 16:46

Attachment

error.log [ 50448 ]

Johnny Oskarsson added a comment - 2020-02-09 17:00 - edited

I managed to recover from it just now, I finally got mysqld --innodb-force-recovery=5 working. I did a mysqldump --all-tables >mysql.backup, killed mysqld, removed everything in /var/lib/mysql, ran mysql_install_db and started mysqld anew and then did a mysql -u root <mysql.backup. Now it seems to work again, but I don't know if this was the best way to go about it.

But I was a bit worried when I did not get any recovery working, but this was mostly because I interpreted the "server system variable" in the recovery documentation as an environment variable.

Attached is an error log (of "one crash cycle"). The config files in /etc/mysql are the default Debian 10 configs, which are pretty much empty. Previously today I did some changes to the Nextcloud database (I was Enabling MySQL 4-byte support), in case that could be related.

error.log

Sorry about the tone in my previous post, my frustration levels has been a bit too high today.

Johnny Oskarsson added a comment - 2020-02-09 17:00 - edited I managed to recover from it just now, I finally got mysqld --innodb-force-recovery=5 working. I did a mysqldump --all-tables >mysql.backup , killed mysqld, removed everything in /var/lib/mysql, ran mysql_install_db and started mysqld anew and then did a mysql -u root <mysql.backup . Now it seems to work again, but I don't know if this was the best way to go about it. But I was a bit worried when I did not get any recovery working, but this was mostly because I interpreted the "server system variable" in the recovery documentation as an environment variable. Attached is an error log (of "one crash cycle"). The config files in /etc/mysql are the default Debian 10 configs, which are pretty much empty. Previously today I did some changes to the Nextcloud database (I was Enabling MySQL 4-byte support ), in case that could be related. error.log Sorry about the tone in my previous post, my frustration levels has been a bit too high today.

Elena Stepanova added a comment - 2020-02-09 19:35

joskar, thanks. Yes, such problems are frustrating for us too, as there isn't much we can do when it happens once in two years and cannot be reproduced. Maybe marko will come up with some idea, though.

Meanwhile, do you happen to still have the error log from the very first such crash and, importantly, the previous server session before it? It might be important to see what happened there before the problems started, maybe there were errors or warnings (or even notes) which will shed some light on it.

Elena Stepanova added a comment - 2020-02-09 19:35 joskar , thanks. Yes, such problems are frustrating for us too, as there isn't much we can do when it happens once in two years and cannot be reproduced. Maybe marko will come up with some idea, though. Meanwhile, do you happen to still have the error log from the very first such crash and, importantly, the previous server session before it? It might be important to see what happened there before the problems started, maybe there were errors or warnings (or even notes) which will shed some light on it.

Johnny Oskarsson made changes - 2020-02-12 18:09

Attachment

error.log.3 [ 50482 ]

Johnny Oskarsson added a comment - 2020-02-12 18:11

elenst, here are the logs I had on that day until the first assertion, which is to my knowledge the first such crash I have seen.

error.log.3

On that note, it is completely possible that my problems originates from malfunctioning hardware. Any help in narrowing this down would be appreciated.

Johnny Oskarsson added a comment - 2020-02-12 18:11 elenst , here are the logs I had on that day until the first assertion, which is to my knowledge the first such crash I have seen. error.log.3 On that note, it is completely possible that my problems originates from malfunctioning hardware. Any help in narrowing this down would be appreciated.

Elena Stepanova made changes - 2020-03-12 17:19

Labels

need_feedback

Daniel Black made changes - 2020-05-15 00:40

Link

This issue relates to ~~MDEV-22341~~ [ ~~MDEV-22341~~ ]

Alice Sherepa added a comment - 2020-11-03 10:29 - edited

Server crashed as in ~~MDEV-24096~~ and after that refused to restart (it started after--innodb_force_recovery=1 helps)
I attached datadir in data.7z - to reproduce: start mysqld with it.

10.5 44836bcd12e3974e79c928be74
2020-11-03 11:24:47 0 [ERROR] InnoDB: Not applying UNDO_APPEND due to corruption on [page id: space=0, page number=384]
2020-11-03 11:24:47 0 [ERROR] InnoDB: Set innodb_force_recovery=1 to ignore corruption.
2020-11-03 11:24:47 0x7f165541c880 InnoDB: Assertion failure in file /10.5/src/storage/innobase/include/fut0lst.h line 127
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 https://jira.mariadb.org/
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: https://mariadb.com/kb/en/library/innodb-recovery-modes/
InnoDB: about forcing recovery.
201103 11:24:47 [ERROR] mysqld got signal 6 ;

sigaction.c:0(__restore_rt)[0x7f16578553c0]
linux/raise.c:51(__GI_raise)[0x7f165734318b]
stdlib/abort.c:81(__GI_abort)[0x7f1657322859]
ut/ut0dbg.cc:60(_sub_D_00099_0)[0x55c4cf4e1e61]
include/fut0lst.h:128(flst_read_addr(unsigned char const*))[0x55c4cf102aa2]
include/fut0lst.h:142(flst_get_last(unsigned char const*))[0x55c4cf102bb2]
trx/trx0undo.cc:905(trx_undo_mem_create_at_db_start(trx_rseg_t*, unsigned long, unsigned int, unsigned long&))[0x55c4cf4dac41]
trx/trx0rseg.cc:433(trx_undo_lists_init(trx_rseg_t, unsigned long&, buf_block_t const))[0x55c4cf4a77a3]
trx/trx0rseg.cc:508(trx_rseg_mem_restore(trx_rseg_t, unsigned long&, mtr_t))[0x55c4cf4a7fa2]
trx/trx0rseg.cc:619(trx_rseg_array_init())[0x55c4cf4a8ed2]
trx/trx0trx.cc:743(trx_lists_init_at_db_start())[0x55c4cf4b6899]
srv/srv0start.cc:1479(srv_start(bool))[0x55c4cf409771]
handler/ha_innodb.cc:3939(innodb_init(void*))[0x55c4cef66a91]
sql/handler.cc:645(ha_initialize_handlerton(st_plugin_int*))[0x55c4ce116a97]
sql/sql_plugin.cc:1459(plugin_initialize(st_mem_root, st_plugin_int, int, char*, bool))[0x55c4cd9524c0]
sql/sql_plugin.cc:1751(plugin_init(int, char*, int))[0x55c4cd95444e]
sql/mysqld.cc:4915(init_server_components())[0x55c4cd60f230]
sql/mysqld.cc:5496(mysqld_main(int, char**))[0x55c4cd61122f]
sql/main.cc:25(main)[0x55c4cd5fac2d]
csu/libc-start.c:342(__libc_start_main)[0x7f16573240b3]

Alice Sherepa added a comment - 2020-11-03 10:29 - edited Server crashed as in MDEV-24096 and after that refused to restart (it started after--innodb_force_recovery=1 helps) I attached datadir in data.7z - to reproduce: start mysqld with it. 10.5 44836bcd12e3974e79c928be74 2020-11-03 11:24:47 0 [ERROR] InnoDB: Not applying UNDO_APPEND due to corruption on [page id: space=0, page number=384] 2020-11-03 11:24:47 0 [ERROR] InnoDB: Set innodb_force_recovery=1 to ignore corruption. 2020-11-03 11:24:47 0x7f165541c880 InnoDB: Assertion failure in file /10.5/src/storage/innobase/include/fut0lst.h line 127 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 https://jira.mariadb.org/ 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: https://mariadb.com/kb/en/library/innodb-recovery-modes/ InnoDB: about forcing recovery. 201103 11:24:47 [ERROR] mysqld got signal 6 ; sigaction.c:0(__restore_rt)[0x7f16578553c0] linux/raise.c:51(__GI_raise)[0x7f165734318b] stdlib/abort.c:81(__GI_abort)[0x7f1657322859] ut/ut0dbg.cc:60(_sub_D_00099_0)[0x55c4cf4e1e61] include/fut0lst.h:128(flst_read_addr(unsigned char const*))[0x55c4cf102aa2] include/fut0lst.h:142(flst_get_last(unsigned char const*))[0x55c4cf102bb2] trx/trx0undo.cc:905(trx_undo_mem_create_at_db_start(trx_rseg_t*, unsigned long, unsigned int, unsigned long&))[0x55c4cf4dac41] trx/trx0rseg.cc:433(trx_undo_lists_init(trx_rseg_t*, unsigned long&, buf_block_t const*))[0x55c4cf4a77a3] trx/trx0rseg.cc:508(trx_rseg_mem_restore(trx_rseg_t*, unsigned long&, mtr_t*))[0x55c4cf4a7fa2] trx/trx0rseg.cc:619(trx_rseg_array_init())[0x55c4cf4a8ed2] trx/trx0trx.cc:743(trx_lists_init_at_db_start())[0x55c4cf4b6899] srv/srv0start.cc:1479(srv_start(bool))[0x55c4cf409771] handler/ha_innodb.cc:3939(innodb_init(void*))[0x55c4cef66a91] sql/handler.cc:645(ha_initialize_handlerton(st_plugin_int*))[0x55c4ce116a97] sql/sql_plugin.cc:1459(plugin_initialize(st_mem_root*, st_plugin_int*, int*, char**, bool))[0x55c4cd9524c0] sql/sql_plugin.cc:1751(plugin_init(int*, char**, int))[0x55c4cd95444e] sql/mysqld.cc:4915(init_server_components())[0x55c4cd60f230] sql/mysqld.cc:5496(mysqld_main(int, char**))[0x55c4cd61122f] sql/main.cc:25(main)[0x55c4cd5fac2d] csu/libc-start.c:342(__libc_start_main)[0x7f16573240b3]

Alice Sherepa made changes - 2020-11-03 10:33

Attachment

data.7z [ 54612 ]

Alice Sherepa made changes - 2020-11-03 11:30

Assignee

Elena Stepanova [ elenst ]

Marko Mäkelä [ marko ]

Julian Rilli made changes - 2020-11-07 15:49

Attachment		error.log.1 [ 54720 ]
Attachment		etc_mysql.tar.gz [ 54721 ]

Julian Rilli added a comment - 2020-11-07 16:05

Hey, the same thing happened to me yesterday (mariadb-server-10.3 10.3.25-0+deb10u1; Linux Debian 10; Nextcloud 18.0.10.2; PHP 7.3.23). But the repair didn't work, with `--innodb-force-recovery=5` the mysql service came up again, but then mysql tables were missing in the engine. Well, I finally deleted the data folder, recreated the mysql user and restored the backup from the day before.

Julian Rilli added a comment - 2020-11-07 16:05 Hey, the same thing happened to me yesterday (mariadb-server-10.3 10.3.25-0+deb10u1; Linux Debian 10; Nextcloud 18.0.10.2; PHP 7.3.23). But the repair didn't work, with `--innodb-force-recovery=5` the mysql service came up again, but then mysql tables were missing in the engine. Well, I finally deleted the data folder, recreated the mysql user and restored the backup from the day before.

Marko Mäkelä added a comment - 2020-12-17 10:45

alice, what is the history of data.7z? Was that data directory at any point touched by MariaDB 10.5.7? If yes, then the corruption could have been introduced by the bug that was fixed in ~~MDEV-24096~~.

Marko Mäkelä added a comment - 2020-12-17 10:45 alice , what is the history of data.7z ? Was that data directory at any point touched by MariaDB 10.5.7? If yes, then the corruption could have been introduced by the bug that was fixed in MDEV-24096 .

Alice Sherepa added a comment - 2020-12-17 11:15 - edited

marko, yes, data.7z is exactly the datadir after hitting bug from ~~MDEV-24096~~, so it might be unrelated to the bug in the description, sorry for mixing it/

Alice Sherepa added a comment - 2020-12-17 11:15 - edited marko , yes, data.7z is exactly the datadir after hitting bug from MDEV-24096 , so it might be unrelated to the bug in the description, sorry for mixing it/

Sergei Golubchik made changes - 2021-02-15 20:19

Fix Version/s

N/A [ 14700 ]

Sergei Golubchik made changes - 2021-02-15 20:19

Fix Version/s

10.2 [ 14601 ]

Marko Mäkelä added a comment - 2021-04-26 13:05

We have daily internal testing that involves killing and restarting the server, or running Mariabackup concurrently with a write workload, and restoring the data. If this type of errors would occur in any way regularly, we would detect it.

Two known sources of this type of problems are innodb_scrub_log (deprecated and ignored in ~~MDEV-21870~~) and the scrubbing of InnoDB tables (reimplemented in ~~MDEV-8139~~).

Bad things can also happen if the server is being run on an unreliable file system, such as some implementations of NFS. Also, in the case of a power outage, one may learn in the hard way that some storage devices are cheating with volatile caches or by reordering writes. The messages "log sequence number is in the future" basically mean that you have to treat all InnoDB data as seriously corrupted.

Marko Mäkelä added a comment - 2021-04-26 13:05 We have daily internal testing that involves killing and restarting the server, or running Mariabackup concurrently with a write workload, and restoring the data. If this type of errors would occur in any way regularly, we would detect it. Two known sources of this type of problems are innodb_scrub_log (deprecated and ignored in MDEV-21870 ) and the scrubbing of InnoDB tables (reimplemented in MDEV-8139 ). Bad things can also happen if the server is being run on an unreliable file system, such as some implementations of NFS. Also, in the case of a power outage, one may learn in the hard way that some storage devices are cheating with volatile caches or by reordering writes. The messages "log sequence number is in the future" basically mean that you have to treat all InnoDB data as seriously corrupted.

Marko Mäkelä made changes - 2021-04-26 13:05

Fix Version/s		N/A [ 14700 ]
Fix Version/s	10.2 [ 14601 ]
Resolution		Cannot Reproduce [ 5 ]
Status	Open [ 1 ]	Closed [ 6 ]

Sergei Golubchik made changes - 2021-12-06 21:45

Workflow

MariaDB v3 [ 82335 ]

MariaDB v4 [ 152735 ]

Jose Sanchez made changes - 2023-12-19 19:34

Comment

[ I have just experienced this in mysqld Ver 10.5.9-MariaDB for Linux on x86_64 (Arch Linux)

{noformat}
➜ akonadi "/usr/bin/mysqld" --verbose --defaults-file=/home/zaffy/.local/share/akonadi/mysql.conf --datadir=/home/zaffy/.local/share/akonadi/db_data/ --socket=/run/user/1000/akonadi/mysql.socket --pid-file=/run/user/1000/akonadi/mysql.pid
2021-05-06 13:43:36 0 [Note] /usr/bin/mysqld (mysqld 10.5.9-MariaDB) starting as process 7069 ...
2021-05-06 13:43:36 0 [Note] InnoDB: Uses event mutexes
2021-05-06 13:43:36 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2021-05-06 13:43:36 0 [Note] InnoDB: Number of pools: 1
2021-05-06 13:43:36 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions
2021-05-06 13:43:36 0 [Note] mysqld: O_TMPFILE is not supported on /tmp (disabling future attempts)
2021-05-06 13:43:36 0 [Note] InnoDB: Using Linux native AIO
2021-05-06 13:43:36 0 [Note] InnoDB: Initializing buffer pool, total size = 134217728, chunk size = 134217728
2021-05-06 13:43:36 0 [Note] InnoDB: Completed initialization of buffer pool
2021-05-06 13:43:36 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2021-05-06 13:43:36 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=75109388,75109388
2021-05-06 13:43:36 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=9, page number=87] with future log sequence number 75404420
2021-05-06 13:43:36 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=9, page number=86] with future log sequence number 75395868
2021-05-06 13:43:36 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=9, page number=83] with future log sequence number 75377726
2021-05-06 13:43:36 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=9, page number=82] with future log sequence number 75376916
2021-05-06 13:43:36 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=9, page number=81] with future log sequence number 75402089
2021-05-06 13:43:36 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=9, page number=64] with future log sequence number 75376593
2021-05-06 13:43:36 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=9, page number=15] with future log sequence number 75404065
2021-05-06 13:43:36 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=9, page number=63] with future log sequence number 75402142
2021-05-06 13:43:36 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=9, page number=21] with future log sequence number 75404948
2021-05-06 13:43:36 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=9, page number=16] with future log sequence number 75404120
2021-05-06 13:43:36 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=9, page number=17] with future log sequence number 75404894
2021-05-06 13:43:36 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=9, page number=13] with future log sequence number 75402104
2021-05-06 13:43:36 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=9, page number=9] with future log sequence number 75396028
2021-05-06 13:43:36 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=9, page number=3] with future log sequence number 75402059
2021-05-06 13:43:36 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=408] with future log sequence number 75371418
2021-05-06 13:43:36 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=243] with future log sequence number 75398091
2021-05-06 13:43:36 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=355] with future log sequence number 75383510
2021-05-06 13:43:36 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=300] with future log sequence number 75384666
2021-05-06 13:43:36 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=415] with future log sequence number 75383212
2021-05-06 13:43:36 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=299] with future log sequence number 75384640
2021-05-06 13:43:36 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=319] with future log sequence number 75383053
2021-05-06 13:43:36 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=298] with future log sequence number 75384614
2021-05-06 13:43:36 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=432] with future log sequence number 75382670
2021-05-06 13:43:36 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=297] with future log sequence number 75382909
2021-05-06 13:43:36 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=324] with future log sequence number 75382504
2021-05-06 13:43:36 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=296] with future log sequence number 75382883
2021-05-06 13:43:36 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=511] with future log sequence number 75382196
2021-05-06 13:43:36 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=295] with future log sequence number 75382857
2021-05-06 13:43:36 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=490] with future log sequence number 75381984
2021-05-06 13:43:36 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=294] with future log sequence number 75382831
2021-05-06 13:43:36 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=445] with future log sequence number 75381684
2021-05-06 13:43:36 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=293] with future log sequence number 75382805
2021-05-06 13:43:36 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=326] with future log sequence number 75381455
2021-05-06 13:43:36 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=292] with future log sequence number 75382763
2021-05-06 13:43:36 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=427] with future log sequence number 75381236
2021-05-06 13:43:36 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=291] with future log sequence number 75382737
2021-05-06 13:43:36 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=366] with future log sequence number 75380972
2021-05-06 13:43:36 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=290] with future log sequence number 75382711
2021-05-06 13:43:36 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=347] with future log sequence number 75332114
2021-05-06 13:43:36 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=289] with future log sequence number 75332951
2021-05-06 13:43:36 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=334] with future log sequence number 75379472
2021-05-06 13:43:36 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=288] with future log sequence number 75379513
2021-05-06 13:43:36 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=306] with future log sequence number 75379260
2021-05-06 13:43:36 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=287] with future log sequence number 75379327
2021-05-06 13:43:36 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=369] with future log sequence number 75331701
2021-05-06 13:43:36 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=286] with future log sequence number 75331769
2021-05-06 13:43:36 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=410] with future log sequence number 75379085
2021-05-06 13:43:36 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=285] with future log sequence number 75379301
2021-05-06 13:43:36 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=317] with future log sequence number 75378874
2021-05-06 13:43:36 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=284] with future log sequence number 75378941
2021-05-06 13:43:36 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=481] with future log sequence number 75378667
2021-05-06 13:43:36 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=283] with future log sequence number 75378915
2021-05-06 13:43:36 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=340] with future log sequence number 75378295
2021-05-06 13:43:36 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=282] with future log sequence number 75378337
2021-05-06 13:43:36 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=498] with future log sequence number 75330458
2021-05-06 13:43:36 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=281] with future log sequence number 75331304
2021-05-06 13:43:36 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=471] with future log sequence number 75377938
2021-05-06 13:43:36 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=280] with future log sequence number 75378135
2021-05-06 13:43:36 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=333] with future log sequence number 75377772
2021-05-06 13:43:36 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=279] with future log sequence number 75378109
2021-05-06 13:43:36 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=403] with future log sequence number 75377411
2021-05-06 13:43:36 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=278] with future log sequence number 75378083
2021-05-06 13:43:36 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=352] with future log sequence number 75376907
2021-05-06 13:43:36 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=277] with future log sequence number 75378057
2021-05-06 13:43:36 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=505] with future log sequence number 75376584
2021-05-06 13:43:36 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=276] with future log sequence number 75378031
2021-05-06 13:43:36 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=404] with future log sequence number 75376313
2021-05-06 13:43:36 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=275] with future log sequence number 75378005
2021-05-06 13:43:36 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=343] with future log sequence number 75327711
2021-05-06 13:43:36 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=274] with future log sequence number 75327778
2021-05-06 13:43:36 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=339] with future log sequence number 75376144
2021-05-06 13:43:36 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=273] with future log sequence number 75377979
2021-05-06 13:43:36 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=316] with future log sequence number 75327329
2021-05-06 13:43:36 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=272] with future log sequence number 75327370
2021-05-06 13:43:36 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=323] with future log sequence number 75327013
2021-05-06 13:43:36 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=271] with future log sequence number 75327185
2021-05-06 13:43:36 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=384] with future log sequence number 75375530
2021-05-06 13:43:36 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=270] with future log sequence number 75375809
2021-05-06 13:43:36 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=315] with future log sequence number 75372253
2021-05-06 13:43:36 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=269] with future log sequence number 75375783
2021-05-06 13:43:36 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=509] with future log sequence number 75372094
2021-05-06 13:43:36 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=266] with future log sequence number 75375757
2021-05-06 13:43:36 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=342] with future log sequence number 75371867
2021-05-06 13:43:36 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=265] with future log sequence number 75375731
2021-05-06 13:43:36 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=472] with future log sequence number 75371209
2021-05-06 13:43:36 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=263] with future log sequence number 75371496
2021-05-06 13:43:36 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=348] with future log sequence number 75371044
2021-05-06 13:43:36 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=262] with future log sequence number 75371470
2021-05-06 13:43:36 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=301] with future log sequence number 75325835
2021-05-06 13:43:36 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=261] with future log sequence number 75327055
2021-05-06 13:43:36 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=346] with future log sequence number 75370734
2021-05-06 13:43:36 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=259] with future log sequence number 75371444
2021-05-06 13:43:36 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=258] with future log sequence number 75371418
2021-05-06 13:43:36 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=257] with future log sequence number 75371347
2021-05-06 13:43:36 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=497] with future log sequence number 75369530
2021-05-06 13:43:36 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=256] with future log sequence number 75371276
2021-05-06 13:43:36 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=438] with future log sequence number 75369244
2021-05-06 13:43:36 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=255] with future log sequence number 75371250
2021-05-06 13:43:36 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=0, page number=345] with future log sequence number 75368930
2021-05-06 13:43:36 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=23, page number=17] with future log sequence number 75404660
2021-05-06 13:43:36 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=23, page number=9] with future log sequence number 75404651
2021-05-06 13:43:36 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=23, page number=7] with future log sequence number 75404637
2021-05-06 13:43:36 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=20, page number=52] with future log sequence number 75377475
2021-05-06 13:43:36 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=23, page number=1] with future log sequence number 75404651
2021-05-06 13:43:36 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=20, page number=18] with future log sequence number 75400757
2021-05-06 13:43:36 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=20, page number=30] with future log sequence number 75400733
2021-05-06 13:43:36 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=20, page number=14] with future log sequence number 75400904
2021-05-06 13:43:36 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=20, page number=15] with future log sequence number 75400719
2021-05-06 13:43:36 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=13, page number=3] with future log sequence number 75405887
2021-05-06 13:43:36 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=12, page number=365] with future log sequence number 75403129
2021-05-06 13:43:36 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=20, page number=1] with future log sequence number 75338706
2021-05-06 13:43:36 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=12, page number=363] with future log sequence number 75401076
2021-05-06 13:43:36 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=12, page number=361] with future log sequence number 75402909
2021-05-06 13:43:36 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=12, page number=233] with future log sequence number 75285481
2021-05-06 13:43:36 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=12, page number=232] with future log sequence number 75246246
2021-05-06 13:43:36 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=12, page number=187] with future log sequence number 75403437
2021-05-06 13:43:36 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=12, page number=186] with future log sequence number 75368484
2021-05-06 13:43:36 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=12, page number=185] with future log sequence number 75324376
2021-05-06 13:43:36 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=12, page number=57] with future log sequence number 75403155
2021-05-06 13:43:36 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=9, page number=256] with future log sequence number 75405664
2021-05-06 13:43:36 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=12, page number=15] with future log sequence number 75403140
2021-05-06 13:43:36 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=12, page number=11] with future log sequence number 75402780
2021-05-06 13:43:36 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=12, page number=3] with future log sequence number 75403099
2021-05-06 13:43:36 0 [Warning] InnoDB: Ignoring a doublewrite copy of page [page id: space=12, page number=2] with future log sequence number 75366560
2021-05-06 13:43:36 0 [ERROR] InnoDB: Page [page id: space=0, page number=2] log sequence number 75269799 is in the future! Current system log sequence number 75236723.
2021-05-06 13:43:36 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2021-05-06 13:43:36 0 [ERROR] InnoDB: Page [page id: space=0, page number=6] log sequence number 75337034 is in the future! Current system log sequence number 75236723.
2021-05-06 13:43:36 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2021-05-06 13:43:36 0 [ERROR] InnoDB: Page [page id: space=0, page number=309] log sequence number 75335572 is in the future! Current system log sequence number 75236723.
2021-05-06 13:43:36 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2021-05-06 13:43:36 0 [ERROR] InnoDB: Page [page id: space=0, page number=45] log sequence number 75337058 is in the future! Current system log sequence number 75236723.
2021-05-06 13:43:36 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2021-05-06 13:43:36 0 [ERROR] InnoDB: Page [page id: space=0, page number=418] log sequence number 75335790 is in the future! Current system log sequence number 75236723.
2021-05-06 13:43:36 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2021-05-06 13:43:36 0 [ERROR] InnoDB: Page [page id: space=0, page number=46] log sequence number 75384516 is in the future! Current system log sequence number 75236723.
2021-05-06 13:43:36 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2021-05-06 13:43:36 0 [ERROR] InnoDB: Page [page id: space=0, page number=487] log sequence number 75383669 is in the future! Current system log sequence number 75236723.
2021-05-06 13:43:36 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2021-05-06 13:43:36 0 [ERROR] InnoDB: Page [page id: space=0, page number=47] log sequence number 75337106 is in the future! Current system log sequence number 75236723.
2021-05-06 13:43:36 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2021-05-06 13:43:36 0 [ERROR] InnoDB: Page [page id: space=0, page number=383] log sequence number 75336313 is in the future! Current system log sequence number 75236723.
2021-05-06 13:43:36 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2021-05-06 13:43:36 0 [ERROR] InnoDB: Page [page id: space=0, page number=48] log sequence number 75384540 is in the future! Current system log sequence number 75236723.
2021-05-06 13:43:36 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2021-05-06 13:43:36 0 [ERROR] InnoDB: Page [page id: space=0, page number=446] log sequence number 75383977 is in the future! Current system log sequence number 75236723.
2021-05-06 13:43:36 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2021-05-06 13:43:36 0 [ERROR] InnoDB: Page [page id: space=0, page number=49] log sequence number 75384564 is in the future! Current system log sequence number 75236723.
2021-05-06 13:43:36 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2021-05-06 13:43:36 0 [ERROR] InnoDB: Page [page id: space=0, page number=349] log sequence number 75384285 is in the future! Current system log sequence number 75236723.
2021-05-06 13:43:36 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2021-05-06 13:43:36 0 [ERROR] InnoDB: Page [page id: space=0, page number=50] log sequence number 75384588 is in the future! Current system log sequence number 75236723.
2021-05-06 13:43:36 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2021-05-06 13:43:36 0 [ERROR] InnoDB: Page [page id: space=0, page number=476] log sequence number 75384476 is in the future! Current system log sequence number 75236723.
2021-05-06 13:43:36 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2021-05-06 13:43:36 0 [ERROR] InnoDB: Page [page id: space=0, page number=51] log sequence number 75337741 is in the future! Current system log sequence number 75236723.
2021-05-06 13:43:36 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2021-05-06 13:43:36 0 [ERROR] InnoDB: Page [page id: space=0, page number=351] log sequence number 75337527 is in the future! Current system log sequence number 75236723.
2021-05-06 13:43:36 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2021-05-06 13:43:36 0 [ERROR] InnoDB: Page [page id: space=0, page number=52] log sequence number 75385045 is in the future! Current system log sequence number 75236723.
2021-05-06 13:43:36 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2021-05-06 13:43:36 0 [ERROR] InnoDB: Page [page id: space=0, page number=371] log sequence number 75384848 is in the future! Current system log sequence number 75236723.
2021-05-06 13:43:36 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2021-05-06 13:43:36 0 [ERROR] InnoDB: Page [page id: space=0, page number=53] log sequence number 75385069 is in the future! Current system log sequence number 75236723.
2021-05-06 13:43:36 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2021-05-06 13:43:36 0 [ERROR] InnoDB: Page [page id: space=0, page number=311] log sequence number 75385006 is in the future! Current system log sequence number 75236723.
2021-05-06 13:43:36 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2021-05-06 13:43:36 0 [ERROR] InnoDB: Page [page id: space=0, page number=54] log sequence number 75385254 is in the future! Current system log sequence number 75236723.
2021-05-06 13:43:36 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2021-05-06 13:43:36 0 [ERROR] InnoDB: Page [page id: space=0, page number=407] log sequence number 75385214 is in the future! Current system log sequence number 75236723.
2021-05-06 13:43:36 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2021-05-06 13:43:36 0 [ERROR] InnoDB: Page [page id: space=0, page number=55] log sequence number 75290001 is in the future! Current system log sequence number 75236723.
2021-05-06 13:43:36 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2021-05-06 13:43:36 0 [ERROR] InnoDB: Page [page id: space=0, page number=506] log sequence number 75289108 is in the future! Current system log sequence number 75236723.
2021-05-06 13:43:36 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2021-05-06 13:43:36 0 [ERROR] InnoDB: Page [page id: space=0, page number=56] log sequence number 75391059 is in the future! Current system log sequence number 75236723.
2021-05-06 13:43:36 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2021-05-06 13:43:36 0 [ERROR] InnoDB: Page [page id: space=0, page number=491] log sequence number 75390366 is in the future! Current system log sequence number 75236723.
2021-05-06 13:43:36 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2021-05-06 13:43:36 0 [ERROR] InnoDB: Page [page id: space=0, page number=57] log sequence number 75391083 is in the future! Current system log sequence number 75236723.
2021-05-06 13:43:36 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2021-05-06 13:43:36 0 [ERROR] InnoDB: Page [page id: space=0, page number=462] log sequence number 75390643 is in the future! Current system log sequence number 75236723.
2021-05-06 13:43:36 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2021-05-06 13:43:36 0 [ERROR] InnoDB: Page [page id: space=0, page number=58] log sequence number 75391107 is in the future! Current system log sequence number 75236723.
2021-05-06 13:43:36 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2021-05-06 13:43:36 0 [ERROR] InnoDB: Page [page id: space=0, page number=337] log sequence number 75390845 is in the future! Current system log sequence number 75236723.
2021-05-06 13:43:36 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2021-05-06 13:43:36 0 [ERROR] InnoDB: Page [page id: space=0, page number=59] log sequence number 75391131 is in the future! Current system log sequence number 75236723.
2021-05-06 13:43:36 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2021-05-06 13:43:36 0 [ERROR] InnoDB: Page [page id: space=0, page number=499] log sequence number 75391019 is in the future! Current system log sequence number 75236723.
2021-05-06 13:43:36 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2021-05-06 13:43:36 0 [ERROR] InnoDB: Page [page id: space=0, page number=60] log sequence number 75391636 is in the future! Current system log sequence number 75236723.
2021-05-06 13:43:36 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2021-05-06 13:43:36 0 [ERROR] InnoDB: Page [page id: space=0, page number=312] log sequence number 75391407 is in the future! Current system log sequence number 75236723.
2021-05-06 13:43:36 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2021-05-06 13:43:36 0 [ERROR] InnoDB: Page [page id: space=0, page number=61] log sequence number 75391660 is in the future! Current system log sequence number 75236723.
2021-05-06 13:43:36 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2021-05-06 13:43:36 0 [ERROR] InnoDB: Page [page id: space=0, page number=466] log sequence number 75391597 is in the future! Current system log sequence number 75236723.
2021-05-06 13:43:36 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2021-05-06 13:43:36 0 [ERROR] InnoDB: Page [page id: space=0, page number=62] log sequence number 75391845 is in the future! Current system log sequence number 75236723.
2021-05-06 13:43:36 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2021-05-06 13:43:36 0 [ERROR] InnoDB: Page [page id: space=0, page number=350] log sequence number 75391805 is in the future! Current system log sequence number 75236723.
2021-05-06 13:43:36 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2021-05-06 13:43:36 0 [ERROR] InnoDB: Page [page id: space=0, page number=63] log sequence number 75340218 is in the future! Current system log sequence number 75236723.
2021-05-06 13:43:36 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2021-05-06 13:43:36 0 [ERROR] InnoDB: Page [page id: space=0, page number=386] log sequence number 75339360 is in the future! Current system log sequence number 75236723.
2021-05-06 13:43:36 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2021-05-06 13:43:36 0 [ERROR] InnoDB: Page [page id: space=0, page number=192] log sequence number 75393944 is in the future! Current system log sequence number 75236723.
2021-05-06 13:43:36 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2021-05-06 13:43:36 0 [ERROR] InnoDB: Page [page id: space=0, page number=503] log sequence number 75393262 is in the future! Current system log sequence number 75236723.
2021-05-06 13:43:36 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2021-05-06 13:43:36 0 [ERROR] InnoDB: Page [page id: space=0, page number=193] log sequence number 75393970 is in the future! Current system log sequence number 75236723.
2021-05-06 13:43:36 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2021-05-06 13:43:36 0 [ERROR] InnoDB: Page [page id: space=0, page number=500] log sequence number 75393524 is in the future! Current system log sequence number 75236723.
2021-05-06 13:43:36 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2021-05-06 13:43:36 0 [ERROR] InnoDB: Page [page id: space=0, page number=194] log sequence number 75393996 is in the future! Current system log sequence number 75236723.
2021-05-06 13:43:36 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2021-05-06 13:43:36 0 [ERROR] InnoDB: Page [page id: space=0, page number=420] log sequence number 75393743 is in the future! Current system log sequence number 75236723.
2021-05-06 13:43:36 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2021-05-06 13:43:36 0 [ERROR] InnoDB: Page [page id: space=0, page number=195] log sequence number 75394022 is in the future! Current system log sequence number 75236723.
2021-05-06 13:43:36 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2021-05-06 13:43:36 0 [ERROR] InnoDB: Page [page id: space=0, page number=455] log sequence number 75393902 is in the future! Current system log sequence number 75236723.
2021-05-06 13:43:36 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2021-05-06 13:43:36 0 [ERROR] InnoDB: Page [page id: space=0, page number=196] log sequence number 75395195 is in the future! Current system log sequence number 75236723.
2021-05-06 13:43:36 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2021-05-06 13:43:36 0 [ERROR] InnoDB: Page [page id: space=0, page number=329] log sequence number 75394183 is in the future! Current system log sequence number 75236723.
2021-05-06 13:43:36 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2021-05-06 13:43:36 0 [ERROR] InnoDB: Page [page id: space=0, page number=197] log sequence number 75340312 is in the future! Current system log sequence number 75236723.
2021-05-06 13:43:36 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2021-05-06 13:43:36 0 [ERROR] InnoDB: Page [page id: space=0, page number=327] log sequence number 75339858 is in the future! Current system log sequence number 75236723.
2021-05-06 13:43:36 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2021-05-06 13:43:36 0 [ERROR] InnoDB: Page [page id: space=0, page number=198] log sequence number 75340338 is in the future! Current system log sequence number 75236723.
2021-05-06 13:43:36 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2021-05-06 13:43:36 0 [ERROR] InnoDB: Page [page id: space=0, page number=488] log sequence number 75340019 is in the future! Current system log sequence number 75236723.
2021-05-06 13:43:36 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2021-05-06 13:43:36 0 [ERROR] InnoDB: Page [page id: space=0, page number=199] log sequence number 75395221 is in the future! Current system log sequence number 75236723.
2021-05-06 13:43:36 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2021-05-06 13:43:36 0 [ERROR] InnoDB: Page [page id: space=0, page number=507] log sequence number 75394343 is in the future! Current system log sequence number 75236723.
2021-05-06 13:43:36 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2021-05-06 13:43:36 0 [ERROR] InnoDB: Page [page id: space=0, page number=200] log sequence number 75395247 is in the future! Current system log sequence number 75236723.
2021-05-06 13:43:36 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2021-05-06 13:43:36 0 [ERROR] InnoDB: Page [page id: space=0, page number=338] log sequence number 75394503 is in the future! Current system log sequence number 75236723.
2021-05-06 13:43:36 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2021-05-06 13:43:36 0 [ERROR] InnoDB: Page [page id: space=0, page number=201] log sequence number 75340728 is in the future! Current system log sequence number 75236723.
2021-05-06 13:43:36 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2021-05-06 13:43:36 0 [ERROR] InnoDB: Page [page id: space=0, page number=353] log sequence number 75340529 is in the future! Current system log sequence number 75236723.
2021-05-06 13:43:36 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2021-05-06 13:43:36 0 [ERROR] InnoDB: Page [page id: space=0, page number=202] log sequence number 75395273 is in the future! Current system log sequence number 75236723.
2021-05-06 13:43:36 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2021-05-06 13:43:36 0 [ERROR] InnoDB: Page [page id: space=0, page number=467] log sequence number 75394812 is in the future! Current system log sequence number 75236723.
2021-05-06 13:43:36 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2021-05-06 13:43:36 0 [ERROR] InnoDB: Page [page id: space=0, page number=203] log sequence number 75395299 is in the future! Current system log sequence number 75236723.
2021-05-06 13:43:36 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2021-05-06 13:43:36 0 [ERROR] InnoDB: Page [page id: space=0, page number=447] log sequence number 75395137 is in the future! Current system log sequence number 75236723.
2021-05-06 13:43:36 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2021-05-06 13:43:36 0 [ERROR] InnoDB: Page [page id: space=0, page number=204] log sequence number 75341635 is in the future! Current system log sequence number 75236723.
2021-05-06 13:43:36 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2021-05-06 13:43:36 0 [ERROR] InnoDB: Page [page id: space=0, page number=493] log sequence number 75341074 is in the future! Current system log sequence number 75236723.
2021-05-06 13:43:36 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2021-05-06 13:43:36 0 [ERROR] InnoDB: Page [page id: space=0, page number=205] log sequence number 75297490 is in the future! Current system log sequence number 75236723.
2021-05-06 13:43:36 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2021-05-06 13:43:36 0 [ERROR] InnoDB: Page [page id: space=0, page number=320] log sequence number 75297241 is in the future! Current system log sequence number 75236723.
2021-05-06 13:43:36 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2021-05-06 13:43:36 0 [ERROR] InnoDB: Page [page id: space=0, page number=206] log sequence number 75341661 is in the future! Current system log sequence number 75236723.
2021-05-06 13:43:36 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2021-05-06 13:43:36 0 [ERROR] InnoDB: Page [page id: space=0, page number=318] log sequence number 75341234 is in the future! Current system log sequence number 75236723.
2021-05-06 13:43:36 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2021-05-06 13:43:36 0 [ERROR] InnoDB: Page [page id: space=0, page number=207] log sequence number 75298928 is in the future! Current system log sequence number 75236723.
2021-05-06 13:43:36 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2021-05-06 13:43:36 0 [ERROR] InnoDB: Page [page id: space=0, page number=330] log sequence number 75297660 is in the future! Current system log sequence number 75236723.
2021-05-06 13:43:36 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2021-05-06 13:43:36 0 [ERROR] InnoDB: Page [page id: space=0, page number=208] log sequence number 75395682 is in the future! Current system log sequence number 75236723.
2021-05-06 13:43:36 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2021-05-06 13:43:36 0x7f45b222ec40 InnoDB: Assertion failure in file /build/mariadb/src/mariadb-10.5.9/storage/innobase/include/fut0lst.h line 127
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 https://jira.mariadb.org/
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: https://mariadb.com/kb/en/library/innodb-recovery-modes/
InnoDB: about forcing recovery.
210506 13:43:36 [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.5.9-MariaDB
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 = 467864 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 0x49000
??:0(my_print_stacktrace)[0x55fa57679ebf]
??:0(handle_fatal_signal)[0x55fa5715d650]
sigaction.c:0(__restore_rt)[0x7f45b29ad960]
:0(__GI_raise)[0x7f45b24c4ef5]
:0(__GI_abort)[0x7f45b24ae862]
??:0(Wsrep_server_service::log_dummy_write_set(wsrep::client_state&, wsrep::ws_meta const&))[0x55fa56e3c586]
??:0(Wsrep_server_service::log_dummy_write_set(wsrep::client_state&, wsrep::ws_meta const&))[0x55fa56e3c071]
??:0(Wsrep_server_service::log_dummy_write_set(wsrep::client_state&, wsrep::ws_meta const&))[0x55fa56e3c2e9]
??:0(std::unique_lock<std::mutex>::unlock())[0x55fa575471cc]
??:0(std::unique_lock<std::mutex>::unlock())[0x55fa5754d6d0]
??:0(Wsrep_server_service::log_dummy_write_set(wsrep::client_state&, wsrep::ws_meta const&))[0x55fa56e35e1d]
??:0(wsrep_notify_status(wsrep::server_state::state, wsrep::view const*))[0x55fa5746392a]
??:0(ha_initialize_handlerton(st_plugin_int*))[0x55fa57160193]
??:0(sys_var_pluginvar::sys_var_pluginvar(sys_var_chain*, char const*, st_plugin_int*, st_mysql_sys_var*))[0x55fa56f738dd]
??:0(plugin_init(int*, char**, int))[0x55fa56f74a04]
??:0(unireg_abort)[0x55fa56e9e89a]
??:0(mysqld_main(int, char**))[0x55fa56ea4725]
??:0(__libc_start_main)[0x7f45b24afb25]
??:0(_start)[0x55fa56e986fe]
The manual page at https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mysqld/ contains
information that should help you find out what is causing the crash.
Writing a core file...
Working directory at /home/zaffy/.local/share/akonadi/db_data
Resource Limits:
Limit Soft Limit Hard Limit Units
Max cpu time unlimited unlimited seconds
Max file size unlimited unlimited bytes
Max data size unlimited unlimited bytes
Max stack size 8388608 unlimited bytes
Max core file size unlimited unlimited bytes
Max resident set unlimited unlimited bytes
Max processes 128003 128003 processes
Max open files 32198 32198 files
Max locked memory 65536 65536 bytes
Max address space unlimited unlimited bytes
Max file locks unlimited unlimited locks
Max pending signals 128003 128003 signals
Max msgqueue size 819200 819200 bytes
Max nice priority 0 0
Max realtime priority 0 0
Max realtime timeout unlimited unlimited us
Core pattern: |/usr/lib/systemd/systemd-coredump %P %u %g %s %t %c %h

[1] 7069 abort (core dumped) "/usr/bin/mysqld" --verbose --socket=/run/user/1000/akonadi/mysql.socket
{noformat}
]

Jira Automation (IT) made changes - 2024-07-04 08:10

Zendesk Related Tickets

160805

People

Assignee:: Marko Mäkelä

Reporter:: Elena Stepanova

Votes:: 3 Vote for this issue

Watchers:: 9 Start watching this issue

Dates

Created:: 2017-08-31 10:13

Updated:: 2024-07-08 00:38

Resolved:: 2021-04-26 13:05

Git Integration

Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.

MariaDB Server

Details

Description

Attachments

Attachments

Issue Links

Activity

People

Dates

Git Integration