Hide Forgot
This bug has been copied from bug #1299404 and has been proposed to be backported to 7.2 z-stream (EUS).
Instruction for test While galera cluster is up, create a new user for the test create user 'testuser'@'%' identified by 'test'; Allow user to log in to a tcp socket grant all privileges on 'testuser'@'%'; Stop galera. pcs resource disable galera Once stopped, change /etc/my.cnf.d/galera.cnf to have mysql listen to port 4242 on an available interface: bind_address=0.0.0.0 port=4242 Then configure /etc/sysconfig/clustercheck to make the resource agent contact mysqld on the tcp port above. Modify the entries so that the file looks like: MYSQL_USERNAME="testuser" MYSQL_PASSWORD="test" MYSQL_HOST="127.0.0.1" MYSQL_PORT="4242" (don't set MYSQL_HOST to "localhost" otherwise mysql will try to connect via UNIX socket) Start galera again. pcs resource enable galera After all machine are marked as master, verify that mysqld is listening to port 4242. netstat -tnlp | grep mysqld If so, the test is working as expected since the resource agent polls mysqld regularly to ensure that galera has started properly and is still running. For cleaning up, stop galera, reset the two config files to their original values, and restart galera. Once started, you can delete the test user drop user 'testuser'@'%';
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2016-0217.html