Re: [Pacemaker] Pacemaker restart resources when node joins cluster after failback

2012-03-05 Thread José Alonso
Hi all, I removed apache from the init-process but still having the same behavior. When a node rejoins the cluster, all resources are restarted again. Is there any way to avoid that?? Best regards, Jose On Mon, Mar 5, 2012 at 2:53 PM, Arnold Krille wrote: > Hi, > > On Monday 05 March 2012 12:

[Pacemaker] Can Master/Slave resource transit from Master to Stopped directly ?

2012-03-05 Thread Takatoshi MATSUO
Hi I want Pacemaker to transit from Master to Stopped directly on demote without failcount for managing PostgreSQL streaming replication. Can Pacemaker do this ? I returned "$OCF_NOT_RUNNING" on demote as a trial, but it incremented a failcount. Regards, Takatoshi MATSUO ___

Re: [Pacemaker] Pacemaker restart resources when node joins cluster after failback

2012-03-05 Thread Arnold Krille
Hi, On Monday 05 March 2012 12:58:16 José Alonso wrote: > I have 2 Debian nodes with heartbeat and pacemaker 1.1.6 installed, and > almost everything is working fine, I have only apache configured for > testing, when a node goes down the failover is done correctly, but there's > a problem when a n

[Pacemaker] Pacemaker restart resources when node joins cluster after failback

2012-03-05 Thread José Alonso
Hi all, I have 2 Debian nodes with heartbeat and pacemaker 1.1.6 installed, and almost everything is working fine, I have only apache configured for testing, when a node goes down the failover is done correctly, but there's a problem when a node failbacks. For example, let's say that Node1 has th

Re: [Pacemaker] STONITH: Avocent PDU ?

2012-03-05 Thread Dejan Muhamedagic
Hi, On Wed, Feb 29, 2012 at 10:58:06AM +0100, Pascal Bleser wrote: > Does anyone have experience with using an Avocent (formerly known as > Cyclades) APDU with STONITH ? > http://www.avocent.de/Products/Category/Power_Distribution_Units/PM1000_2000_3000_PDUs.aspx#tab=details_tab_6 > > I would be

Re: [Pacemaker] fence_legacy, stonith and apcmastersnmp

2012-03-05 Thread Kadlecsik József
On Mon, 5 Mar 2012, Andrew Beekhof wrote: > 2012/3/2 Kadlecsik József : > > On Fri, 2 Mar 2012, Andrew Beekhof wrote: > > > >> 2012/3/2 Kadlecsik József : > >> > > >> > After upgrading to pacemaker 1.1.6, cluster-glue 1.0.8 on Debian, our > >> > working apcmastersnmp resources stopped to work: > >

Re: [Pacemaker] prevent the resource's start if it has "stop NG" history on the other node

2012-03-05 Thread Junko IKEDA
>> Actually, it's desirable to "prevent Pacemaker shutdown" if there are >> unmanaged resource, > > What about unmanaged /and/ failed? To be more specific, if there remains the resource which failed to stop operation and went to the unmanaged status with its on-fail="block" configuration, it would

Re: [Pacemaker] prevent the resource's start if it has "stop NG" history on the other node

2012-03-05 Thread Andrew Beekhof
On Mon, Mar 5, 2012 at 8:45 PM, Junko IKEDA wrote: > Hi, > >> On the one hand the admin is saying "always stop A before B", but then >> also asking for "stop B" while preventing "stop A". >> So the admin is making incompatible demands, which one do you want us to >> ignore? > > It seems that the

Re: [Pacemaker] prevent the resource's start if it has "stop NG" history on the other node

2012-03-05 Thread Junko IKEDA
Hi, > On the one hand the admin is saying "always stop A before B", but then > also asking for "stop B" while preventing "stop A". > So the admin is making incompatible demands, which one do you want us to > ignore? It seems that the current Pacemaker does shutdown in spite of unmanaged resource