Server version: 10.3.31-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 = 467364 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
2021-10-17 8:04:19 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
2021-10-17 8:04:19 0 [Note] InnoDB: Waiting for purge to start
2021-10-17 8:04:19 0 [Note] InnoDB: 10.3.31 started; log sequence number 171595881596; transaction id 310689378
2021-10-17 8:04:19 0 [Note] InnoDB: Loading buffer pool(s) from /home/mysql/ib_buffer_pool
2021-10-17 8:04:19 0 [Note] Plugin 'FEEDBACK' is disabled.
2021-10-17 8:04:19 0 [Note] Recovering after a crash using tc.log
2021-10-17 8:04:19 0 [Note] Starting crash recovery...
2021-10-17 8:04:19 0 [Note] Crash recovery finished.
2021-10-17 8:04:19 0 [Note] Server socket created on IP: '::'.
2021-10-17 8:04:19 0 [Note] Reading of all Master_info entries succeeded
2021-10-17 8:04:19 0 [Note] Added new Master_info '' to hash table
2021-10-17 8:04:19 0 [Note] /usr/local/mysql/bin/mysqld: ready for connections.
Version: '10.3.31-MariaDB' socket: '/tmp/mysql.sock' port: 3306 Source distribution
2021-10-17 8:04:19 0 [Note] InnoDB: Buffer pool(s) load completed at 211017 8:04:19
0x114f04e <my_print_stacktrace+0x2e> at /usr/local/mysql/bin/mysqld
0xb47575 <handle_fatal_signal+0x295> at /usr/local/mysql/bin/mysqld
0x801773b70 <_pthread_sigmask+0x530> at /lib/libthr.so.3
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.
Core pattern: %N.core
2021-10-17 8:04:20 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2021-10-17 8:04:20 0 [Note] InnoDB: Uses event mutexes
2021-10-17 8:04:20 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2021-10-17 8:04:20 0 [Note] InnoDB: Number of pools: 1
2021-10-17 8:04:20 0 [Note] InnoDB: Using SSE2 crc32 instructions
2021-10-17 8:04:20 0 [Note] InnoDB: Initializing buffer pool, total size = 512M, instances = 1, chunk size = 128M
2021-10-17 8:04:20 0 [Note] InnoDB: Completed initialization of buffer pool
2021-10-17 8:04:20 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=171588556686
2021-10-17 8:04:20 0 [Note] InnoDB: 1 transaction(s) which must be rolled back or cleaned up in total 1 row operations to undo
2021-10-17 8:04:20 0 [Note] InnoDB: Trx id counter is 310689377
2021-10-17 8:04:20 0 [Note] InnoDB: Starting final batch to recover 410 pages from redo log.
2021-10-17 8:04:21 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2021-10-17 8:04:21 0 [Note] InnoDB: Starting in background the rollback of recovered transactions
211017 8:04:21 [ERROR] mysqld got signal 10 ;
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.
