MariaDB does not start

My MariaDB does not start and it seems because of a problem with InnoDB recovery

The Log says:

024-10-23 15:26:46 0 [Note] Starting MariaDB 10.5.25-MariaDB-log source revision 29c185bd771ac441121468b3850d6dc8d13b8a1f as process 15106 2024-10-23 15:26:46 0 [Note] InnoDB: Uses event mutexes 2024-10-23 15:26:46 0 [Note] InnoDB: Compressed tables use zlib 1.2.7 2024-10-23 15:26:46 0 [Note] InnoDB: Number of pools: 1 2024-10-23 15:26:46 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions 2024-10-23 15:26:46 0 [Note] InnoDB: Using Linux native AIO 2024-10-23 15:26:46 0 [Note] InnoDB: Initializing buffer pool, total size = 134217728, chunk size = 134217728 2024-10-23 15:26:46 0 [Note] InnoDB: Completed initialization of buffer pool 2024-10-23 15:26:46 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=512991862361,512991862361 2024-10-23 15:26:46 0 [Note] InnoDB: 1 transaction(s) which must be rolled back or cleaned up in total 1 row operations to undo 2024-10-23 15:26:46 0 [Note] InnoDB: Trx id counter is 472065695 2024-10-23 15:26:46 0 [Note] InnoDB: Starting final batch to recover 4 pages from redo log. 2024-10-23 15:26:46 0 [Note] InnoDB: 128 rollback segments are active. 2024-10-23 15:26:46 0 [Note] InnoDB: Starting in background the rollback of recovered transactions 2024-10-23 15:26:46 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1" 2024-10-23 15:26:46 0 [Note] InnoDB: Creating shared tablespace for temporary tables 2024-10-23 15:26:46 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ... 2024-10-23 15:26:46 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB. 241023 15:26:46 [ERROR] mysqld got signal 11 ; 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.25-MariaDB-log source revision: 29c185bd771ac441121468b3850d6dc8d13b8a1f key_buffer_size=134217728 read_buffer_size=131072 max_used_connections=0 max_threads=3602 thread_count=0 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 8061271 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 2024-10-23 15:26:46 0 [Note] InnoDB: 10.5.25 started; log sequence number 512991877461; transaction id 472065696 2024-10-23 15:26:46 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool 2024-10-23 15:26:46 0 [Note] Plugin 'FEEDBACK' is disabled. /usr/sbin/mariadbd(my_print_stacktrace+0x2e)[0x55b244ab888e] 2024-10-23 15:26:46 0 [Note] Server socket created on IP: '::'. /usr/sbin/mariadbd(handle_fatal_signal+0x2f7)[0x55b2444c4b57] 2024-10-23 15:26:46 0 [Warning] 'user' entry '[email protected]' ignored in --skip-name-resolve mode. 2024-10-23 15:26:46 0 [Warning] 'proxies_priv' entry '@% [email protected]' ignored in --skip-name-resolve mode. sigaction.c:0(restore_rt)[0x7fc2bab16630] 2024-10-23 15:26:46 0 [Note] Reading of all Master_info entries succeeded 2024-10-23 15:26:46 0 [Note] Added new Master_info '' to hash table 2024-10-23 15:26:46 0 [Note] /usr/sbin/mariadbd: ready for connections. Version: '10.5.25-MariaDB-log' socket: '/var/lib/mysql/mysql.sock' port: 3306 MariaDB Server /usr/sbin/mariadbd(+0xd349a8)[0x55b24481e9a8] /usr/sbin/mariadbd(+0xe499c9)[0x55b2449339c9] /usr/sbin/mariadbd(+0xdb2a12)[0x55b24489ca12] /usr/sbin/mariadbd(+0xdb2b83)[0x55b24489cb83] /usr/sbin/mariadbd(+0xf485c8)[0x55b244a325c8] /usr/sbin/mariadbd(+0xf48efb)[0x55b244a32efb] /usr/sbin/mariadbd(+0xdbdc20)[0x55b2448a7c20] /usr/sbin/mariadbd(+0xd6257b)[0x55b24484c57b] /usr/sbin/mariadbd(+0xdfb106)[0x55b2448e5106] /usr/sbin/mariadbd(+0xdfd4c2)[0x55b2448e74c2] /usr/sbin/mariadbd(+0xdfd837)[0x55b2448e7837] 2024-10-23 15:26:46 0 [Note] InnoDB: Buffer pool(s) load completed at 241023 15:26:46 pthread_create.c:0(start_thread)[0x7fc2bab0eea5] /lib64/libc.so.6(clone+0x6d)[0x7fc2ba029b0d] 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 /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 0 unlimited bytes Max resident set unlimited unlimited bytes Max processes 127797 127797 processes Max open files 500000 500000 files Max locked memory 65536 65536 bytes Max address space unlimited unlimited bytes Max file locks unlimited unlimited locks Max pending signals 127797 127797 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