On 25/04/2013, at 5:22 AM, Brian J. Murrell br...@interlinx.bc.ca wrote:
On 13-04-24 01:16 AM, Andrew Beekhof wrote:
Almost certainly you are hitting:
https://bugzilla.redhat.com/show_bug.cgi?id=951340
Yup. The patch posted there fixed it.
I am doing my best to convince people
On 4/25/13 7:43 PM, Andrew Beekhof wrote:
I certainly hope so :)
So I should complain to our sales people about this BZ before we upgrade
our clusters to 6.4?
___
Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
On 26/04/2013, at 10:24 AM, David Coulson da...@davidcoulson.net wrote:
On 4/25/13 7:43 PM, Andrew Beekhof wrote:
I certainly hope so :)
So I should complain to our sales people about this BZ before we upgrade our
clusters to 6.4?
I don't think it would hurt to demonstrate how many
On 26/04/2013, at 10:24 AM, David Coulson da...@davidcoulson.net wrote:
On 4/25/13 7:43 PM, Andrew Beekhof wrote:
I certainly hope so :)
So I should complain to our sales people about this BZ before we upgrade our
clusters to 6.4?
Actually, I'm going to back-track on this.
After further
On 13-04-24 01:16 AM, Andrew Beekhof wrote:
Almost certainly you are hitting:
https://bugzilla.redhat.com/show_bug.cgi?id=951340
Yup. The patch posted there fixed it.
I am doing my best to convince people that make decisions that this is worthy
of an update before 6.5.
I've added
Using pacemaker 1.1.8 on RHEL 6.4, I did a test where I just killed
(-KILL) corosync on a peer node. Pacemaker seemed to take a long time
to transition to stonithing it though after noticing it was AWOL:
Apr 23 19:05:20 node2 corosync[1324]: [TOTEM ] A processor failed, forming
new
As I understand it, this is a known issue with the 1.1.8 release. I
believe that 1.1.9 is now available from the pacemaker repos and it
should fix the problem.
digimer
On 04/23/2013 03:34 PM, Brian J. Murrell wrote:
Using pacemaker 1.1.8 on RHEL 6.4, I did a test where I just killed
(-KILL)
