Re: [Pacemaker] resource can not be started

2012-10-18 Thread Florian Crouzat
Le 18/10/2012 03:13, Mia Lueng a écrit : I just set "one" order rule: order rg_apache_order : res_ip_apache res_apache You mean the rule group rg_apache2 res_apache res_ip_apache \ meta target-role="Started" also indicates an order rule ? Yep, and a collocation as I said. It's all in t

Re: [Pacemaker] resource can not be started

2012-10-17 Thread Jake Smith
(Sorry for the top post)Yes... Groups are a syntactical shortcut for order and collocation statements. Resources in a group are ordered in the sequence they are written and collocated in reverse. HTHJakeFrom: Mia Lueng Sent: Wed, 17/10/2012 09:17 PMTo: The Pacemaker cluster resource manager Subject

Re: [Pacemaker] resource can not be started

2012-10-17 Thread Mia Lueng
I just set "one" order rule: order rg_apache_order : res_ip_apache res_apache You mean the rule group rg_apache2 res_apache res_ip_apache \ meta target-role="Started" also indicates an order rule ? 2012/10/17 Lars Marowsky-Bree : > On 2012-10-17T14:03:16, Florian Crouzat wrote: > >> Le

Re: [Pacemaker] resource can not be started

2012-10-17 Thread Lars Marowsky-Bree
On 2012-10-17T14:03:16, Florian Crouzat wrote: > Le 17/10/2012 11:56, Mia Lueng a écrit : > > >group rg_apache2 res_apache res_ip_apache \ > > meta target-role="Started" > >order rg_apache_order : res_ip_apache res_apache > > It seems not correct. A group is already a shortcut for an ordere

Re: [Pacemaker] resource can not be started

2012-10-17 Thread Florian Crouzat
Le 17/10/2012 11:56, Mia Lueng a écrit : group rg_apache2 res_apache res_ip_apache \ meta target-role="Started" order rg_apache_order : res_ip_apache res_apache It seems not correct. A group is already a shortcut for an ordered collocation. Either use collocation+ordering, or a group,

[Pacemaker] resource can not be started

2012-10-17 Thread Mia Lueng
sles11 sp2 High availability extenstion hatest01:~ # crm configure show node hatest01 node hatest02 node hatest03 primitive res_apache ocf:heartbeat:apache \ operations $id="res_apache-operations" \ op monitor interval="10" timeout="20s" \ params configfile="/etc/apache2/h