[MDEV-15102] MariaDB 10.2.9 server crashes when Galera replication is enabled Created: 2018-01-28  Updated: 2019-12-12  Resolved: 2019-12-12

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

Type: Bug Priority: Major
Reporter: Vidyasagar Mundroy Assignee: Jan Lindström (Inactive)
Resolution: Fixed Votes: 0
Labels: crash, galera, replication
Environment:

Ubuntu 16.04 LTS, 64-bit, Intel® Core™ i5-3210M CPU @ 2.50GHz × 4


Attachments: File mvslt.err     File my.cnf    

 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]

  1. 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!



 Comments   
Comment by Elena Stepanova [ 2018-01-28 ]

From the error log

/opt/mariadb/bin/mysqld(my_print_stacktrace+0x2e)[0xde4f7e]
/opt/mariadb/bin/mysqld(handle_fatal_signal+0x444)[0x7dcaf4]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x11390)[0x7fb8fcbd2390]
/opt/mariadb/bin/mysqld(_Z12wsrep_commitP10handlertonP3THDb+0x1df)[0x75245f]
/opt/mariadb/bin/mysqld[0x7e04ae]
/opt/mariadb/bin/mysqld(_Z15ha_commit_transP3THDb+0x208)[0x7e15e8]
/opt/mariadb/bin/mysqld(_Z17trans_commit_stmtP3THD+0x5c)[0x6ed56c]
/opt/mariadb/bin/mysqld(_Z18close_mysql_tablesP3THD+0x1d)[0x59b50d]
/opt/mariadb/bin/mysqld[0x5ff494]
/opt/mariadb/bin/mysqld(_Z11plugin_initPiPPci+0xc05)[0x600755]
/opt/mariadb/bin/mysqld[0x54b40d]
/opt/mariadb/bin/mysqld(_Z11mysqld_mainiPPc+0x526)[0x54c2b6]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf0)[0x7fb8fb946830]
/opt/mariadb/bin/mysqld(__gxx_personality_v0+0x3c9)[0x541769]
 
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): 0
Status: NOT_KILLED

Comment by Vidyasagar Mundroy [ 2019-12-12 ]

Thank you very much!

On Thu, Dec 12, 2019 at 5:19 PM Jan Lindström (Jira) <jira@mariadb.org>


Regards
M.Vidyasagar
http://www.queper.in
----------------------------------------------------------------------------------------------

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