On 02/02/15 11:48 AM, Jan Pokorný wrote:
On 26/01/15 15:14 +0100, Jan Pokorný wrote:
Timeline?
Best if you send me your public keys before 2015-02-02. I will then
compile a list of the attendees together with their keys and publish
it at https://people.redhat.com/jpokorny/keysigning/2015-ha/
so
On 26/01/15 15:14 +0100, Jan Pokorný wrote:
> Timeline?
> Best if you send me your public keys before 2015-02-02. I will then
> compile a list of the attendees together with their keys and publish
> it at https://people.redhat.com/jpokorny/keysigning/2015-ha/
> so you can print it out and be ready
That fence failed until the network came back makes your fence method
less than ideal. Will it eventually fence with the network still failed?
Most importantly though; Cluster resources blocked while the fence was
pending? If so, then your cluster is safe, and that is the most
important part.
On 01/30/2015 05:03 PM, Jérôme Charaoui wrote:
Thank you for looking at this, much appreciated.
The timeout issue intrigued me because I had noticed ipmitool taking
sometimes over 10 seconds attempting to execute an action on a
non-responding IPMI device over the lanplus interface.
So I ha
Hi,
I tryed a network failure and it works.
During failure, each node try to fence other node.
When network come back, the node with network problem is fenced and reboot.
Moreover, the cman kill(cman) on one node, tipically node1 kill(cman) on
node2, so, I have 2 situations:
1) Network failure on
