[MDEV-17910] MariaDB Crashed when I Updated WSREP_ON Global Variable Created: 2018-12-05  Updated: 2022-01-24  Resolved: 2022-01-24

Status: Closed
Project: MariaDB Server
Component/s: Galera
Affects Version/s: 10.3.10
Fix Version/s: N/A

Type: Bug Priority: Major
Reporter: Test Jetco Assignee: Jan Lindström (Inactive)
Resolution: Incomplete Votes: 0
Labels: None
Environment:

RedHat 7.3


Attachments: File prondb11.err    

 Description   

Today I performed testing on Galera Clustering with MariaDB 10.3.10. I have 3-node cluster.

I updated the server.cnf with the following statement:

wsrep_on=OFF

I restarted mysql by ...

  1. systemctl stop mysql
  1. systemctl sart mysql

It worked.

wsrep_cluster_status = Disconnected
 
MariaDB [(none)]> SHOW global variables  LIKE 'wsrep_on%';
+---------------+-------+
| Variable_name | Value |
+---------------+-------+
| wsrep_on      | OFF   |
+---------------+-------+

Then I typed the following command to change wsrep_on to ON:

MariaDB [(none)]> set global wsrep_on = ON;
 
MariaDB [(none)]> SHOW global variables  LIKE 'wsrep_on%';
+---------------+-------+
| Variable_name | Value |
+---------------+-------+
| wsrep_on      | ON    |
+---------------+-------+
1 row in set (0.002 sec)

Then, MariaDB was DEAD!

  1. ps -ef|grep mysql
    root 6270 3685 0 17:24 pts/1 00:00:00 grep --color=auto mysql

Here attached is the error log file.



 Comments   
Comment by Elena Stepanova [ 2018-12-07 ]

From the error log (not helpful, but for the record):

10.3.10-MariaDB

181205 16:56:15 [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.3.10-MariaDB
key_buffer_size=134217728
read_buffer_size=131072
max_used_connections=1
max_threads=153
thread_count=7
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 467398 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
 
Thread pointer: 0x7f13f00009a8
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 = 0x7f1445cb3d70 thread_stack 0x49000
/usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x7f1462c8c1de]
/usr/sbin/mysqld(handle_fatal_signal+0x357)[0x7f14627266d7]
sigaction.c:0(__restore_rt)[0x7f1461b7d370]
/usr/sbin/mysqld(_Z14end_connectionP3THD+0x154)[0x7f146262da34]
sql/sql_connect.cc:1183(end_connection(THD*))[0x7f146262e1c4]
sql/sql_connect.cc:1408(do_handle_one_connection(CONNECT*))[0x7f146262e2cd]
pthread_create.c:0(start_thread)[0x7f1461b75dc5]
/lib64/libc.so.6(clone+0x6d)[0x7f14601c973d]
 
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): 10
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,orderby_uses_equalities=on,condition_pushdown_for_derived=on,split_materialized=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: 

Comment by Jan Lindström (Inactive) [ 2021-12-23 ]

testjetco Can you try with more recent version of MariaDB and Galera library?

Generated at Thu Feb 08 08:40:04 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.