Re: [Pacemaker] Node sends shutdown request to other node:error: handle_request: We didn't ask to be shut down, yet our DC is telling us too

On 17/07/2013, at 6:11 PM, K Mehta wrote: > Andrew, > Thanks to your reply. Here is the detail > > [root@vsanqa8 ~]# rpm -qa | grep pacemaker > pacemaker-cluster-libs-1.1.8-7.el6.x86_64 > pacemaker-1.1.8-7.el6.x86_64 > pacemaker-libs-1.1.8-7.el6.x86_64 > pacemaker-cli-1.1.8-7.el6.x86_64 > > [

Re: [Pacemaker] Pacemaker remote nodes, naming, and attributes

- Original Message - > From: "David Vossel" > To: "The Pacemaker cluster resource manager" > Sent: Monday, July 15, 2013 5:16:11 PM > Subject: Re: [Pacemaker] Pacemaker remote nodes, naming, and attributes > > - Original Message - > > From: "Lindsay Todd" > > To: "The Pacemaker

Re: [Pacemaker] Node sends shutdown request to other node:error: handle_request: We didn't ask to be shut down, yet our DC is telling us too

This isn't how fencing works. If a node enters an unknown state (stops responding to the other node(s)), it must be put into a known state. This mechanism must work without any input from the target node. If you try to do "resource level" fencing, you are assuming that the node can respond. S

Re: [Pacemaker] Help required translating crm commands into pcs ones

> -Original Message- > From: Chris Feist [mailto:cfe...@redhat.com] > Sent: 16 July 2013 20:38 > > On 07/15/13 09:02, Alex Hemsley wrote: > > Hi, > > > > We have some telephony failover equipment (Digium R850 appliances) > > that came with a sample Pacemaker configuration using the "crm >

Re: [Pacemaker] Question about the behavior when a pacemaker's process crashed

(13.07.16 21:18), Andrew Beekhof wrote: On 16/07/2013, at 7:04 PM, Kazunori INOUE wrote: (13.07.15 11:00), Andrew Beekhof wrote: On 12/07/2013, at 6:28 PM, Kazunori INOUE wrote: Hi, I'm using pacemaker-1.1.10. When a pacemaker's process crashed, the node is sometimes fenced or is not s

Re: [Pacemaker] version compatility

Andrew, I am using centos 6.2 and RHEL 6.2. Currently i have setup with whatever comes with distribution. 1. Are the components (pacemaker, cman, corosync) forward and backward compatible with each other..just in cases where i want to continue with current stable version of a component and upgr

Re: [Pacemaker] Node sends shutdown request to other node:error: handle_request: We didn't ask to be shut down, yet our DC is telling us too

Thanks Digimer. I will make sure that I configure fencing along with CMAN. I have multiple independent master slave resources in the cluster. A node could be master for few and slave for other resources. I need to make sure that fencing occurs at resource level (no klling of nodes) rather than at n

Re: [Pacemaker] Node sends shutdown request to other node:error: handle_request: We didn't ask to be shut down, yet our DC is telling us too

Andrew, Thanks to your reply. Here is the detail [root@vsanqa8 ~]# rpm -qa | grep pacemaker pacemaker-cluster-libs-1.1.8-7.el6.x86_64 pacemaker-1.1.8-7.el6.x86_64 pacemaker-libs-1.1.8-7.el6.x86_64 pacemaker-cli-1.1.8-7.el6.x86_64 [root@vsanqa8 ~]# rpm -qa | grep coro corosynclib-1.4.1-15.el6_4.