Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Incomplete
-
10.3.8
-
None
-
CentOS 7 x86-64
Description
The server crashed and through out:
Jul 30 17:10:56 maridb.server mysqld[12566]: 180730 17:10:56 [ERROR] mysqld got signal 11 ;
|
Jul 30 17:10:56 maridb.server mysqld[12566]: This could be because you hit a bug. It is also possible that this binary
|
Jul 30 17:10:56 maridb.server mysqld[12566]: or one of the libraries it was linked against is corrupt, improperly built,
|
Jul 30 17:10:56 maridb.server mysqld[12566]: or misconfigured. This error can also be caused by malfunctioning hardware.
|
Jul 30 17:10:56 maridb.server mysqld[12566]: To report this bug, see https://mariadb.com/kb/en/reporting-bugs |
Jul 30 17:10:56 maridb.server mysqld[12566]: We will try our best to scrape up some info that will hopefully help
|
Jul 30 17:10:56 maridb.server mysqld[12566]: diagnose the problem, but since we have already crashed,
|
Jul 30 17:10:56 maridb.server mysqld[12566]: something is definitely wrong and this may fail.
|
Jul 30 17:10:56 maridb.server mysqld[12566]: Server version: 10.3.8-MariaDB
|
Jul 30 17:10:56 maridb.server mysqld[12566]: key_buffer_size=1073741824
|
Jul 30 17:10:56 maridb.server mysqld[12566]: read_buffer_size=4194304
|
Jul 30 17:10:56 maridb.server mysqld[12566]: max_used_connections=5
|
Jul 30 17:10:56 maridb.server mysqld[12566]: max_threads=83
|
Jul 30 17:10:56 maridb.server mysqld[12566]: thread_count=14
|
Jul 30 17:10:56 maridb.server mysqld[12566]: It is possible that mysqld could use up to
|
Jul 30 17:10:56 maridb.server mysqld[12566]: key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 2070312 K bytes of memory
|
Jul 30 17:10:56 maridb.server mysqld[12566]: Hope that's ok; if not, decrease some variables in the equation. |
Jul 30 17:10:56 maridb.server mysqld[12566]: Thread pointer: 0x7fd998001298
|
Jul 30 17:10:56 maridb.server mysqld[12566]: Attempting backtrace. You can use the following information to find out |
Jul 30 17:10:56 maridb.server mysqld[12566]: where mysqld died. If you see no messages after this, something went
|
Jul 30 17:10:56 maridb.server mysqld[12566]: terribly wrong...
|
Jul 30 17:10:56 maridb.server mysqld[12566]: stack_bottom = 0x7fdc64089580 thread_stack 0x49000
|
Jul 30 17:10:56 maridb.server mysqld[12566]: /usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x56550ecbfece] |
Jul 30 17:10:56 maridb.server mysqld[12566]: /usr/sbin/mysqld(handle_fatal_signal+0x357)[0x56550e75c577] |
Jul 30 17:10:56 maridb.server mysqld[12566]: sigaction.c:0(__restore_rt)[0x7fdc718946d0]
|
Jul 30 17:10:56 maridb.server mysqld[12566]: /usr/sbin/mysqld(+0x95e529)[0x56550e93d529] |
Jul 30 17:10:56 maridb.server mysqld[12566]: /usr/sbin/mysqld(+0xa4b4f5)[0x56550ea2a4f5] |
Jul 30 17:10:56 maridb.server mysqld[12566]: /usr/sbin/mysqld(+0xa4bfd7)[0x56550ea2afd7] |
Jul 30 17:10:56 maridb.server mysqld[12566]: handler/ha_innodb.cc:20822(innobase_allocate_row_for_vcol(THD*, dict_index_t*, mem_block_info_t**, TABLE**, unsigned char**, VCOL_STORAGE**))[0x56550ea2c0bb] |
Jul 30 17:10:56 maridb.server mysqld[12566]: row/row0upd.cc:2140(row_upd_store_v_row)[0x56550e9f9311] |
Jul 30 17:10:56 maridb.server mysqld[12566]: row/row0upd.cc:2991(row_upd_del_mark_clust_rec)[0x56550e9e3fe3] |
Jul 30 17:10:56 maridb.server mysqld[12566]: row/row0upd.cc:3296(row_upd)[0x56550ea2598b] |
Jul 30 17:10:56 maridb.server mysqld[12566]: row/row0mysql.cc:2250(row_update_cascade_for_mysql(que_thr_t*, upd_node_t*, dict_table_t*))[0x56550ea2b4f8] |
Jul 30 17:10:56 maridb.server mysqld[12566]: row/row0ins.cc:1444(row_ins_foreign_check_on_constraint)[0x56550ea2c0bb] |
Jul 30 17:10:56 maridb.server mysqld[12566]: row/row0upd.cc:321(row_upd_check_references_constraints(upd_node_t*, btr_pcur_t*, dict_table_t*, dict_index_t*, unsigned long*, que_thr_t*, mtr_t*) [clone .part.44])[0x56550e9f8e0b] |
Jul 30 17:10:56 maridb.server mysqld[12566]: row/row0upd.cc:234(row_upd_check_references_constraints)[0x56550e938114] |
Jul 30 17:10:56 maridb.server mysqld[12566]: row/row0upd.cc:3296(row_upd)[0x56550e767c1f] |
Jul 30 17:10:56 maridb.server mysqld[12566]: sql/handler.cc:6284(handler::ha_delete_row(unsigned char const*))[0x56550e864201] |
Jul 30 17:10:56 maridb.server mysqld[12566]: sql/log_event.cc:14080(Delete_rows_log_event::do_exec_row(rpl_group_info*))[0x56550e857cec] |
Jul 30 17:10:56 maridb.server mysqld[12566]: sql/log_event.cc:11519(Rows_log_event::do_apply_event(rpl_group_info*))[0x56550e4e7593] |
Jul 30 17:10:57 maridb.server mysqld[12566]: sql/log_event.h:1482(Log_event::apply_event(rpl_group_info*))[0x56550e4f0c5c] |
Jul 30 17:10:57 maridb.server mysqld[12566]: pthread_create.c:0(start_thread)[0x7fdc7188ce25]
|
Jul 30 17:10:57 maridb.server mysqld[12566]: /lib64/libc.so.6(clone+0x6d)[0x7fdc6fc30bad] |
Jul 30 17:10:57 maridb.server mysqld[12566]: Trying to get some variables.
|
Jul 30 17:10:57 maridb.server mysqld[12566]: Some pointers may be invalid and cause the dump to abort.
|
Jul 30 17:10:57 maridb.server kernel: mysqld[12604]: segfault at 0 ip 000056550e93d529 sp 00007fdc64085dc0 error 4 in mysqld[56550dfdf000+12aa000] |
Jul 30 17:10:57 maridb.server mysqld[12566]: Query (0x0):
|
Jul 30 17:10:57 maridb.server mysqld[12566]: Connection ID (thread ID): 11
|
Jul 30 17:10:57 maridb.server mysqld[12566]: Status: NOT_KILLED
|
Jul 30 17:10:57 maridb.server mysqld[12566]: 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,orderby_uses_equalities=on,condition_pushdown_for_derived=on,split_materialized=on
|
Jul 30 17:10:57 maridb.server mysqld[12566]: The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains |
Jul 30 17:10:57 maridb.server mysqld[12566]: information that should help you find out what is causing the crash. |
Jul 30 17:10:57 maridb.server systemd[1]: mariadb.service: main process exited, code=killed, status=11/SEGV |
Jul 30 17:10:57 maridb.server systemd[1]: Unit mariadb.service entered failed state.
|
Jul 30 17:10:57 maridb.server systemd[1]: mariadb.service failed.
|
What can it be?
The server is a slave from 10.2 with some users reading data.
Attachments
Issue Links
- relates to
-
MDEV-17005 ASAN heap-use-after-free in innobase_get_computed_value
- Closed
-
MDEV-23033 All slaves crash once in ~24 hours and loop restart with signal 11
- Closed