maria-discuss team mailing list archive
-
maria-discuss team
-
Mailing list archive
-
Message #06545
mariadb crash und recovery
-
To:
maria-discuss@xxxxxxxxxxxxxxxxxxx
-
From:
Radisson97@xxxxxx
-
Date:
Mon, 17 Apr 2023 12:37:02 +0200
-
Importance:
normal
-
Sensitivity:
Normal
-
Ui-outboundreport:
notjunk:1;M01:P0:1MsBiTxVbEQ=;scUbXsZawctTiN4FBRrQv7/BqoH 651kuJjs+LPp+mc9596n7jo80o9EEmJUZQ5UhmFJzyqP90UEQx05I2KUfflJ+jXTsmsaIbGPv V05A23FFQ2Cp8WwGy9lh4qiD2IgCT52Xp0J9eGN+VVSEG7pr1Eoq4dpt7oza3or6OkLAkd87A A5Knk+dorVCwRYo+mngr+cTOKRkcZeGeWhFrrKgw6x2TI2VwgVVeFkh/QtMSumgpuX31B5XK1 BziygUY6ER/7GBDPIzb2QXGGuAut3uBCd6JcL6tcdKRqDwxnmY0tjCF7at30ExRuIjDOxHoox dGbe/HKWqM2gb+afYoOqDpDvAS+G7UC1oormuPD5vf87IwfbxKW+KOLdCVPMpDnoO+6G1F10Y GQfTlErd60bHj/DUgvrOnYlYqNL47yUZ2NBSsPYkrN0AzuBssI2ysSvpEw/HqI/DUzQvPXBTn CLDiDdlgqkjLU5ZZGz1cW5JBeSUrwAD0Yqw7QqrVYwbDAJclI9dHluYgpiRCSCxgrwmIXwmfU LC0tqDXGGDJbsYtnIGfkUkUjDCT0VopETUjKcwJ1MxtgbVxtV5SluP5x+FrjZPS/syxoNtWqV 5okMlgtnawUXI0qSRJwfFAjuAD6CAhRl1EyoO7M2DTWnVrWEmNdJbKdMeLzO56tHBs9Mflhco bW+Z7eaMjqV91T1pltQt0dPl580G5CqPz4jDU7tYztT5fYi4HHCRclG3DQ7BvPE+5QyCHvKOS OnBokrJ2819S9w+oi6BKkNKvIs37pQutAycPHiF5CuBgcORbil7fJCVB/zTZ0Mv3POQKg46/r 7ujKiZk79NIz0N/6gaNXQ2HQ==
Hello list,
i had a crash at weekend with no apparend cause.
The aria engine did a recovery without furture problems.
Maybe that is a hint that somebody can make use of.
Hints welcome.
CU
from log:
230416 7:20:17 [ERROR] mysqld got signal 11 ;
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.15-MariaDB-0+deb11u1-log
key_buffer_size=134217728
read_buffer_size=131072
max_used_connections=86
max_threads=252
thread_count=38
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 685818 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x7f01e4000c58
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 = 0x7f02b6894d38 thread_stack 0x49000
??:0(my_print_stacktrace)[0x5559d92bb54e]
??:0(handle_fatal_signal)[0x5559d8dbaf65]
sigaction.c:0(__restore_rt)[0x7f043591a140]
??:0(_ma_state_info_write)[0x5559d8fafc73]
??:0(_ma_state_info_write)[0x5559d8fb1737]
??:0(_ma_state_info_write)[0x5559d8fb946c]
??:0(handler::ha_write_row(unsigned char const*))[0x5559d8dc7aa8]
??:0(MyCTX_nopad::finish(unsigned char*, unsigned int*))[0x5559d8ff40da]
??:0(handler::ha_write_row(unsigned char const*))[0x5559d8dc7aa8]
??:0(write_record(THD*, TABLE*, st_copy_info*, select_result*))[0x5559d8b8787d]
??:0(mysql_insert(THD*, TABLE_LIST*, List<Item>&, List<List<Item> >&, List<Item>&, List<Item>&, enum_duplicates, bool, select
_result*))[0x5559d8b8f8a4]
??:0(mysql_execute_command(THD*))[0x5559d8bc2716]
??:0(mysql_parse(THD*, char*, unsigned int, Parser_state*, bool, bool))[0x5559d8bc65db]
??:0(dispatch_command(enum_server_command, THD*, char*, unsigned int, bool, bool))[0x5559d8bc8a5d]
??:0(do_command(THD*))[0x5559d8bca2de]
??:0(do_handle_one_connection(CONNECT*, bool))[0x5559d8cbbfb2]
??:0(handle_one_connection)[0x5559d8cbc22d]
??:0(MyCTX_nopad::finish(unsigned char*, unsigned int*))[0x5559d8ff811b]
nptl/pthread_create.c:478(start_thread)[0x7f043590eea7]
x86_64/clone.S:97(__GI___clone)[0x7f0435525def]
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0x7f01e4010440): INSERT INTO messwerte VALUES ( 83110995 , 1200 , 909 , 331 , '2023-04-16 05:20:00' , '2023-04-16 05:
20:00' , 0.0703000000000000013766765505351941101253032684326171875 , 0.001000000000000000020816681711721685132943093776702880
859375 , 0 , 0 , 0 , 0 , 60 , 0 )
Connection ID (thread ID): 5463672
Status: NOT_KILLED
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,index_condition_pushdown=on,derived_merge=on,derived_with_keys=on,firstmatch=o
n,loosescan=on,materialization=on,in_to_exists=on,semijoin=on,partial_match_rowid_merge=on,partial_match_table_scan=on,subque
ry_cache=on,mrr=off,mrr_cost_based=off,mrr_sort_keys=off,outer_join_with_cache=on,semijoin_with_cache=on,join_cache_increment
al=on,join_cache_hashed=on,join_cache_bka=on,optimize_join_buffer_size=on,table_elimination=on,extended_keys=on,exists_to_in=
on,orderby_uses_equalities=on,condition_pushdown_for_derived=on,split_materialized=on,condition_pushdown_for_subquery=on,rowi
d_filter=on,condition_pushdown_from_having=on,not_null_range_scan=off
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 127976 127976 processes
Max open files 32313 32313 files
Max locked memory 65536 65536 bytes
Max address space unlimited unlimited bytes
Max file locks unlimited unlimited locks
Max pending signals 127976 127976 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
230416 07:20:19 mysqld_safe Number of processes running now: 0
230416 07:20:19 mysqld_safe mysqld restarted
2023-04-16 7:20:19 0 [Note] /usr/sbin/mariadbd (mysqld 10.5.15-MariaDB-0+deb11u1-log) starting as process 415 ...
2023-04-16 7:20:20 0 [Note] mariadbd: Aria engine: starting recovery
recovered pages: 0% 10% 20% 30% 40% 50% 60% 70% 80% 90% 100% (0.0 seconds); tables to flush: 22 21 20 19 18 17 16 15 14 13 12
11 10 9 8 7 6 5 4 3 2 1 0
(0.1 seconds);
2023-04-16 7:20:20 0 [Note] mariadbd: Aria engine: recovery done
Follow ups