To close the loop, this was the root cause of the problem. There are several configuration files that mySQL reads at startup, and later files in the chain overwrite settings from files earlier in the chain. I had to edit two or three config files on each node to get mySQL to stop binding to 0.0.0.0 (netstat -tl is your friend!) but once I did the HAProxy clustered resource came back online.
Hopefully there's enough information in this thread to help those coming across this problem after me. ________________________________ From: Ian <ian.ninjabad...@gmail.com> Sent: Wednesday, March 16, 2016 8:27 PM To: Cluster Labs - All topics related to open-source clustering welcomed Subject: Re: [ClusterLabs] Installed Galera, now HAProxy won't start > configure MariaDB server to bind to all available ports > (http://docs.openstack.org/ha-guide/controller-ha-galera-config.html, scroll > to "Database Configuration," note that bind-address is 0.0.0.0.). If MariaDB > binds to the virtual IP address, then HAProxy can't bind to that address and > therefore won't start. Right? That is correct as far as my understanding goes. By binding to port 3306 on all IPs (0.0.0.0), you are effectively preventing HAProxy from being able to use port 3306 on its own IP and vice-versa. Try setting specific bind addresses for your Galera nodes; I would be surprised and interested if it didn't work. OpenStack Docs: Configuration<http://docs.openstack.org/ha-guide/controller-ha-galera-config.html> docs.openstack.org SELinux¶ Security-Enhanced Linux is a kernel module for improving security on Linux operating systems. It is commonly enabled and configured by default on Red Hat ...
_______________________________________________ Users mailing list: Users@clusterlabs.org http://clusterlabs.org/mailman/listinfo/users Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
