MariaDB Crashed when I Updated WSREP_ON Global Variable
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 ...
# systemctl stop mysql
# 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!
# ps -ef|grep mysql
root 6270 3685 0 17:24 pts/1 00:00:00 grep --color=auto mysql
Here below is the error log:
2018-12-05 16:33:47 0 [Note] InnoDB: 10.3.10 started; log sequence number 23935227307; transaction id 55857469
2018-12-05 16:33:47 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
2018-12-05 16:33:47 0 [Note] Plugin 'FEEDBACK' is disabled.
2018-12-05 16:33:47 0 [Note] Server socket created on IP: '::'.
2018-12-05 16:33:47 0 [Note] InnoDB: Buffer pool(s) load completed at 181205 16:33:47
2018-12-05 16:33:47 0 [Note] Reading of all Master_info entries succeded
2018-12-05 16:33:47 0 [Note] Added new Master_info '' to hash table
2018-12-05 16:33:47 0 [Note] /usr/sbin/mysqld: ready for connections.
Version: '10.3.10-MariaDB' socket: '/var/lib/mysql/mysql.sock' port: 3306 MariaDB Server
2018-12-05 16:33:47 8 [Warning] Access denied for user 'root'@'localhost' (using password: NO)
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:
-
Official comment
Hi,
It seems like you hit some bug in MariaDB or Galera code. I think the best course of action would be to open a bug report in MariaDB Jira (https://jira.mariadb.org/secure/Dashboard.jspa) and see if they can help you debugging this issue further. If you'll open the bug report, please paste the link to it here for the reference and for further readers who may end up with the similar case like you have.
Thanks,
KrzysztofComment actions -
Complete log here....
2018-12-05 16:33:15 0 [Note] InnoDB: Starting shutdown...
2018-12-05 16:33:15 0 [Note] InnoDB: Dumping buffer pool(s) to /var/lib/mysql/ib_buffer_pool
2018-12-05 16:33:15 0 [Note] InnoDB: Buffer pool(s) dump completed at 181205 16:33:15
2018-12-05 16:33:16 0 [Note] InnoDB: Shutdown completed; log sequence number 23935227307; transaction id 55857476
2018-12-05 16:33:16 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
2018-12-05 16:33:16 0 [Note] /usr/sbin/mysqld: Shutdown complete
2018-12-05 16:33:47 0 [Warning] You need to use --log-bin to make --binlog-format work.
2018-12-05 16:33:47 0 [Note] InnoDB: Using Linux native AIO
2018-12-05 16:33:47 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2018-12-05 16:33:47 0 [Note] InnoDB: Uses event mutexes
2018-12-05 16:33:47 0 [Note] InnoDB: Compressed tables use zlib 1.2.7
2018-12-05 16:33:47 0 [Note] InnoDB: Number of pools: 1
2018-12-05 16:33:47 0 [Note] InnoDB: Using SSE2 crc32 instructions
2018-12-05 16:33:47 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
2018-12-05 16:33:47 0 [Note] InnoDB: Completed initialization of buffer pool
2018-12-05 16:33:47 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2018-12-05 16:33:47 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2018-12-05 16:33:47 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2018-12-05 16:33:47 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2018-12-05 16:33:47 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
2018-12-05 16:33:47 0 [Note] InnoDB: 10.3.10 started; log sequence number 23935227307; transaction id 55857469
2018-12-05 16:33:47 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
2018-12-05 16:33:47 0 [Note] Plugin 'FEEDBACK' is disabled.
2018-12-05 16:33:47 0 [Note] Server socket created on IP: '::'.
2018-12-05 16:33:47 0 [Note] InnoDB: Buffer pool(s) load completed at 181205 16:33:47
2018-12-05 16:33:47 0 [Note] Reading of all Master_info entries succeded
2018-12-05 16:33:47 0 [Note] Added new Master_info '' to hash table
2018-12-05 16:33:47 0 [Note] /usr/sbin/mysqld: ready for connections.
Version: '10.3.10-MariaDB' socket: '/var/lib/mysql/mysql.sock' port: 3306 MariaDB Server
2018-12-05 16:33:47 8 [Warning] Access denied for user 'root'@'localhost' (using password: NO)
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: -
Already reported the bug to https://jira.mariadb.org/secure/Dashboard.jspa
Please sign in to leave a comment.
Comments
3 comments