Details
-
Bug
-
Status: Closed (View Workflow)
-
Critical
-
Resolution: Fixed
-
10.5.5, 10.5.6, 10.11.3, 10.6.12, 10.6.16, 10.11.6
-
Centos 7.8.2003
Description
See below error dump, happens sporadically (every 2 to 3 weeks) resulting in dropping of all connections and evacuation of cache taking around 20 seconds to recover. In each case it is a random simple select that causes the issue. All tables are innodb and have been mysqlcheck'd with no issue found. Issue did not occur under 10.4 but coincided with move to 10.5.5. System is not under excessive load at the time the problems manifests. Recent upgrade to 10.5.6 has not resolved the issue
IMPORTANT : Knock on effect for replication slaves is duplicate records causing replication to fail - so this effectively looks like two bugs (duplicate updates can be skipped). I believe the assertion failure handling may be causing this secondary serious issue :
1) assertion failure on master host
2) replication failure on slave host
2020-10-21 14:47:03 0x7f45b0c42700 InnoDB: Assertion failure in file /home/buildbot/buildbot/padding_for_CPACK_RPM_BUILD_SOURCE_DIRS_PREFIX/mariadb-10.5.5/storage/innobase/trx/trx0trx.cc line 1329
|
InnoDB: Failing assertion: UT_LIST_GET_LEN(lock.trx_locks) == 0
|
InnoDB: We intentionally generate a memory trap.
|
InnoDB: Submit a detailed bug report to https://jira.mariadb.org/
|
InnoDB: If you get repeated assertion failures or crashes, even
|
InnoDB: immediately after the mysqld startup, there may be
|
InnoDB: corruption in the InnoDB tablespace. Please refer to
|
InnoDB: https://mariadb.com/kb/en/library/innodb-recovery-modes/
|
InnoDB: about forcing recovery.
|
201021 14:47:03 [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.5-MariaDB-log
|
key_buffer_size=67108864
|
read_buffer_size=1048576
|
max_used_connections=1137
|
max_threads=1252
|
thread_count=486
|
It is possible that mysqld could use up to
|
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 2660907 K bytes of memory
|
Hope that's ok; if not, decrease some variables in the equation.
|
|
|
Thread pointer: 0x7f43a0064958
|
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 = 0x7f45b0c41c90 thread_stack 0x49000
|
Can't start addr2line
|
/usr/sbin/mariadbd(my_print_stacktrace+0x2e)[0x556585139f3e]
|
/usr/sbin/mariadbd(handle_fatal_signal+0x307)[0x556584b3c607]
|
/lib64/libpthread.so.0(+0xf630)[0x7f7d8a62e630]
|
/lib64/libc.so.6(gsignal+0x37)[0x7f7d88688387]
|
/lib64/libc.so.6(abort+0x148)[0x7f7d88689a78]
|
/usr/sbin/mariadbd(+0x64c5e7)[0x55658481a5e7]
|
/usr/sbin/mariadbd(+0xda9197)[0x556584f77197]
|
/usr/sbin/mariadbd(+0xda92c3)[0x556584f772c3]
|
/usr/sbin/mariadbd(+0xda95a4)[0x556584f775a4]
|
/usr/sbin/mariadbd(+0xc4b6cc)[0x556584e196cc]
|
/usr/sbin/mariadbd(+0xc56723)[0x556584e24723]
|
/usr/sbin/mariadbd(_ZN7handler16ha_external_lockEP3THDi+0x261)[0x556584b48681]
|
/usr/sbin/mariadbd(+0xa6ae7a)[0x556584c38e7a]
|
/usr/sbin/mariadbd(_Z24mysql_unlock_read_tablesP3THDP13st_mysql_lock+0x72)[0x556584c39702]
|
/usr/sbin/mariadbd(_ZN4JOIN9join_freeEv+0x169)[0x556584976cb9]
|
/usr/sbin/mariadbd(_ZN4JOIN10exec_innerEv+0xc6c)[0x55658499b55c]
|
/usr/sbin/mariadbd(_ZN4JOIN4execEv+0x33)[0x55658499b813]
|
/usr/sbin/mariadbd(_Z12mysql_selectP3THDP10TABLE_LISTR4ListI4ItemEPS4_jP8st_orderS9_S7_S9_yP13select_resultP18st_select_lex_unitP13st_select_lex+0x186)[0x5565849999d6]
|
/usr/sbin/mariadbd(_Z13handle_selectP3THDP3LEXP13select_resultm+0x1cc)[0x55658499a53c]
|
/usr/sbin/mariadbd(+0x63343a)[0x55658480143a]
|
/usr/sbin/mariadbd(_Z21mysql_execute_commandP3THD+0x37f5)[0x556584940605]
|
/usr/sbin/mariadbd(_Z11mysql_parseP3THDPcjP12Parser_statebb+0x36a)[0x55658494350a]
|
/usr/sbin/mariadbd(_Z16dispatch_command19enum_server_commandP3THDPcjbb+0x1bbd)[0x55658494587d]
|
/usr/sbin/mariadbd(_Z10do_commandP3THD+0x10b)[0x55658494701b]
|
/usr/sbin/mariadbd(_Z24do_handle_one_connectionP7CONNECTb+0x1b2)[0x556584a2fb32]
|
/usr/sbin/mariadbd(handle_one_connection+0x34)[0x556584a2fde4]
|
/usr/sbin/mariadbd(+0xbb62ad)[0x556584d842ad]
|
/lib64/libpthread.so.0(+0x7ea5)[0x7f7d8a626ea5]
|
/lib64/libc.so.6(clone+0x6d)[0x7f7d887508dd]
|
|
|
Trying to get some variables.
|
Some pointers may be invalid and cause the dump to abort.
|
Query (0x7f43a0074710): SELECT * FROM `lookup_permissions_grid` WHERE `application` IN ('guest')
|
Connection ID (thread ID): 187768692
|
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 /mnt/db/mysql
|
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 1030944 1030944 processes
|
Max open files 16384 16384 files
|
Max locked memory 65536 65536 bytes
|
Max address space unlimited unlimited bytes
|
Max file locks unlimited unlimited locks
|
Max pending signals 1030944 1030944 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
|
|
|
2020-10-21 14:47:27 0 [Note] mariadbd: Aria engine: starting recovery
|
tables to flush: 2 1 0
|
(0.0 seconds);
|
2020-10-21 14:47:27 0 [Note] mariadbd: Aria engine: recovery done
|
mysqld --print-defaults
mysqld would have been started with the following arguments:
--datadir=/mnt/db/mysql --tmpdir=/var/lib/mysqltmp --sql-mode=STRICT_TRANS_TABLES,NO_ENGINE_SUBSTITUTION --userstat=1 --log_warnings=2 --thread_handling=one-thread-per-connection --thread-cache-size=16 --table-open-cache=4096 --table-definition-cache=2048 --query-cache-type=0 --sort-buffer-size=1M --read-buffer-size=1M --read-rnd-buffer-size=1M --join-buffer-size=1M --tmp-table-size=128M --max-heap-table-size=128M --back-log=100 --max-connections=1250 --max-connect-errors=10000 --max-allowed-packet=16M --interactive-timeout=28800 --wait-timeout=28800 --default-storage-engine=InnoDB --innodb=FORCE --key-buffer-size=64M --myisam-sort-buffer-size=128M --innodb-buffer-pool-size=224256M --innodb-log-file-size=100M --innodb-file-per-table=1 --innodb-open-files=4096 --innodb_flush_log_at_trx_commit=0 --innodb_buffer_pool_instances=16 --innodb_flush_method=O_DIRECT --log-output=FILE --slow-query-log=1 --slow-query-log-file=/mnt/db/mysql_slow.log --long-query-time=1 --character-set-server=utf8 --group_concat_max_len=40960 --log-error=/mnt/db/mysqld.log --open-files-limit=65535 --server-id=1 --gtid-domain-id=1 --log-bin=/mnt/db/mysqllogs/bin-log --relay-log-space-limit=16G --expire-logs-days=2 --sync-binlog=0 --innodb_io_capacity=2000 --innodb_thread_concurrency=0
|
Attachments
Issue Links
- duplicates
-
-
- Closed
-
- is blocked by
-
-
- Closed
-
- is duplicated by
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
MDEV-31259 mariadb server crash dump
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
- relates to
-
-
- Closed
-
-
-
- Closed
-
-
-
- Open
-
-
-
- Open
-
-
-
- Closed
-
-
-
- Confirmed
-
-
-
- Confirmed
-
-
-
- Closed
-
-
-
- Closed
-
- mentioned in
-
Page Loading...