231021 11:28:02 mysqld_safe Starting mariadbd daemon with databases from /var/lib/mysql
|
2023-10-21 11:28:02 0 [Note] /usr/sbin/mariadbd (mysqld 10.5.18-MariaDB-0+deb11u1-log) starting as process 19639 ...
|
2023-10-21 11:28:02 0 [ERROR] mariadbd: File '/var/lib/mysql/aria_log.00002957' not found (Errcode: 2 "No such file or directory")
|
free(): invalid pointer
|
231021 11:28:02 [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.5.18-MariaDB-0+deb11u1-log
|
key_buffer_size=134217728
|
read_buffer_size=131072
|
max_used_connections=0
|
max_threads=252
|
thread_count=0
|
It is possible that mysqld could use up to
|
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 685832 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
|
??:0(my_print_stacktrace)[0x55a48dfe65de]
|
??:0(handle_fatal_signal)[0x55a48dae2635]
|
sigaction.c:0(__restore_rt)[0x7f0786c29140]
|
linux/raise.c:51(__GI_raise)[0x7f0786352ce1]
|
stdlib/abort.c:81(__GI_abort)[0x7f078633c537]
|
posix/libc_fatal.c:156(__libc_message)[0x7f0786395768]
|
malloc/malloc.c:5348(malloc_printerr)[0x7f078639ca5a]
|
malloc/malloc.c:4173(_int_free)[0x7f078639dc14]
|
??:0(ha_maria::max_supported_key_part_length() const)[0x55a48dcae204]
|
??:0(ha_maria::multi_range_read_explain_info(unsigned int, char*, unsigned long))[0x55a48dc9a25d]
|
??:0(ha_initialize_handlerton(st_plugin_int*))[0x55a48dae56ae]
|
??:0(sys_var_pluginvar::sys_var_pluginvar(sys_var_chain*, char const*, st_plugin_int*, st_mysql_sys_var*, char const*))[0x55a48d8f78da]
|
??:0(plugin_init(int*, char**, int))[0x55a48d8f89c7]
|
??:0(unireg_abort)[0x55a48d820a07]
|
??:0(mysqld_main(int, char**))[0x55a48d8267f4]
|
csu/libc-start.c:308(__libc_start_main)[0x7f078633dd0a]
|
??:0(_start)[0x55a48d81b6da]
|
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.
|
Writing a core file...
|
Working directory at /home/kpc/kpc.dbs
|
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 127944 127944 processes
|
Max open files 32313 32313 files
|
Max locked memory 8388608 8388608 bytes
|
Max address space unlimited unlimited bytes
|
Max file locks unlimited unlimited locks
|
Max pending signals 127944 127944 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.11-x64v3-xanmod1 (root@mascote) (gcc-12 (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #0~20230210.d26e42a SMP PREEMPT_DYNAMIC Fri Feb 10 01:19:20 UTC
|
|
231021 11:28:02 mysqld_safe mysqld from pid file /var/lib/mysql/omnfr103.pid ended
|