On Wed, Feb 24, 2010 at 9:33 AM, Alain.Moulle wrote:
> Hi Andrew,
> I meant "stopped" by target-role : crm resource respingal2 stop
Then the behavior is expected, since there is no cluster node it is
allowed to run on.
And if it can't run anywhere, why bother moving the rest of the group?
> You
Hi Andrew,
I meant "stopped" by target-role : crm resource respingal2 stop
You mean that the behavior of collocation is only valuable for status
failed event ? Not
in case of voluntary crm stop commands ?
Thanks
Alain
> > so I did some simple scripts /pingalain1/ (resource respingal1) and
> /ping
On Tue, Feb 23, 2010 at 3:32 PM, Alain.Moulle wrote:
> Hi Andrew
>
> ok that was not a good choice to take smard as test init script to
> demonstrate the problem about group ... sorry , so I did some simple
> scripts /pingalain1/ (resource respingal1) and /pingalain2/ (resource
> respingal2)
> whi
Hi Andrew
ok that was not a good choice to take smard as test init script to
demonstrate the problem about group ... sorry , so I did some simple
scripts /pingalain1/ (resource respingal1) and /pingalain2/ (resource
respingal2)
which have for sure status eq 0 gathered in a group /groupresping/
smartd2 can't run on node1 because it returned rc=5 for the monitor op.
EXECRA_NOT_INSTALLED = 5,
On Mon, Feb 22, 2010 at 3:34 PM, Alain.Moulle wrote:
> Hi Andrew,
>
> sorry for the delay, but about my problem on groups I've reproduced it with
> only two resources resal1 and resal2 gat
Hi Andrew,
sorry for the delay, but about my problem on groups I've reproduced it with
only two resources resal1 and resal2 gathered in a group groupal1.
The behavior is :
1/ when both res are started, and I stop resal1 , all the group is stopped.
2/ when both res are started, and I stop resal2
On Wed, Feb 17, 2010 at 8:02 AM, Alain.Moulle wrote:
> Hi Andrew,
> the releases are those officially delivered with fc12 :
> pacemaker-1.0.5-4.fc12
> and :
> cluster-glue-1.0-0.11.b79635605337.hg.fc12
> corosync-1.1.2-1.fc12
> heartbeat-3.0.0-0.5.0daab7da36a8.hg.fc12
> openais-1.1.0-1.fc12
> all
Hi Andrew,
the releases are those officially delivered with fc12 :
pacemaker-1.0.5-4.fc12
and :
cluster-glue-1.0-0.11.b79635605337.hg.fc12
corosync-1.1.2-1.fc12
heartbeat-3.0.0-0.5.0daab7da36a8.hg.fc12
openais-1.1.0-1.fc12
all in x86_64 .
Thanks
Alain
> Hi,
> >
> > Suppose we have 4 resources in
On Tue, Feb 16, 2010 at 5:00 PM, Alain.Moulle wrote:
> Hi,
>
> Suppose we have 4 resources in a group, res1, res2, res3 and res4.
>
> By default if the res4 fails(or stops), there is no impact on others,
What version are you using?
Recent versions shouldn't be behaving like that.
> whereas if
>
Hi,
Suppose we have 4 resources in a group, res1, res2, res3 and res4.
By default if the res4 fails(or stops), there is no impact on others,
whereas if
res2 fails(or stops) , res3 and res4 will be stopped and no impact on res1.
But I would like that if any of the 4 resources fails(or stops) , t
10 matches
Mail list logo
