[ClusterLabs] cluster stops randomly

Hi, I have a cluster and it works good, but I see sometimes cluster is stopped on all nodes and I should start manually. pcsd service is running but cluster is stopped.I see the pacemaker log but I couldn't find any warning or error. what is the issue? (stonith is disable.) Regards,H.Yavari

Re: [ClusterLabs] Resource seems to not obey constraint

On 05/20/2016 10:29 AM, Leon Botes wrote: > I push the following config. > The iscsi-target fails as it tries to start on iscsiA-node1 > This is because I have no target installed on iscsiA-node1 which is by > design. All services listed here should only start on iscsiA-san1 > iscsiA-san2. > I am

Re: [ClusterLabs] Issue in resource constraints and fencing - RHEL7 - AWS EC2

On 05/20/2016 10:02 AM, Pratip Ghosh wrote: > Hi All, > > I am implementing 2 node RedHat (RHEL 7.2) HA cluster on Amazon EC2 > instance. For floating IP I am using a shell script provided by AWS so > that virtual IP float to another instance if any one server failed with > health check. In basic

Re: [ClusterLabs] Antw: Re: Informing RAs about recovery: failed resource recovery, or any start-stop cycle?

Klaus Wenninger wrote: > On 05/20/2016 08:39 AM, Ulrich Windl wrote: > Jehan-Guillaume de Rorthais schrieb am 19.05.2016 um > 21:29 in > > Nachricht <20160519212947.6cc0fd7b@firost>: > > [...] > >> I was thinking of a use case where a graceful

Re: [ClusterLabs] Informing RAs about recovery: failed resource recovery, or any start-stop cycle?

Ken Gaillot wrote: > A recent thread discussed a proposed new feature, a new environment > variable that would be passed to resource agents, indicating whether a > stop action was part of a recovery. > > Since that thread was long and covered a lot of topics, I'm starting a

Re: [ClusterLabs] Antw: Re: FR: send failcount to OCF RA start/stop actions

Ken Gaillot wrote: > On 05/12/2016 06:21 AM, Adam Spiers wrote: > > Ken Gaillot wrote: > >> On 05/10/2016 02:29 AM, Ulrich Windl wrote: > Here is what I'm testing currently: > > - When the cluster recovers a resource, the resource agent's

[ClusterLabs] Resource seems to not obey constraint

I push the following config. The iscsi-target fails as it tries to start on iscsiA-node1 This is because I have no target installed on iscsiA-node1 which is by design. All services listed here should only start on iscsiA-san1 iscsiA-san2. I am using using the iscsiA-node1 basically for quorum

[ClusterLabs] Issue in resource constraints and fencing - RHEL7 - AWS EC2

Hi All, I am implementing 2 node RedHat (RHEL 7.2) HA cluster on Amazon EC2 instance. For floating IP I am using a shell script provided by AWS so that virtual IP float to another instance if any one server failed with health check. In basic level cluster is working but I have 2 issues on

Re: [ClusterLabs] crm_attribute bug in 1.1.15-rc1

Le Fri, 20 May 2016 15:31:16 +0300, Andrey Rogovsky a écrit : > Hi! > I cant get attribute value: > /usr/sbin/crm_attribute -q --type nodes --node-uname $HOSTNAME --attr-name > master-pgsqld --get-value > Error performing operation: No such device or address > > This value

Re: [ClusterLabs] Pacemaker not invoking monitor after $interval

> -Ursprüngliche Nachricht- > Von: Jehan-Guillaume de Rorthais [mailto:j...@dalibo.com] > Gesendet: Freitag, 20. Mai 2016 13:52 > An: Felix Zachlod (Lists) > Cc: users@clusterlabs.org > Betreff: Re: [ClusterLabs] Pacemaker not invoking monitor after > $interval >

[ClusterLabs] Antw: Pacemaker not invoking monitor after $interval

>>> "Felix Zachlod (Lists)" schrieb am 20.05.2016 um 13:33 in Nachricht <670f732376b88843b8df7ad917cf8dd9289c0...@bulla.intern.onesty-tech.loc>: > Hello! > > I am currently working on a cluster setup which includes several resources > with "monitor interval=XXs" set. As

Re: [ClusterLabs] Pacemaker not invoking monitor after $interval

Le Fri, 20 May 2016 11:33:39 +, "Felix Zachlod (Lists)" a écrit : > Hello! > > I am currently working on a cluster setup which includes several resources > with "monitor interval=XXs" set. As far as I understand this should run the > monitor action on the resource

[ClusterLabs] Pacemaker not invoking monitor after $interval

Hello! I am currently working on a cluster setup which includes several resources with "monitor interval=XXs" set. As far as I understand this should run the monitor action on the resource agent every XX seconds. But it seems it doesn't. Actually monitor is only invoked in special condition,

[ClusterLabs] Pacemaker reload Master/Slave resource

version 1.1.13-10.el7_2.2-44eb2dd Hello! I am currently developing a master/slave resource agent. So far it is working just fine, but this resource agent implements reload() and this does not work as expected when running as Master: The reload action is invoked and it succeeds returning 0. The

Re: [ClusterLabs] Antw: Re: Informing RAs about recovery: failed resource recovery, or any start-stop cycle?

Le Fri, 20 May 2016 11:12:28 +0200, "Ulrich Windl" a écrit : > >>> Jehan-Guillaume de Rorthais schrieb am 20.05.2016 um > 09:59 in > Nachricht <20160520095934.029c1822@firost>: > > Le Fri, 20 May 2016 08:39:42 +0200, > > "Ulrich Windl"

[ClusterLabs] Antw: Re: Antw: Re: Informing RAs about recovery: failed resource recovery, or any start-stop cycle?

>>> Jehan-Guillaume de Rorthais schrieb am 20.05.2016 um 09:59 in Nachricht <20160520095934.029c1822@firost>: > Le Fri, 20 May 2016 08:39:42 +0200, > "Ulrich Windl" a écrit : > >> >>> Jehan-Guillaume de Rorthais schrieb am

Re: [ClusterLabs] Antw: Re: Informing RAs about recovery: failed resource recovery, or any start-stop cycle?

On 05/20/2016 08:39 AM, Ulrich Windl wrote: Jehan-Guillaume de Rorthais schrieb am 19.05.2016 um 21:29 in > Nachricht <20160519212947.6cc0fd7b@firost>: > [...] >> I was thinking of a use case where a graceful demote or stop action failed >> multiple times and to give a

Re: [ClusterLabs] Antw: Re: Informing RAs about recovery: failed resource recovery, or any start-stop cycle?

Le Fri, 20 May 2016 08:39:42 +0200, "Ulrich Windl" a écrit : > >>> Jehan-Guillaume de Rorthais schrieb am 19.05.2016 um > >>> 21:29 in > Nachricht <20160519212947.6cc0fd7b@firost>: > [...] > > I was thinking of a use case where a graceful

[ClusterLabs] Antw: Re: Informing RAs about recovery: failed resource recovery, or any start-stop cycle?

>>> Jehan-Guillaume de Rorthais schrieb am 19.05.2016 um >>> 21:29 in Nachricht <20160519212947.6cc0fd7b@firost>: [...] > I was thinking of a use case where a graceful demote or stop action failed > multiple times and to give a chance to the RA to choose another method to >