[MDEV-20626] MariaDB crash if wsrep_sst_method enabled without wsrep_cluster_address Created: 2019-09-18  Updated: 2021-06-30  Resolved: 2021-06-30

Status: Closed
Project: MariaDB Server
Component/s: wsrep
Affects Version/s: 10.4.8
Fix Version/s: N/A

Type: Bug Priority: Major
Reporter: Marcelo Altmann Assignee: Julius Goryavsky
Resolution: Not a Bug Votes: 0
Labels: None


 Description   

Starting MySQL without a wsrep_cluster_address and with wsrep_sst_method=mariabackup result in segmentation fault.

How to reproduce

mysqld --no-defaults --wsrep_on=ON --wsrep_provider=/usr/lib64/galera-4/libgalera_smm.so --wsrep_sst_method=mariabackup --user=mysql --binlog_format=ROW 

Result

2019-09-18 20:32:35 0 [Note] mysqld (mysqld 10.4.8-MariaDB) starting as process 2482 ...
2019-09-18 20:32:35 0 [ERROR] WSREP: mariabackup SST method requires wsrep_cluster_address to be configured on startup.
2019-09-18 20:32:35 0 [ERROR] Aborting
190918 20:32:35 [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.4.8-MariaDB
key_buffer_size=0
read_buffer_size=131072
max_used_connections=0
max_threads=153
thread_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 336663 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
 
Thread pointer: 0x0
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 = 0x0 thread_stack 0x49000
addr2line: 'mysqld': No such file
mysqld(my_print_stacktrace+0x2e)[0x555a45d3f83e]
mysqld(handle_fatal_signal+0x30f)[0x555a457d5e0f]
sigaction.c:0(__restore_rt)[0x7f7ab62115d0]
addr2line: 'mysqld': No such file
mysqld(unireg_abort+0x373)[0x555a455052b3]
mysqld(_Z11mysqld_mainiPPc+0x963)[0x555a4550c323]
/lib64/libc.so.6(__libc_start_main+0xf5)[0x7f7ab44cf3d5]
addr2line: 'mysqld': No such file
mysqld(+0x5cebd4)[0x555a454ffbd4]
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.
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        0                    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       1542427              1542427              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
 
Segmentation fault



 Comments   
Comment by Marcelo Altmann [ 2019-09-18 ]

Perhaps it's related to https://jira.mariadb.org/browse/MDEV-20624 . Galera errors are causing segmentation fault instead of abort and shut down the server cleanly.

Comment by Jan Lindström (Inactive) [ 2021-06-30 ]

Used configuration is not supported as noted in error log. Server startup is aborted intentionally using unireg_abort that causes assertion.

Generated at Thu Feb 08 09:00:56 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.