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

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 ) order or-raid 0: ( iscsi_1 iscsi_2 iscsi_3 ) md_raid Got rid of the group, changed the score on the order to 0, and changed the grouping of both the colocation

[Pacemaker] continue starting chain with failed group resources

Is there a way to continue down a chain of starting resources once a previous resource hast tried to start, no matter if the try was successful or not? I've got 3 iSCSI resources which are in a group, and then an md raid-5 array as another resource. I have the raid array resource set to start

Re: [Pacemaker] colocation issues (isnt it always)

Sent: Mon Dec 13 2010 15:19:48 GMT-0700 (Mountain Standard Time) From: Pavlos Parissis To: The Pacemaker cluster resource manager Subject: Re: [Pacemaker] colocation issues (isnt it always) If you put all of them in a group and have the nfs_sdb1 as last resource you will manage to have what you

[Pacemaker] why two corosync pid running

Hi all    One node corosync start is ok ,however, could not add into cluster, I found corosync (pid 20303 20296) is running. is this result in the problem? ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/ma

Re: [Pacemaker] colocation issues (isnt it always)

On 13 December 2010 06:09, Patrick H. wrote: > > So colocation is biting me in the ass again and I cant figure this one out. > I have a group of iSCSI devices that then go into an md raid device that then > goes into an lvm device which then gets mounted and then exported by nfs. > Thoughout thi

Re: [Pacemaker] pingd location constraints

Simon, I'm new to this, so if this doesn't help, don't despair - the more experienced members will be along shortly. :-) Could it be that you need "stickyness?" I think that's the term for the concept you are describing. Also, if that's a two node cluster, have you defined cluster property no-q

Re: [Pacemaker] pingd location constraints

With the help of "crm_mon -f" I found out that just one node has the right pingd score. Migration summary: * Node node1: pingd=3 * Node node2: pingd=0 When I intiate a failover by setting node1 to standby the pingd score on node2 becomes 3. A ping that is run manually arrives the destina

[Pacemaker] GUUG-Frühjahrsfachgespräch 2011

[ This mail is in German, since the call for papers and the main focus of the conference is too. Sorry for the incovenience. ] Moin Cluster-Community, auch nächstes Jahr veranstaltet die German Unix User Group wieder ihr Frühjahrsfachgespräch - dieses Jahr in Wismar. Vielleicht möchtet ihr da j

[Pacemaker] pingd location constraints

Hi, I'm trying to set up location contraints for my cluster, but I don't get them to work in the way that I want. The constraints should implement the following behaviour: - Normal operation msDRBD0 and resIP0 start on node1, msDRBD1 and resIP1 start on node2 - Loss of network connection When the

Re: [Pacemaker] crmd exits and restarts after failback

Hi Andrew, thank you for your answer. I meanwhile deleted the configuration and set it up again. Now the error does not occur any more. -- Regards, Simon Jansen --- Simon Jansen 64291 Darmstadt ___ Pacemaker mailing list: Pa