InnoDB: Assertion failure in file /home/buildbot/buildbot/build/mariadb-10.4.12/storage/innobase/lock/lock0lock.cc

2024-03-14 09:11:12 0x7f8839ae0700  InnoDB: Assertion failure in file /home/buildbot/buildbot/build/mariadb-10.4.12/storage/innobase/lock/lock0lock.cc line 6901

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.

240314  9:11:12 [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.4.12-MariaDB-1:10.4.12+maria~buster-log

key_buffer_size=134217728

read_buffer_size=2097152

max_used_connections=1346

max_threads=2502

thread_count=817

It is possible that mysqld could use up to 

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

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

Thread pointer: 0x7f8358047d48

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

*** buffer overflow detected ***: /usr/sbin/mysqld terminated

2024-03-14  9:11:52 0 [Note] mysqld: Aria engine: starting recovery

tables to flush: 4 3 2 1 0

 (0.0 seconds); 

2024-03-14  9:11:52 0 [Note] mysqld: Aria engine: recovery done

2024-03-14  9:11:52 0 [Note] InnoDB: Using Linux native AIO

2024-03-14  9:11:52 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins

2024-03-14  9:11:52 0 [Note] InnoDB: Uses event mutexes

2024-03-14  9:11:52 0 [Note] InnoDB: Compressed tables use zlib 1.2.11

2024-03-14  9:11:52 0 [Note] InnoDB: Number of pools: 1

2024-03-14  9:11:52 0 [Note] InnoDB: Using SSE2 crc32 instructions

2024-03-14  9:11:52 0 [Note] mysqld: O_TMPFILE is not supported on /var/lib/mysql/tmp (disabling future attempts)

2024-03-14  9:11:53 0 [Note] InnoDB: Initializing buffer pool, total size = 354G, instances = 16, chunk size = 128M

2024-03-14  9:12:05 0 [Note] InnoDB: Completed initialization of buffer pool

2024-03-14  9:12:05 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().

2024-03-14  9:12:05 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=82292129095942

2024-03-14  9:12:11 0 [Note] InnoDB: Transaction 384313048155 was in the XA prepared state.

2024-03-14  9:12:11 0 [Note] InnoDB: Transaction 384313048156 was in the XA prepared state.

2024-03-14  9:12:11 0 [Note] InnoDB: 2 transaction(s) which must be rolled back or cleaned up in total 0 row operations to undo

2024-03-14  9:12:11 0 [Note] InnoDB: Trx id counter is 384313048157

2024-03-14  9:12:11 0 [Note] InnoDB: Starting final batch to recover 166439 pages from redo log.

2024-03-14  9:12:20 0 [Note] InnoDB: To recover: 30610 pages from log

2024-03-14  9:12:23 0 [Note] InnoDB: Last binlog file '/var/log/mysql/binlogs/mysql-bin.240055', position 96599871

2024-03-14  9:12:24 0 [Note] InnoDB: 128 out of 128 rollback segments are active.

2024-03-14  9:12:24 0 [Note] InnoDB: Starting in background the rollback of recovered transactions

2024-03-14  9:12:24 0 [Note] InnoDB: Rollback of non-prepared transactions completed

2024-03-14  9:12:24 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"

2024-03-14  9:12:24 0 [Note] InnoDB: Creating shared tablespace for temporary tables

2024-03-14  9:12:24 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...

2024-03-14  9:12:24 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.

2024-03-14  9:12:24 0 [Note] InnoDB: Waiting for purge to start

2024-03-14  9:12:24 0 [Note] InnoDB: 10.4.12 started; log sequence number 82292130377803; transaction id 384313048159

2024-03-14  9:12:24 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool

2024-03-14  9:12:24 0 [Note] Plugin 'FEEDBACK' is disabled.

240314  9:12:24 server_audit: INCL_DML_USERS and EXCL_DML_USERS specified simultaneously - both set to empty

240314  9:12:24 server_audit: server_audit_incl_users set to ''.

240314  9:12:24 server_audit: MariaDB Audit Plugin version 1.4.8 STARTED.

240314  9:12:24 server_audit: logging started to the file /var/log/mysql/mysql-audit-server.log.

2024-03-14  9:12:24 0 [Note] Recovering after a crash using /var/log/mysql/binlogs/server.log

2024-03-14  9:12:24 0 [Note] Starting crash recovery...

2024-03-14  9:12:24 0 [Note] InnoDB: Starting recovery for XA transactions...

2024-03-14  9:12:24 0 [Note] InnoDB: Transaction 384313048156 in prepared state after recovery

2024-03-14  9:12:24 0 [Note] InnoDB: Transaction contains changes to 1 rows

2024-03-14  9:12:24 0 [Note] InnoDB: Transaction 384313048155 in prepared state after recovery

2024-03-14  9:12:24 0 [Note] InnoDB: Transaction contains changes to 1 rows

2024-03-14  9:12:24 0 [Note] InnoDB: 2 transactions in prepared state after recovery

2024-03-14  9:12:24 0 [Note] Found 2 prepared transaction(s) in InnoDB

2024-03-14  9:12:24 0 [Note] Crash recovery finished.

2024-03-14  9:12:24 0 [Note] Server socket created on IP: '0.0.0.0'.

2024-03-14  9:12:24 7 [Note] Event Scheduler: scheduler thread started with id 7

2024-03-14  9:12:24 0 [Note] Reading of all Master_info entries succeeded

2024-03-14  9:12:24 0 [Note] Added new Master_info '' to hash table