[MDEV-21006] Can't add galera node Created: 2019-11-07  Updated: 2019-12-12  Resolved: 2019-12-12

Status: Closed
Project: MariaDB Server
Component/s: Galera, Galera SST
Affects Version/s: 10.4.8
Fix Version/s: N/A

Type: Bug Priority: Major
Reporter: Loris Reiff Assignee: Jan Lindström (Inactive)
Resolution: Not a Bug Votes: 0
Labels: galera
Environment:

mysql Ver 15.1 Distrib 10.4.8-MariaDB, for debian-linux-gnu (x86_64) using readline 5.2

Debian 10 Buster
Repo: http://mirror.mva-n.net/mariadb/repo/10.4/debian buster main

Virtual machines


Attachments: File 60-server.cnf     File mariadb.cnf     File my.cnf     HTML File syslog    

 Description   

Hi,

I tested galera-3 and mariadb from the Debian repo, which worked with the provided configs (there are some config files that come with the Debian install, but they didn't seem to matter). However, their version uses yassl which is buggy and doesn't support tls 1.3. So I tried the 10.4.8-MariaDB version from the official repo which comes with openssl. I did a complete reinstall, but I can't add a second galera node, which worked with the package that debian provides...

I use ansible to configure the DB, so after installing mariadb, I add a root password and perform the suggested hardening steps (i.e. the ones im mysql_secure_installation) on both servers (virtual machines) called asldb01 and asldb02. I only then add the 60-server.cnf to /etc/mysql/mariadb.conf.d/ and stop both mariadb instances with `systemctl stop mysql`. Note I only attached the 60-server.cnf of asldb02, but the other one is similar except that the names are set accordingly. I restart them as follows:

On one (virual) machine [asldb01] I start galera with: `galera_new_cluster` and on the other node I start it with `systemctl start mysql`. Unfortunately, the second one does not start successfully... The relevant part of the log can be seen in the syslog file.

Let me know if more information is needed.
Thanks for you time



 Comments   
Comment by Loris Reiff [ 2019-11-13 ]

I got it working by using the ip addresses instead of the hostnames for "wsrep_cluster_address" and "wsrep_node_address".

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