Details
-
Bug
-
Status: Closed (View Workflow)
-
Critical
-
Resolution: Fixed
-
10.1.10, 10.1.20, 10.1.23, 10.2(EOL)
-
10.1.19, 10.1.22, 10.2.6-2, 10.2.6-3, 10.3.1-2, 10.2.10, 10.1.29, 10.2.11
Description
A user saw this crash in MariaDB 10.1.10 on Ubuntu:
160201 21:22:07 [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 http://kb.askmonty.org/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.1.10-MariaDB-1~trusty-log
|
key_buffer_size=134217728
|
read_buffer_size=2097152
|
max_used_connections=30
|
max_threads=102
|
thread_count=15
|
It is possible that mysqld could use up to
|
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 759823 K bytes of memory
|
Hope that's ok; if not, decrease some variables in the equation.
|
|
Thread pointer: 0x0x7f1818883008
|
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 = 0x7f182b2dce10 thread_stack 0x48000
|
/usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x7f182acf3a6e]
|
/usr/sbin/mysqld(handle_fatal_signal+0x38d)[0x7f182a82216d]
|
/lib/x86_64-linux-gnu/libpthread.so.0(+0x10340)[0x7f1828d7c340]
|
/usr/sbin/mysqld(_ZN13MYSQL_BIN_LOG13mark_xid_doneEmb+0xc7)[0x7f182a8e2cb7]
|
/usr/sbin/mysqld(binlog_background_thread+0x2b5)[0x7f182a8e3275]
|
/lib/x86_64-linux-gnu/libpthread.so.0(+0x8182)[0x7f1828d74182]
|
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7f182849747d]
|
|
Trying to get some variables.
|
Some pointers may be invalid and cause the dump to abort.
|
Query (0x0): is an invalid pointer
|
Connection ID (thread ID): 3
|
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=off,table_elimination=on,extended_keys=on,exists_to_in=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.
|
I will try to get more information.
Attachments
Issue Links
- duplicates
-
MDEV-14395 171114 7:17:09 [ERROR] mysqld got signal 11
- Closed
- is duplicated by
-
MDEV-9901 Mariadb crashes
- Closed
-
MDEV-13058 MariaDB crashing
- Closed
-
MDEV-14521 [ERROR] mysqld got signal 11
- Closed
-
MDEV-15307 MariaDB 10.1 crashing on binlog switch to new file
- Closed
- is part of
-
MDEV-9960 Binary log not rotating
- Closed
- relates to
-
MDEV-9498 MariaDB server with Galera replication crashes randomly
- Closed
-
MDEV-10301 Signal 11 crash at random times
- Closed
-
MDEV-10501 MariaDB crash
- Closed
-
MDEV-13747 MariaDB 10.1.21 server sudden crash
- Closed
-
MDEV-10196 Binlog checkpoint segfault
- Closed
-
MDEV-10276 Crash signal 11 during logrotate
- Closed
-
MDEV-10601 Mariadb 10.1.16 got signal 11
- Closed
-
MDEV-10645 Crash signal 11 during SST on DONOR node
- Closed
-
MDEV-10656 Got Signal 11 on one node randomly every week since 3 months
- Closed
-
MDEV-10809 Logrotates flush-logs process never ends
- Closed
-
MDEV-11053 [ERROR] mysqld got signal 11 ;
- Closed
-
MDEV-11595 MariaDB server cluster regularly stops with an error
- Closed
-
MDEV-11860 Signal 11 - Buffer overflow detected
- Closed