disable innobackupex --version-check

[Darren Carpenter]

When rebuilding a failed galera container, the joiner attempts to pull updates from the donor but the donor fails due to what appears to be a permission issue with the percona-version-check in /tmp. After modifying the permissions to mysql:mysql, the transfer succeeds and the container can then join the cluster.

Is it necessary that we keep this enabled?

[Kevin Carter (kevin-carter)]

This is a known issue with galera clusters (anything using the percona tools). Generally the version check file needs to either contain the proper permissions or be deleted to ensure cluster stability. What version were you seeing this issue on because I believe that problem was fixed in late 5.5 and for sure in 10.

[Darren Carpenter (wdarrenc)]

infra01_galera_container-f1e6f823 | success | rc=0 >>
ii libdbd-mysql-perl 4.025-1 amd64 Perl5 database interface to the MySQL database
ii libmariadbclient-dev 5.5.44+maria-1~trusty amd64 MariaDB database development files
ii libmariadbclient18 5.5.44+maria-1~trusty amd64 MariaDB database client library
ii libmysqlclient18 5.5.44+maria-1~trusty amd64 Virtual package to satisfy external depends
ii mariadb-client 5.5.44+maria-1~trusty all MariaDB database client (metapackage depending on the latest version)
ii mariadb-client-5.5 5.5.44+maria-1~trusty amd64 MariaDB database client binaries
ii mariadb-client-core-5.5 5.5.44+maria-1~trusty amd64 MariaDB database core client binaries
ii mariadb-common 5.5.44+maria-1~trusty all MariaDB database common files (e.g. /etc/mysql/conf.d/mariadb.cnf)
ii mariadb-galera-server-5.5 5.5.44+maria-1~trusty amd64 MariaDB database server with Galera cluster binaries
ii mysql-common 5.5.44+maria-1~trusty all MariaDB database common files (e.g. /etc/mysql/my.cnf)

infra02_galera_container-fb52b17c | success | rc=0 >>
ii libdbd-mysql-perl 4.025-1 amd64 Perl5 database interface to the MySQL database
ii libmariadbclient-dev 5.5.46+maria-1~trusty amd64 MariaDB database development files
ii libmariadbclient18 5.5.46+maria-1~trusty amd64 MariaDB database client library
ii libmysqlclient18 5.5.46+maria-1~trusty amd64 Virtual package to satisfy external depends
ii mariadb-client 5.5.46+maria-1~trusty all MariaDB database client (metapackage depending on the latest version)
ii mariadb-client-5.5 5.5.46+maria-1~trusty amd64 MariaDB database client binaries
ii mariadb-client-core-5.5 5.5.46+maria-1~trusty amd64 MariaDB database core client binaries
ii mariadb-common 5.5.46+maria-1~trusty all MariaDB database common files (e.g. /etc/mysql/conf.d/mariadb.cnf)
ii mariadb-galera-server-5.5 5.5.46+maria-1~trusty amd64 MariaDB database server with Galera cluster binaries
ii mysql-common 5.5.46+maria-1~trusty all MariaDB database common files (e.g. /etc/mysql/my.cnf)

infra03_galera_container-c226b2fc | success | rc=0 >>
ii libdbd-mysql-perl 4.025-1 amd64 Perl5 database interface to the MySQL database
ii libmariadbclient-dev 5.5.44+maria-1~trusty amd64 MariaDB database development files
ii libmariadbclient18 5.5.44+maria-1~trusty amd64 MariaDB database client library
ii libmysqlclient18 5.5.44+maria-1~trusty amd64 Virtual package to satisfy ext...

[Kevin Carter (kevin-carter)]

It seems like the best solution here is to document galera recovery to indicate that it may be necessary to remove the percona-version-check file if it causes issues. At this time I dont believe we can resolve this issue as its a bug within various versions of mariadb+galera 5.5