I solved the issue:
I had to configure resrouce-stickness option to 0 and now whatever hosts I
reboot the resources are back and stay like this:
ClusterVIP:0 (ocf::heartbeat:IPaddr2): Started haproxy01
ClusterVIP:1 (ocf::heartbeat:IPaddr2): Started haproxy02
Rega
:33:52 schrieb Net Warrior:
> > Hi there guys.
> (...)
> > If I do an sshd to the VIP I can see the round robin is woking and it
> > switches bettween hosts and I can see of course the alias created on the
> > eth0 iface.
> >
> > My problem is that when I re
Hi there guys.
I'm new to pacemaker and I'm trying to accomplish an active/active cluster
with a VIP ip address, I used the java frontend for the initial setup, I'm
using LCMC-1.7.6.jar.
This is what I've got:
CentOS release 6.5
pacemaker-libs-1.1.10-14.el6_5.3.x86_64
pacemaker-cli-1.1.10-14.el6_
i need the reverse way, how to remove the
resource-stickiness="INFINITY" from "crm(live)configure"?, i tried to add a
comment but it doesn't work, do you know to fix this issue?
Best regards from danian(warrior)
__
Hello,
I`ve configured heartbeat and pacemaker with 2 nodes, all resources work
well, all resources start when some of them is down, when the host is down,
pacemaker moves all resources to the other one, my configuration:
node $id="06d57c5a-3d47-4ef1-b518-7b8501f5ca9d" premailman1.mpt.es
node $id=
Hi There Guys.
Maybe this was asked a million times before, so, here goes the millon
and one.
I'm getting this error which I do not know what is means:
What is "not configured" what is "not installed" ? what "unmanaged" means?
I'm trying to set up a simple apache server cluster in order to