Failed to Create Galera Cluster

Follow

Jati Nurohman

• October 11, 2018 17:41
• Edited

Hi,

Today I've updated ClusterControl to the latest version. But when I want to create a galera cluster with mariadb version 10.3, the process failed with last log below :

•  [00:32:09]: xx.xx.xx.xx:3306: failed to setup MySql server
•  [00:32:09]: xx.xx.xx.xx: Setup server failure, see the previous messages.
•  [00:32:08]: xx.xx.xx.xx: Installing cronie.
•  [00:32:08]: xx.xx.xx.xx:3306: The percona-xtrabackup package is not installed.
•  [00:32:08]: xx.xx.xx.xx: Failed to parse line 'Error: No matching Packages to list
  '.
•  [00:32:07]: xx.xx.xx.xx: Verifying the percona-xtrabackup* installation.
•  [00:32:05]: xx.xx.xx.xx:3306: Verifying the MySQL installation.
•  [00:26:20]: xx.xx.xx.xx: Installing MariaDB-server.x86_64 MariaDB-client.x86_64 galera MariaDB-compat.x86_64 MariaDB-common.x86_64 MariaDB-backup percona-toolkit percona-xtrabackup-24.

Seems like the script did not recognize that percona-xtrabackup was installed.

Here my clustercontrol version :

[root@clustercontrol ~]# rpm -qa | grep cluster
clustercontrol-notifications-1.7.0-139.x86_64
clustercontrol-1.7.0-5259.x86_64
clustercontrol-controller-1.7.0-2825.x86_64
clustercontrol-ssh-1.7.0-62.x86_64
clustercontrol-cmonapi-1.7.0-333.x86_64
clustercontrol-clud-1.7.0-147.x86_64
clustercontrol-cloud-1.7.0-147.x86_64
[root@clustercontrol ~]# cmon -v
cmon, version 1.7.0.2825

Enabled features: mongodb, mongo-scram-sha1, postgresql, websocket, yaml, rpc, libssh, mysql, prometheus
[root@clustercontrol ~]#

 

Do you have any idea to solve this error?

Thank you

0

• 

  Paul Namuag

  • October 11, 2018 20:37

  Hello Jati,

  We're sorry to hear that. In fact, we know this issue already. We have actually twitted here https://twitter.com/severalnines/status/1050092144944386048 and there's a Jira already created regarding this issue https://jira.mariadb.org/browse/MDEV-17379 which I left a comment. Unfortunately, MariaDB haven't commented yet on this.

   

  However, you can do the workaround but it's not feasible but it works.

  Since going thru the conventional way of using ClusterControl, I suggest that use ClusterControl to handle the installation for all your nodes to make it quicker and no manual hands-on to be wasted. Just go over this steps:

  • Deploy -> Select MySQL Galera -> Setup your SSH user credentials and cluster name -> Select MariaDB 10.3 -> Add Node one at a time. This means let CC install the packages for each and every node. The downside is that you have to duplicate this task each on every node but only replace the IP/Hostname on the "Add Node" part with the ip/hostname of the current node you're going to install. Let the error in ClusterControl since this is really a bug as mentioned in https://jira.mariadb.org/browse/MDEV-17379
  • Stop the mariadb background/daemon processes on all of the nodes i.e. 

       systemctl stop mariadb 

                or            

       service mariadb stop

  • Edit /bin/galera_new_cluster and on the last line, replace the "return" command with "exit" which would the expected output of the last line would look like as follows:

      exit $extcode

  - Then go back again to ClusterControl then,
    "Deploy -> Select MySQL Galera -> Setup your SSH user credentials and cluster name  and down below the "Cluster Name", you see the checkbox "Install Software". Set this to NO by clicking it leaving it just like then hit continue -> Select MariaDB 10.3 -> Add Node then add all the nodes IP/hostname.
  
  This works for me without any errors and I was able to run it without any issues:
  
  

  Alternatively, you just have to install manually on all of the nodes and import the nodes afterwards. 

  1

  Comment actions Permalink
• 

  Jati Nurohman

  • October 18, 2018 06:11

  Hi Paul.

  Thank you for your reply. I've tried your solution and the galera cluster works without any issue.

  0

  Comment actions Permalink

Please sign in to leave a comment.