InnoDB: Trying to read 16384 bytes at xxxx outside the bounds of the file: ./ibdata1

2024-10-01 12:04:25 7 [Note] InnoDB: Cannot close file ./dw_etl/QuickSearchSort.ibd because of pending fsync

2024-10-01 12:04:57 7 [Note] InnoDB: Cannot close file ./dw_etl/QuickSearchSort.ibd because of pending fsync

2024-10-01 12:26:13 153 [ERROR] InnoDB: Trying to read 16384 bytes at 70368744161280 outside the bounds of the file: ./ibdata1

2024-10-01 12:26:13 153 [ERROR] InnoDB: File './ibdata1' is corrupted

2024-10-01 12:26:13 0x7fae3f1fb640  InnoDB: Assertion failure in file /home/xxxx/mariadb/mariadb-10.6.19/storage/innobase/trx/trx0undo.cc line 1465

InnoDB: Failing assertion: rollback

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.

241001 12:26:13 [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.6.19-MariaDB-log source revision: 8f020508c87461bbeee551c3001acac56d506ae7

key_buffer_size=3221225472

read_buffer_size=131072

max_used_connections=42

max_threads=302

thread_count=41

It is possible that mysqld could use up to

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

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

Thread pointer: 0x7fb6d9e0e658

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

mysys/stacktrace.c:216(my_print_stacktrace)[0x558031b02332]

sql/signal_handler.cc:239(handle_fatal_signal)[0x558031573e55]

/lib/x86_64-linux-gnu/libc.so.6(+0x42520)[0x7fb6dc0f3520]

/lib/x86_64-linux-gnu/libc.so.6(+0x42520)[0x7fb6dc0f3520]

/lib/x86_64-linux-gnu/libc.so.6(pthread_kill+0x12c)[0x7fb6dc1479fc]

/lib/x86_64-linux-gnu/libc.so.6(raise+0x16)[0x7fb6dc0f3476]

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

2024-10-01 12:26:18 0 [Note] /usr/local/mysql/bin/mariadbd (initiated by: unknown): Normal shutdown

2024-10-01 12:26:18 6 [Note] Error reading relay log event: slave SQL thread was killed

2024-10-01 12:26:18 6 [Note] Slave SQL thread exiting, replication stopped in log 'bin-log.038405' at position 360850969, master: 192.168.30.18:3306

2024-10-01 12:26:18 5 [Note] Slave I/O thread exiting, read up to log 'bin-log.038405', position 360850969, master 192.168.30.18:3306

ut/ut0rbt.cc:460(rbt_eject_node(ib_rbt_node_t*, ib_rbt_node_t*) [clone .part.0])[0x5580311cf7d2]

include/dyn0buf.h:140(mtr_buf_t::block_t::init())[0x5580311cf657]

trx/trx0trx.cc:1968(trx_prepare_low(trx_t*))[0x5580319bda19]

trx/trx0trx.cc:1986(trx_prepare(trx_t*))[0x55803122fd51]

trx/trx0trx.cc:2043(trx_prepare_for_mysql(trx_t*))[0x5580319bf054]

handler/ha_innodb.cc:17130(innobase_xa_prepare(handlerton*, THD*, bool))[0x5580318b340a]

sql/handler.cc:1466(ha_commit_trans(THD*, bool))[0x5580315787f1]

sql/transaction.cc:497(trans_commit_stmt(THD*))[0x558031453ba0]

sql/sql_class.h:4540(THD::get_stmt_da())[0x558031328eac]

sql/sql_parse.cc:8182(mysql_parse(THD*, char*, unsigned int, Parser_state*))[0x5580313182f7]

sql/sql_parse.cc:1899(dispatch_command(enum_server_command, THD*, char*, unsigned int, bool))[0x558031325135]

sql/sql_parse.cc:1412(do_command(THD*, bool))[0x5580313274ae]

sql/sql_connect.cc:1417(do_handle_one_connection(CONNECT*, bool))[0x558031442687]

sql/sql_connect.cc:1325(handle_one_connection)[0x5580314429dd]

perfschema/pfs.cc:2204(pfs_spawn_thread)[0x55803180af36]

/lib/x86_64-linux-gnu/libc.so.6(+0x94ac3)[0x7fb6dc145ac3]

/lib/x86_64-linux-gnu/libc.so.6(+0x126850)[0x7fb6dc1d7850]

Trying to get some variables.

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

Query (0x7fb6d9e487f0): REPLACE INTO `tools`.`heartbeat` (ts, server_id, file, position, relay_master_log_file, exec_master_log_pos) VALUES ('2024-10-01T12:26:13.800640', '5',

Connection ID (thread ID): 153

Status: KILL_SERVER

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,inde

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.

Writing a core file...

Working directory at /mnt/scsi/mysql/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        0                    unlimited            bytes

Max resident set          unlimited            unlimited            bytes

Max processes             377706               377706               processes

Max open files            1048576              1048576              files

Max locked memory         65536                65536                bytes

Max address space         unlimited            unlimited            bytes

Max file locks            unlimited            unlimited            locks

Max pending signals       377706               377706               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/share/apport/apport -p%p -s%s -c%c -d%d -P%P -u%u -g%g -- %E

Kernel version: Linux version 5.15.0-118-generic (buildd@lcy02-amd64-080) (gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0, GNU ld (GNU Binutils for Ubuntu) 2.38) #128-Ubuntu SMP Fri

241001 12:26:28 mysqld_safe Number of processes running now: 0

241001 12:26:28 mysqld_safe mysqld restarted

2024-10-01 12:26:28 0 [Note] Starting MariaDB 10.6.19-MariaDB-log source revision 8f020508c87461bbeee551c3001acac56d506ae7 server_uid KXeBmuid5omrfaaTMDcljUHia5E= as process 32

2024-10-01 12:26:32 0 [Note] mariadbd: Aria engine: starting recovery

recovered pages: 0% 49% 65% 99% 100% (0.0 seconds); tables to flush: 1 0

 (0.0 seconds);

2024-10-01 12:26:32 0 [Note] mariadbd: Aria engine: recovery done

2024-10-01 12:26:33 0 [Note] mariadbd: AWS KMS plugin: loaded key 1, version 1, key length 128 bit

2024-10-01 12:26:33 0 [Note] InnoDB: Compressed tables use zlib 1.3.1

2024-10-01 12:26:33 0 [Note] InnoDB: Number of pools: 1

2024-10-01 12:26:33 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions

2024-10-01 12:26:33 0 [Note] InnoDB: Using Linux native AIO

2024-10-01 12:26:33 0 [Note] InnoDB: Initializing buffer pool, total size = 32212254720, chunk size = 134217728

2024-10-01 12:26:33 0 [Note] InnoDB: Completed initialization of buffer pool

2024-10-01 12:26:33 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=301067631532229,301069143937341

2024-10-01 12:26:48 0 [Note] InnoDB: Read redo log up to LSN=301068733913088

2024-10-01 12:26:55 0 [ERROR] InnoDB: Corrupted page identifier at 301069143888274; set innodb_force_recovery=1 to ignore the record.