maria-discuss team mailing list archive
-
maria-discuss team
-
Mailing list archive
-
Message #06571
FYI:10.5.15-MariaDB crash und recover
-
To:
maria-discuss@xxxxxxxxxxxxxxxxxxx
-
From:
Radisson97@xxxxxx
-
Date:
Thu, 1 Jun 2023 10:44:19 +0200
-
Importance:
normal
-
Sensitivity:
Normal
-
Ui-outboundreport:
notjunk:1;M01:P0:bGY6HpIS5QU=;AUBTqxs7Vu/bXY9P2nYPfx5YQ4i J5KAlfpI79kDJTskso+ZwpaQY4z0KmCiigi6Ij2zF2/Z5BXFPaSEn2HrH69y9t9sEQxK1/h6w UbolQVJ5myyzy4g0Vim+q/6skjHkYFt4+jiDJj+hlxy1M333+hv25Q6cr95DlsC/x05CaKSkY l7aypt+jQnfIAN44D00w8u4e0OHsuCjaFKWz6q+oQ2kehZl7KH7NkPaKa/Fu6EjB6sgaFPLvP 4P3DaexTRIrkD9WnIVTImdfnPb3iH7ARb6zml5yeOs9YQ9YKz/8Zi4ix5N2CSpnTta6SvWAXE Wwcs1d0B6rdVAPf47jM+S+mRubdmDA+gNHZ2DdS2EAsRhT/8ZFW5sG1DY3/XbdlNNqUeRJQXD rRg193j2JpI5ZNIg0yOjxNmjYeKokP2MGZ4AsqCIiWaTtwcaMtidemD8ebRqPdKkA7jyXwFiZ UrLHLeGbEk8KoiYesQ0EsxHhyp5308G0lb6cUuoe6NwRUE6uqTZDjRBqNPfDomc75r4KMGpo6 gawe4im5T//u7dVLyXF16J6CG7LqwJbnb+Ncz6tguXcdEMYkkO/f63MMdU/VhQE5+YV2lG+J7 3hDhvHrSjAQpSpiJfI7Tgr5cGc8gGkrOJujrYaTDHUUH2XNLgGZXiQPiEAC62dd563I/aXQKn OThOPWZ0GTEEQrCiBoFrdn/X3Fy0ORpRrmEkdMfzg/YWKaoYa7bipMiYMf4Sibqk2tk1bRnOI HhKmXJCOzwiqHZsBXXqsH3xY4hp3SjqbpgsPilfdg/+6o33EKBZnO1wM7RtYJ10p05ggEuQ3I MgL+qa+VxyLyj2g8h3/H4ukw==
Hello I had a crash today,
there was no problem with the hardware. Maybe someone is interessted
or find some useful information. It is a production machine so no core file.
have fun.
btw: Linux 5.10.0-17-amd64 #1 SMP Debian 5.10.136-1
== mariadb.log ==
230601 8:22:09 [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=11
max_threads=252
thread_count=11
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: 0x7faf440061d8
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 = 0x7fafa439bd38 thread_stack 0x49000
??:0(my_print_stacktrace)[0x55ebc2f0954e]
??:0(handle_fatal_signal)[0x55ebc2a08f65]
sigaction.c:0(__restore_rt)[0x7fb11f670140]
??:0(_ma_state_info_write)[0x55ebc2bfdc73]
??:0(_ma_state_info_write)[0x55ebc2bff737]
??:0(_ma_state_info_write)[0x55ebc2c0746c]
??:0(handler::ha_write_row(unsigned char const*))[0x55ebc2a15aa8]
??:0(MyCTX_nopad::finish(unsigned char*, unsigned int*))[0x55ebc2c420da]
??:0(handler::ha_write_row(unsigned char const*))[0x55ebc2a15aa8]
??:0(write_record(THD*, TABLE*, st_copy_info*, select_result*))[0x55ebc27d587d]
??:0(mysql_insert(THD*, TABLE_LIST*, List<Item>&, List<List<Item> >&, List<Item>&, List<Item>&, enum_duplicates, bool, select_result*))[0x55ebc
27dd8a4]
??:0(mysql_execute_command(THD*))[0x55ebc2810716]
??:0(mysql_parse(THD*, char*, unsigned int, Parser_state*, bool, bool))[0x55ebc28145db]
??:0(dispatch_command(enum_server_command, THD*, char*, unsigned int, bool, bool))[0x55ebc2816a5d]
??:0(do_command(THD*))[0x55ebc28182de]
??:0(do_handle_one_connection(CONNECT*, bool))[0x55ebc2909fb2]
??:0(handle_one_connection)[0x55ebc290a22d]
??:0(MyCTX_nopad::finish(unsigned char*, unsigned int*))[0x55ebc2c4611b]
nptl/pthread_create.c:478(start_thread)[0x7fb11f664ea7]
x86_64/clone.S:97(__GI___clone)[0x7fb11f27bdef]
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0x7faf44014860): INSERT INTO wetter_daten VALUES ( 190600010 , '2023-06-01 06:00:00' , 0 , 0 )
Connection ID (thread ID): 5569194
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,e
ngine_condition_pushdown=off,index_condition_pushdown=on,derived_merge=on,derived_with_keys=on,firstmatch=on,loosescan=on,materialization=on,in
_to_exists=on,semijoin=on,partial_match_rowid_merge=on,partial_match_table_scan=on,subquery_cache=on,mrr=off,mrr_cost_based=off,mrr_sort_keys=o
ff,outer_join_with_cache=on,semijoin_with_cache=on,join_cache_incremental=on,join_cache_hashed=on,join_cache_bka=on,optimize_join_buffer_size=o
n,table_elimination=on,extended_keys=on,exists_to_in=on,orderby_uses_equalities=on,condition_pushdown_for_derived=on,split_materialized=on,cond
ition_pushdown_for_subquery=on,rowid_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 127967 127967 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 127967 127967 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
230601 08:22:10 mysqld_safe Number of processes running now: 0
230601 08:22:10 mysqld_safe mysqld restarted
2023-06-01 8:22:11 0 [Note] /usr/sbin/mariadbd (mysqld 10.5.15-MariaDB-0+deb11u1-log) starting as process 24005 ...
2023-06-01 8:22:11 0 [Note] mariadbd: Aria engine: starting recovery
recovered pages: 0% 10% 20% 30% 40% 50% 60% 70% 80% 90% 100% (0.1 seconds); tables to flush: 62 61 60 59 58 57 56 55 54 53 52 51 50 49 48 47 46
45 44 43 42 41 40 39 38 37 36 35 34 33 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
(0.4 seconds);
2023-06-01 8:22:11 0 [Note] mariadbd: Aria engine: recovery done
2023-06-01 8:22:11 0 [Note] InnoDB: Uses event mutexes
2023-06-01 8:22:11 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2023-06-01 8:22:11 0 [Note] InnoDB: Number of pools: 1
2023-06-01 8:22:11 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions
2023-06-01 8:22:11 0 [Note] InnoDB: Using Linux native AIO
2023-06-01 8:22:11 0 [Note] InnoDB: Initializing buffer pool, total size = 5368709120, chunk size = 134217728
2023-06-01 8:22:11 0 [Note] InnoDB: Completed initialization of buffer pool
2023-06-01 8:22:11 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=463015889782,463015889782
2023-06-01 8:22:13 0 [Note] InnoDB: Starting final batch to recover 2019 pages from redo log.
2023-06-01 8:22:15 0 [Note] InnoDB: 128 rollback segments are active.
2023-06-01 8:22:15 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
2023-06-01 8:22:15 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2023-06-01 8:22:15 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2023-06-01 8:22:15 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
2023-06-01 8:22:15 0 [Note] InnoDB: 10.5.15 started; log sequence number 463033688604; transaction id 19549881
2023-06-01 8:22:15 0 [Note] InnoDB: Loading buffer pool(s) from /home/kpc/kpc.dbs/ib_buffer_pool
2023-06-01 8:22:15 0 [Note] Plugin 'FEEDBACK' is disabled.
2023-06-01 8:22:15 0 [Note] Server socket created on IP: '::'.
2023-06-01 8:22:16 0 [Note] Reading of all Master_info entries succeeded
2023-06-01 8:22:16 0 [Note] Added new Master_info '' to hash table
2023-06-01 8:22:16 0 [Note] /usr/sbin/mariadbd: ready for connections.
Version: '10.5.15-MariaDB-0+deb11u1-log' socket: '/run/mysqld/mysqld.sock' port: 3306 Debian 11
2023-06-01 8:22:18 0 [Note] InnoDB: Buffer pool(s) load completed at 230601 8:22:18
Follow ups