[MDEV-26268] RDS 10.5.9 crashes signal 11 consistently upon SELECT query Created: 2021-07-28  Updated: 2021-08-30  Resolved: 2021-08-30

Status: Closed
Project: MariaDB Server
Component/s: Server
Affects Version/s: 10.5.9
Fix Version/s: N/A

Type: Bug Priority: Major
Reporter: Cyril Bouteille Assignee: Unassigned
Resolution: Incomplete Votes: 1
Labels: crash, need_feedback, select
Environment:

AWS RDS



 Description   

AWS RDS MariaDB 10.5.9 crashes with signal 11 consistently upon SELECT query below.

Rebooting and increasing memory does not help. Any ideas?

210728 22:04:30 [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.9-MariaDB-log
key_buffer_size=16777216
read_buffer_size=262144
max_used_connections=31
max_threads=75
thread_count=32
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 190955 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x2b01e326e098
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 = 0x2b01ddcc2578 thread_stack 0x40000
/rdsdbbin/mysql/bin/mysqld(my_print_stacktrace+0x2e)[0x5622f39a7b2e]
Printing to addr2line failed
/rdsdbbin/mysql/bin/mysqld(handle_fatal_signal+0x545)[0x5622f3302be5]
/lib64/libpthread.so.0(+0xf100)[0x2b018bffb100]
/rdsdbbin/mysql/bin/mysqld(+0xe9efef)[0x5622f377cfef]
/rdsdbbin/mysql/bin/mysqld(+0x72c63d)[0x5622f300a63d]
/rdsdbbin/mysql/bin/mysqld(+0x72c8f1)[0x5622f300a8f1]
/rdsdbbin/mysql/bin/mysqld(+0xea406e)[0x5622f378206e]
/rdsdbbin/mysql/bin/mysqld(+0xdbd1c1)[0x5622f369b1c1]
/rdsdbbin/mysql/bin/mysqld(_ZN7handler17ha_index_read_mapEPhPKhm16ha_rkey_function+0x268)[0x5622f3307e08]
/rdsdbbin/mysql/bin/mysqld(+0x875568)[0x5622f3153568]
/rdsdbbin/mysql/bin/mysqld(_Z10sub_selectP4JOINP13st_join_tableb+0x187)[0x5622f31463b7]
/rdsdbbin/mysql/bin/mysqld(_ZN4JOIN10exec_innerEv+0xa4e)[0x5622f3167e6e]
/rdsdbbin/mysql/bin/mysqld(_ZN4JOIN4execEv+0x30)[0x5622f31682a0]
/rdsdbbin/mysql/bin/mysqld(_Z12mysql_selectP3THDP10TABLE_LISTR4ListI4ItemEPS4_jP8st_orderS9_S7_S9_yP13select_resultP18st_select_lex_unitP13st_select_lex+0xf8)[0x5622f31665b8]
/rdsdbbin/mysql/bin/mysqld(_Z13handle_selectP3THDP3LEXP13select_resultm+0x141)[0x5622f3166f71]
/rdsdbbin/mysql/bin/mysqld(+0x82eba1)[0x5622f310cba1]
/rdsdbbin/mysql/bin/mysqld(_Z21mysql_execute_commandP3THD+0x103b)[0x5622f31095fb]
/rdsdbbin/mysql/bin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_statebb+0x1cc)[0x5622f310f5ec]
/rdsdbbin/mysql/bin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcjbb+0x13f3)[0x5622f3106393]
/rdsdbbin/mysql/bin/mysqld(_Z10do_commandP3THD+0xdd)[0x5622f3104d4d]
/rdsdbbin/mysql/bin/mysqld(_Z24do_handle_one_connectionP7CONNECTb+0x4c1)[0x5622f31fa081]
/rdsdbbin/mysql/bin/mysqld(handle_one_connection+0x34)[0x5622f31fa3f4]
/rdsdbbin/mysql/bin/mysqld(+0xd2d2cc)[0x5622f360b2cc]
/lib64/libpthread.so.0(+0x7dc5)[0x2b018bff3dc5]
/lib64/libc.so.6(clone+0x6d)[0x2b018c2fec9d]
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0x2b01e3290f70): SELECT * FROM wines LEFT OUTER JOIN appellations AS appellations_1 ON appellations_1.id = wines.appellation_id LEFT OUTER JOIN wine_classifications AS wine_classifications_1 ON wine_classifications_1.id = wines.classification_id LEFT OUTER JOIN wine_locales AS wine_locales_1 ON wine_locales_1.id = wines.origin_locale_id LEFT OUTER JOIN countries AS countries_1 ON countries_1.iso = wine_locales_1.country_code LEFT OUTER JOIN producers AS producers_1 ON producers_1.id = wines.producer_id LEFT OUTER JOIN vineyards AS vineyards_1 ON vineyards_1.id = wines.vineyard_id LEFT OUTER JOIN wine_varietals AS wine_varietals_1 ON wine_varietals_1.id = wines.varietal_id WHERE wines.producer_id = 69665 AND wines.designation = '' AND wines.appellation_id = 2074 AND wines.vineyard_id IS NULL AND wines.classification_id IS NULL AND wines.id != 432120
Connection ID (thread ID): 66
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=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=off,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=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,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 /rdsdbdata/db
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 unlimited unlimited bytes
Max core file size 0 unlimited bytes
Max resident set unlimited unlimited bytes
Max processes unlimited unlimited processes
Max open files 65535 65535 files
Max locked memory 65536 65536 bytes
Max address space unlimited unlimited bytes
Max file locks unlimited unlimited locks
Max pending signals 7784 7784 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: /rdsdbdata/tmp/core-%e-%p



 Comments   
Comment by Alice Sherepa [ 2021-07-29 ]

Could you please try the latest 10.5 release (10.5.11) and see if the problem goes away?

Generated at Thu Feb 08 09:44:01 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.