Galera Node crashes regularly with signal 11
57 views
Skip to first unread message
Michael Hunger
Jul 15, 2021, 12:08:38 PM7/15/21
to codership
We have just configured a new cluster with 3 nodes. Regularly nodes crash with the following error message:
210715 14:08:51 [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.8-MariaDB-1:10.5.8+maria~focal-log
key_buffer_size=134217728
read_buffer_size=131072
max_used_connections=64
max_threads=302
thread_count=66
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 795868 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x7efafc05aea8
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 = 0x7efb836d1d58 thread_stack 0x49000
mysqld(my_print_stacktrace+0x32)[0x559e6b2c9692]
Printing to addr2line failed
mysqld(handle_fatal_signal+0x485)[0x559e6ad20e45]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x153c0)[0x7efcbf6563c0]
mysqld(_ZNK19rpl_sql_thread_info22cached_charset_compareEPc+0x6)[0x559e6ac0ea76]
mysqld(_ZN15Query_log_event14do_apply_eventEP14rpl_group_infoPKcj+0xa04)[0x559e6ae43dd4]
mysqld(_Z18wsrep_apply_eventsP3THDP14Relay_log_infoPKvm+0x1e9)[0x559e6aff2e79]
mysqld(_ZN22Wsrep_replayer_service15apply_write_setERKN5wsrep7ws_metaERKNS0_12const_bufferERNS0_14mutable_bufferE+0xac)[0x559e6afdaa4c]
mysqld(+0xf94270)[0x559e6b34c270]
mysqld(_ZN5wsrep12server_state8on_applyERNS_21high_priority_serviceERKNS_9ws_handleERKNS_7ws_metaERKNS_12const_bufferE+0xc1)[0x559e6b34d2c1]
mysqld(+0xfa4a3c)[0x559e6b35ca3c]
/usr/lib/libgalera_smm.so(+0x1b6de5)[0x7efcbedfade5]
/usr/lib/libgalera_smm.so(+0x202be8)[0x7efcbee46be8]
/usr/lib/libgalera_smm.so(+0x21d563)[0x7efcbee61563]
mysqld(_ZN5wsrep18wsrep_provider_v266replayERKNS_9ws_handleEPNS_21high_priority_serviceE+0x2d)[0x559e6b35d27d]
mysqld(_ZN20Wsrep_client_service6replayEv+0x102)[0x559e6afda562]
mysqld(_ZN5wsrep11transaction6replayERNS_11unique_lockINS_5mutexEEE+0x8a)[0x559e6b35720a]
mysqld(_ZN5wsrep11transaction15after_statementEv+0xe7)[0x559e6b359557]
mysqld(_ZN5wsrep12client_state15after_statementEv+0xaf)[0x559e6b3436df]
mysqld(+0x74e93c)[0x559e6ab0693c]
mysqld(_Z16dispatch_command19enum_server_commandP3THDPcjbb+0x2e54)[0x559e6ab144f4]
mysqld(_Z10do_commandP3THD+0x116)[0x559e6ab14d76]
mysqld(_Z24do_handle_one_connectionP7CONNECTb+0x411)[0x559e6ac19131]
mysqld(handle_one_connection+0x5d)[0x559e6ac195ad]
mysqld(+0xbbe266)[0x559e6af76266]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x9609)[0x7efcbf64a609]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x43)[0x7efcbf239293]
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0x7efafc047f12): SAVEPOINT `44dz61a6f62c947aaf3abz00a155d359`
Connection ID (thread ID): 1
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 /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 unlimited unlimited bytes
Max resident set unlimited unlimited bytes
Max processes unlimited unlimited processes
Max open files 1048576 1048576 files
Max locked memory 65536 65536 bytes
Max address space unlimited unlimited bytes
Max file locks unlimited unlimited locks
Max pending signals 125521 125521 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
Any idea what the reason could be?
Brian :
Jul 19, 2021, 4:02:44 AM7/19/21
to Michael Hunger, codership
It's probably a Maria issue. If you can get a back trace and file a bug report with them.
> --
> You received this message because you are subscribed to the Google Groups "codership" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to codership-tea...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/codership-team/91af49df-59c2-42fe-b0b0-6370a9b86e91n%40googlegroups.com.
>
> You received this message because you are subscribed to the Google Groups "codership" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to codership-tea...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/codership-team/91af49df-59c2-42fe-b0b0-6370a9b86e91n%40googlegroups.com.
>
Michael Hunger
Jul 19, 2021, 5:09:20 PM7/19/21
to Brian :, codership
Thanks for taking the time to read my message. We ran this application before with just maria 10.5 and did not have that issue. Is there a way to visualize the write-set that is applied here?
On 19. Jul 2021, at 10:02, Brian : <bri...@iptel.co> wrote:
It's probably a Maria issue. If you can get a back trace and file a bug report with them.
Colin Charles
Aug 18, 2021, 1:51:29 AM8/18/21
to Michael Hunger, Brian :, codership
You can definitely check the logs, and if repeatable, just turn on log verbosity to be higher
> On 20 Jul 2021, at 05:09, Michael Hunger <mic...@crewmeister.com> wrote:
>
> Thanks for taking the time to read my message. We ran this application before with just maria 10.5 and did not have that issue. Is there a way to visualize the write-set that is applied here?
--
Colin Charles, http://bytebot.net/blog/
twitter: @bytebot | skype: colincharles
"First they ignore you, then they laugh at you, then they fight you, then you win." -- Mohandas Gandhi
> On 20 Jul 2021, at 05:09, Michael Hunger <mic...@crewmeister.com> wrote:
>
> Thanks for taking the time to read my message. We ran this application before with just maria 10.5 and did not have that issue. Is there a way to visualize the write-set that is applied here?
Colin Charles, http://bytebot.net/blog/
twitter: @bytebot | skype: colincharles
"First they ignore you, then they laugh at you, then they fight you, then you win." -- Mohandas Gandhi
Reply all
Reply to author
Forward
0 new messages