Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
10.4.3, 10.4.4, 10.4.5, 10.4.6, 10.4.7, 10.4.8, 10.4.9, 10.4.10
-
None
-
Gentoo Linux
GCC x86_64-pc-linux-gnu-9.2.0
Linux Kernel 5.3.7
2 x Intel(R) Xeon(R) Gold 6134 CPU's
256GB RAM
Intel 1.6TB P3700 NVME SSD
also CentOS 7
Description
191119 10:57: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.4.10-MariaDB-log
|
key_buffer_size=2147483648
|
read_buffer_size=2097152
|
max_used_connections=884
|
max_threads=5002
|
thread_count=58
|
It is possible that mysqld could use up to
|
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 32945674 K bytes of memory
|
Hope that's ok; if not, decrease some variables in the equation.
|
|
Thread pointer: 0x7f04985d7678
|
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 = 0x7f054f05fe78 thread_stack 0x49000
|
/usr/sbin/mysqld(my_print_stacktrace+0x29)[0x556eb5baefd9]
|
/usr/sbin/mysqld(handle_fatal_signal+0x53d)[0x556eb56d5d0d]
|
/lib64/libpthread.so.0(+0x153a0)[0x7f383c0803a0]
|
/usr/sbin/mysqld(+0xa9577a)[0x556eb594e77a]
|
/usr/sbin/mysqld(+0xa95904)[0x556eb594e904]
|
/usr/sbin/mysqld(+0xa95fb5)[0x556eb594efb5]
|
/usr/sbin/mysqld(+0xa993c0)[0x556eb59523c0]
|
/usr/sbin/mysqld(+0x9c14fb)[0x556eb587a4fb]
|
/usr/sbin/mysqld(+0x68785a)[0x556eb554085a]
|
/usr/sbin/mysqld(_Z10sub_selectP4JOINP13st_join_tableb+0x173)[0x556eb5533b33]
|
/usr/sbin/mysqld(_ZN4JOIN10exec_innerEv+0xc34)[0x556eb555e044]
|
/usr/sbin/mysqld(_ZN4JOIN4execEv+0x2a)[0x556eb555e2ca]
|
/usr/sbin/mysqld(_Z12mysql_selectP3THDP10TABLE_LISTjR4ListI4ItemEPS4_jP8st_orderS9_S7_S9_yP13select_resultP18st_select_lex_unitP13st_select_lex+0x133)[0x556eb555c523]
|
/usr/sbin/mysqld(_Z13handle_selectP3THDP3LEXP13select_resultm+0x152)[0x556eb555cfd2]
|
/usr/sbin/mysqld(+0x63bd56)[0x556eb54f4d56]
|
/usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x15ca)[0x556eb54fdc5a]
|
/usr/sbin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_statebb+0x1b4)[0x556eb5503a44]
|
/usr/sbin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcjbb+0xe8a)[0x556eb550515a]
|
/usr/sbin/mysqld(_Z10do_commandP3THD+0xd9)[0x556eb5506d79]
|
/usr/sbin/mysqld(_Z24do_handle_one_connectionP7CONNECT+0x1bc)[0x556eb55e5abc]
|
/usr/sbin/mysqld(handle_one_connection+0x32)[0x556eb55e5bf2]
|
/lib64/libpthread.so.0(+0x83d7)[0x7f383c0733d7]
|
/lib64/libc.so.6(clone+0x3f)[0x7f383b88014f]
|
|
Trying to get some variables.
|
Some pointers may be invalid and cause the dump to abort.
|
Query (0x7f049812ee00): is an invalid pointer
|
Connection ID (thread ID): 49237686
|
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
|
|
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
|
information that should help you find out what is causing the crash.
|
|
We think the query pointer is invalid, but we will try to print it anyway.
|
Query: SELECT COUNT(*) AS numrows
|
FROM core_reviews
|
WHERE core_reviews.sitearea = '2'
|
AND core_reviews.siteareaid = '59106'
|
AND MATCH (core_reviews.summary) AGAINST ('eren,,,')
|
|
Writing a core file...
|
Working directory at /var/lib/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 1032474 1032474 processes
|
Max open files 70599 70599 files
|
Max locked memory 65536 65536 bytes
|
Max address space unlimited unlimited bytes
|
Max file locks unlimited unlimited locks
|
Max pending signals 1032474 1032474 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
|
Attachments
Issue Links
- duplicates
-
MDEV-21040 InnoDB: fulltext search with ` in(...)` crashed on specific combination
- Closed
Could you please get a stack trace from the coredump? It should be more meaningful than the crash report the server produces.
Please also paste the output of
and paste or attach your config file(s). Thanks.