Hi all,
I'm trying to build my first ever HA cluster and I'm using 3 VMs running CentOS
6.5. I followed the instructions to the letter at:
http://clusterlabs.org/quickstart-redhat.html
and everything appears to start normally, but if I run cman_tool nodes -a, I
only see:
Node StsInc
/10/14 02:50 PM, John Scalia wrote:
Hi all,
I'm trying to build my first ever HA cluster and I'm using 3 VMs running
CentOS 6.5. I followed the instructions to the letter at:
http://clusterlabs.org/quickstart-redhat.html
and everything appears to start normally, but if I run cman_tool nodes
Regards,
Maciej
2014-10-20 20:50 GMT+02:00 John Scalia jayknowsu...@gmail.com:
Hi all,
I'm trying to build my first ever HA cluster and I'm using 3 VMs running
CentOS 6.5. I followed the instructions to the letter at:
http://clusterlabs.org/quickstart-redhat.html
and everything appears
tool to isolate the source of the problem.
cheers
digimer
PS - Can you share your pacemaker configuration?
On 20/10/14 03:40 PM, John Scalia wrote:
Sure, and thanks for helping.
Here's the /etc/cluster/cluster.conf file and it is identical on all three
systems:
cluster config_version=11
Hi all, again,
My network engineer and I have found that the VM's hypervisor was set up to block multicast broadcasts by our security team. We're not really certain why or if we can change that
for at least my 3 systems. He's speaking with them now. Anyway, as you don't have to configure
wrote:
Keep us posted. :)
On 21/10/14 08:40 AM, John Scalia wrote:
I've been check hostname resolution this morning, and all the systems
are listed in each /etc/hosts file (No DNS in this environment.) and
ping works on every system both to itself and all the other systems. At
least it's working
-selected mcast IP, then
you can specify the mcast IP group to use via multicast... /.
digimer
On 21/10/14 12:22 PM, John Scalia wrote:
OK, looking at the cman man page on this system, I see the line saying
the corosync.conf file is not used. So, I'm guessing I need to set a
unicast address
Ok, got it working after a little more effort, and the cluster is now
properly reporting.
On Tue, Oct 21, 2014 at 1:34 PM, John Scalia jayknowsu...@gmail.com wrote:
So, I set transport=udpi' in the cluster.conf file, and it now looks
like this:
cluster config_version=11 name=pgdb_cluster
