Re: [Pacemaker] pingd location constraints

Hi Mike, thank you for the advice. Referring to my actual knowledge the resource stickiness just defines that a resource should remain to the node it is running on. The failover and failback actions are performed correctly with the location contraints that bind the resources to a specific node wh

Re: [Pacemaker] pingd location constraints

Hi, I just want to let you know that the problem is solved. Thanks to "crm_mon -f". ;) The error was the usage of the pingd RA. This RA worked very unreliable and is marked as deprecated though ( http://comments.gmane.org/gmane.linux.highavailability.user/32290). So after changing the RA to ocf:pa

[Pacemaker] monitor operation stopped running

Hi I have noticed this happening a few times on various of my clusters. The monitor operation for some resources stops running, and thus resource failures are not detected. If I edit the cib, and change something regarding the resource (generally I change the monitor interval), the resource start

Re: [Pacemaker] crmd exits and restarts after failback

Hi, On Wed, Dec 08, 2010 at 12:56:40PM +0100, Simon Jansen wrote: > Hi, > > I have set up a pacemaker cluster on Ubuntu 10.04 LTS Server. > Further I wrote an multistate OCF RA for the Rsyslog service. This RA passes > all tests that are run by the ocf-tester tool. > > Now the problem: > When I

Re: [Pacemaker] Best way to check if PM is alive

Hi, On Thu, Dec 09, 2010 at 02:58:33PM +0300, Evgeniy Ivanov wrote: > On Thu, Dec 9, 2010 at 2:32 PM, Andrew Beekhof wrote: > > On Thu, Dec 9, 2010 at 12:14 PM, Evgeniy Ivanov > > wrote: > >> Hi, > >> > >> What is a best way to check if PM is still alive? > > > > "ps axf | grep crmd" is one app

Re: [Pacemaker] monitor operation stopped running

Hi, On Tue, Dec 14, 2010 at 12:16:22PM +0200, Chris Picton wrote: > Hi > > I have noticed this happening a few times on various of my clusters. > The monitor operation for some resources stops running, and thus > resource failures are not detected. If I edit the cib, and change > something regar

Re: [Pacemaker] continue starting chain with failed group resources

Hi, On Mon, Dec 13, 2010 at 10:43:36PM -0700, Patrick H. wrote: > After tinkering with this for a few hours I finally have something working. > > colocation co-raid inf: ( md_raid iscsi_1 iscsi_2 iscsi_3 ) This should be noop. You'd want something like this, I think: colocation co-raid inf: md_

[Pacemaker] pacemaker + corosync in the cloud

Hi Is it possible to use pacemaker based on corosync in the cloud hosting like amazon or soflayer? ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org G

Re: [Pacemaker] continue starting chain with failed group resources

Sent: Tue Dec 14 2010 11:37:06 GMT-0700 (Mountain Standard Time) From: Dejan Muhamedagic To: The Pacemaker cluster resource manager Subject: Re: [Pacemaker] continue starting chain with failed group resources Hi, On Mon, Dec 13, 2010 at 10:43:36PM -0700, Patrick H. wrote: After tinkerin

Re: [Pacemaker] monitor operation stopped running

On Tue, 14 Dec 2010 18:55:06 +0100, Dejan Muhamedagic wrote: > Hi, > > On Tue, Dec 14, 2010 at 12:16:22PM +0200, Chris Picton wrote: >> Hi >> >> I have noticed this happening a few times on various of my clusters. >> The monitor operation for some resources stops running, and thus >> resource fa