Issue with MariaDB-Galera-server update 10.0.33 to 10.0.34-1 in CentOS7

You are viewing an old version of this question. View the current version here.

Hi,

Not a question but an information about an issue : We had an issue performing a yum update from MariaDB-Galera-server-10.0.33 to MariaDB-Galera-server-10.0.34-1 in CentOS7. MySQL refused to restart after update.

Here is what appears in .err file :

180207 15:57:38 [Warning] WSREP: Gap in state sequence. Need state transfer.

180207 15:57:38 [Note] WSREP: Running: 'wsrep_sst_xtrabackup --role 'joiner' --address '172.30.65.37' --datadir '/var/lib/mysql/' --parent '45035' '' '

/usrbin/wsrep_sst_xtrabackup: ligne397: setup_ports : commande introuvable

180207 15:57:38 [ERROR] WSREP: Failed to read 'ready <addr>' from: wsrep_sst_xtrabackup --role 'joiner' --address '172.30.65.37' --datadir '/var/lib/mysql/' --parent '45035' ''

Read: '(null)'

180207 15:57:38 [ERROR] WSREP: Process completed with error: wsrep_sst_xtrabackup --role 'joiner' --address '172.30.65.37' --datadir '/var/lib/mysql/' --parent '45035' '' : 2 (No such file or directory)

180207 15:57:38 [ERROR] WSREP: Failed to prepare for 'xtrabackup' SST. Unrecoverable.

180207 15:57:38 [ERROR] Aborting

A workaround was to restore previous version of /usr/bin/wsrep_sst_xtrabackup (the 10.0.33 one), in which function setup_ports exists. Then we could restart MySQL ans synchronize with other members of the cluster.

System info :

[root@]# cat /etc/redhat-release

CentOS Linux release 7.4.1708 (Core)

[root@]# cat /etc/yum.repos.d/mariadb.repo

[mariadb]

name = MariaDB

baseurl = http://yum.mariadb.org/10.0/centos7-amd64

gpgkey=https://yum.mariadb.org/RPM-GPG-KEY-MariaDB

gpgcheck=1

Regards

Answer Answered by Geoff Montee in this comment.

This sounds kind of like MDEV-15351. That is fixed in MariaDB Galera Cluster 10.0.36.

Comments

Comments loading...
Content reproduced on this site is the property of its respective owners, and this content is not reviewed in advance by MariaDB. The views, information and opinions expressed by this content do not necessarily represent those of MariaDB or any other party.