Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
10.2.9
-
Ubuntu 16.04 LTS, 64-bit, Intel® Core™ i5-3210M CPU @ 2.50GHz × 4
Description
MariaDB server crashes when setting "wsrep_on=ON" is specified in my.cnf. Full list of settings used for galera are as following:
[galera]
- Mandatory settings
wsrep_provider=/opt/mariadb/lib/galera/libgalera_smm.so
wsrep_cluster_address=gcomm://gcn-laptop:4567
wsrep_provider_options=gmcast.listen_addr=tcp://[::]:4567;ist.recv_addr=gcn-laptop:4568;gcache.size=4G;evs.join_retrans_period=PT30S;evs.keepalive_period=PT3S;evs.suspect_timeout=PT30S;evs.inactive_timeout=PT1M;evs.install_timeout=PT1M;gmcast.time_wait=PT5S
wsrep_sst_receive_address=gcn-laptop:4444
wsrep_cluster_name=EMSDB-GALERA
wsrep_node_name=gcn-laptop
wsrep_node_address=gcn-laptop:4567
wsrep_sst_method=rsync
binlog_format=ROW
default_storage_engine=InnoDB
innodb_autoinc_lock_mode=2
innodb_doublewrite=1
query_cache_size=0
wsrep_on=ON
Crash information wrote to a log is as following:
180128 16:59:08 [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.
Attached mariadb configuration and error log files.
Please note that I am not an expert in setting up Galera cluster and trying to learn how to setup. Possible that that I am going in a wrong direction in setting up the cluster. In any case, I do not expect server to crash!