I have the same problem as Quentin Smith (sticky pingd value="0").
[12:49:44 ha1] ~> rpm -qa | egrep -i "pacemaker|corosync|heartbeat|resource"
heartbeat-libs-3.0.2-2.el5
heartbeat-3.0.2-2.el5
pacemaker-libs-1.0.8-1.el5
resource-agents-1.0.1-1.el5
corosync-1.2.0-1.el5
pacemaker-1.0.8-1.el5
coros
On Sat, Mar 13, 2010 at 1:26 AM, Quentin Smith wrote:
> I don't know a lot about hg, but doesn't the "r15404" in the version of
> pacemaker that I'm running now mean that I already have this bugfix
> (r15295)?
Yes.
I'd suggest you use the ping RA instead of pingd.
The ping RA uses your system's
I don't know a lot about hg, but doesn't the "r15404" in the version of
pacemaker that I'm running now mean that I already have this bugfix
(r15295)?
--Quentin
On Fri, 12 Mar 2010, hj lee wrote:
Hi,
This seems the same problem I reported a while ago. It was fixed in
http://hg.clusterlabs.o
Hi,
This seems the same problem I reported a while ago. It was fixed in
http://hg.clusterlabs.org/pacemaker/stable-1.0/rev/214f0fc258f2.
Thanks
On Fri, Mar 12, 2010 at 2:36 PM, Quentin Smith wrote:
> Hi-
>
> I just took the latest updates to pacemaker and heartbeat from
> http://people.debian.
Hi-
I just took the latest updates to pacemaker and heartbeat from
http://people.debian.org/~madkiss/ha. In particular, I upgraded
heartbeat 1:3.0.2-1~bpo50+1 to 1:3.0.2+hg12547-2~bpo50+1
pacemaker 1.0.7+hg20100203-1~bpo50+1 to 1.0.7+hg20100303r15404-3~bpo50+1
cluster-agents 1:1.0.2-1~bpo50+1
