innodb log sequence number (far) into the future / Online DDL

2024-05-01 13:40:17 131 [ERROR] InnoDB: Page [page id: space=1294, page number=2] log sequence number 17908275477 is in the future! Current system log sequence number 2535377.

2024-05-01 13:40:17 131 [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.

2024-05-01 13:40:17 131 [Note] InnoDB: Online DDL : Start reading clustered index of the table and create temporary files

2024-05-01 13:40:17 131 [Note] InnoDB: Online DDL : End of reading clustered index of the table and create temporary files

2024-05-01 13:40:17 131 [Note] InnoDB: Online DDL : Applying log to index

2024-05-01 13:40:19 132 [Note] InnoDB: Online DDL : Start reading clustered index of the table and create temporary files

2024-05-01 13:40:19 132 [Note] InnoDB: Online DDL : End of reading clustered index of the table and create temporary files

2024-05-01 13:40:19 132 [Note] InnoDB: Online DDL : Applying log to index

2024-05-01 13:41:05 73 [Note] InnoDB: Online DDL : Start reading clustered index of the table and create temporary files

2024-05-01 13:41:05 73 [Note] InnoDB: Online DDL : End of reading clustered index of the table and create temporary files

2024-05-01 13:41:05 73 [Note] InnoDB: Online DDL : Applying log to index

2024-05-01 13:41:30 0x7f18a6ffd700  InnoDB: Assertion failure in file ./storage/innobase/fsp/fsp0fsp.cc line 2824

InnoDB: Failing assertion: n != ULINT_UNDEFINED

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 mariadbd 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.

240501 13:41:30 [ERROR] mysqld got signal 6 ;

Sorry, we probably made a mistake, and this is a bug.

Your assistance in bug reporting will enable us to fix this for the next release.

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.23-MariaDB-0+deb11u1 source revision: 6cfd2ba397b0ca689d8ff1bdb9fc4a4dc516a5eb

key_buffer_size=16777216

read_buffer_size=131072

max_used_connections=21

max_threads=153

thread_count=21

It is possible that mysqld could use up to

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

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

Thread pointer: 0x55c92a0cd1d8

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 = 0x7f18a6ffccd8 thread_stack 0x49000

/usr/sbin/mariadbd(my_print_stacktrace+0x2e)[0x55c92840e14e]

/usr/sbin/mariadbd(handle_fatal_signal+0x475)[0x55c927f033b5]

/lib/x86_64-linux-gnu/libpthread.so.0(+0x13140)[0x7f18d9ffd140]

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

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

/usr/sbin/mariadbd(+0x64329a)[0x55c927bd429a]

/usr/sbin/mariadbd(+0x659650)[0x55c927bea650]

/usr/sbin/mariadbd(+0xd3b24a)[0x55c9282cc24a]

/usr/sbin/mariadbd(+0xd2e5c3)[0x55c9282bf5c3]

/usr/sbin/mariadbd(_ZN5tpool10task_group7executeEPNS_4taskE+0x8f)[0x55c9283b091f]

/usr/sbin/mariadbd(_ZN5tpool19thread_pool_generic11worker_mainEPNS_11worker_dataE+0x4f)[0x55c9283ae9bf]

/usr/lib/x86_64-linux-gnu/libstdc++.so.6(+0xceed0)[0x7f18d9ee5ed0]

/lib/x86_64-linux-gnu/libpthread.so.0(+0x7ea7)[0x7f18d9ff1ea7]

/lib/x86_64-linux-gnu/libc.so.6(clone+0x3f)[0x7f18d9bf8a6f]

Trying to get some variables.

Some pointers may be invalid and cause the dump to abort.

Query (0x0): (null)

Connection ID (thread ID): 0

Status: NOT_KILLED

Optimizer switch: index_merge=on,index_merge_union=on,index_merge_sort_union=on,index_merge_intersection=on,index_merge_sort_intersection=off,engine_condition_pushdown=off,index_condition_pushdown=on,derived_merge=on,derived_with_keys=on,firstmatch=on,loosescan=on,materialization=on,in_to_exists=on,semijoin=on,partial_match_rowid_merge=on,partial_match_table_scan=on,subquery_cache=on,mrr=off,mrr_cost_based=off,mrr_sort_keys=off,outer_join_with_cache=on,semijoin_with_cache=on,join_cache_incremental=on,join_cache_hashed=on,join_cache_bka=on,optimize_join_buffer_size=on,table_elimination=on,extended_keys=on,exists_to_in=on,orderby_uses_equalities=on,condition_pushdown_for_derived=on,split_materialized=on,condition_pushdown_for_subquery=on,rowid_filter=on,condition_pushdown_from_having=on,not_null_range_scan=off

The manual page at https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mariadbd/ contains

information that should help you find out what is causing the crash.

We think the query pointer is invalid, but we will try to print it anyway.

Query:

Writing a core file...

Working directory at /var/lib/mysql

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             unlimited            unlimited            processes

Max open files            1048576              1048576              files

Max locked memory         8388608              8388608              bytes

Max address space         unlimited            unlimited            bytes

Max file locks            unlimited            unlimited            locks

Max pending signals       14856                14856                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: core

Kernel version: Linux version 6.1.0-20-amd64 (debian-kernel@lists.debian.org) (gcc-12 (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 SMP PREEMPT_DYNAMIC Debian 6.1.85-1 (2024-04-11)

240501 13:41:30 mysqld_safe Number of processes running now: 0

240501 13:41:30 mysqld_safe mysqld restarted

2024-05-01 13:41:30 0 [Note] Starting MariaDB 10.5.23-MariaDB-0+deb11u1 source revision 6cfd2ba397b0ca689d8ff1bdb9fc4a4dc516a5eb as process 5080

2024-05-01 13:41:30 0 [Note] Initializing built-in plugins

2024-05-01 13:41:30 0 [Note] Initializing plugins specified on the command line

2024-05-01 13:41:30 0 [Warning] The parameter innodb_large_prefix is deprecated and has no effect. It may be removed in future releases. See https://mariadb.com/kb/en/library/xtradbinnodb-file-format/

2024-05-01 13:41:30 0 [Note] InnoDB: Uses event mutexes

2024-05-01 13:41:30 0 [Note] InnoDB: Compressed tables use zlib 1.2.11

2024-05-01 13:41:30 0 [Note] InnoDB: Number of pools: 1

2024-05-01 13:41:30 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions

2024-05-01 13:41:30 0 [Note] mariadbd: O_TMPFILE is not supported on /tmp (disabling future attempts)

2024-05-01 13:41:30 0 [Note] InnoDB: Using Linux native AIO

2024-05-01 13:41:30 0 [Note] InnoDB: Initializing buffer pool, total size = 134217728, chunk size = 134217728

2024-05-01 13:41:30 0 [Note] InnoDB: Completed initialization of buffer pool

2024-05-01 13:41:30 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=2446056,2446056

2024-05-01 13:41:30 0 [ERROR] InnoDB: Page [page id: space=0, page number=7] log sequence number 17907368362 is in the future! Current system log sequence number 3197064.

2024-05-01 13:41:30 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.

2024-05-01 13:41:30 0 [ERROR] InnoDB: Page [page id: space=0, page number=4] log sequence number 17744207355 is in the future! Current system log sequence number 3197064.

2024-05-01 13:41:30 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.

2024-05-01 13:41:30 0 [ERROR] InnoDB: Page [page id: space=0, page number=11] log sequence number 17908295370 is in the future! Current system log sequence number 3197064.

2024-05-01 13:41:30 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.

2024-05-01 13:41:30 0 [ERROR] InnoDB: invalid undo header offset 0

2024-05-01 13:41:30 0 [Note] InnoDB: Retry with innodb_force_recovery=5

2024-05-01 13:41:30 0 [ERROR] InnoDB: Plugin initialization aborted with error Data structure corruption

2024-05-01 13:41:30 0 [Note] InnoDB: Starting shutdown...

2024-05-01 13:41:30 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.

2024-05-01 13:41:30 0 [Note] Plugin 'FEEDBACK' is disabled.

2024-05-01 13:41:30 0 [Note] Initializing installed plugins

2024-05-01 13:41:30 0 [ERROR] Unknown/unsupported storage engine: InnoDB

2024-05-01 13:41:30 0 [ERROR] Aborting

240501 13:41:30 mysqld_safe mysqld from pid file /run/mysqld/mysqld.pid ended