On 18/06/2013, at 7:18 PM, Parkirat <[email protected]> wrote:
> Hi Sven,
>
> Thanks for replying back.
>
> By manually stopping, I mean, I am stopping the resource by running the
> below command:
> /etc/init.d/httpd stop, which is outside the control of pacemaker.
>
> Also, the entries for target-role is not duplicate.
Yes they are. There are 7 of them:
meta target-role="Started" \
meta is-managed="true" target-role="Started" \
meta resource-stickiness="100" target-role="Started" \
meta migration-threshold="2" target-role="Started" \
meta multiple-active="stop_start" target-role="Started" \
meta failure-timeout="300" target-role="Started" \
meta allow-migrate="true" target-role="Started"
> Its configure once for
> each resource. Moreover, I am not using group in the configuration but I am
> just collocating the resources. In the configurations see :
> colocation eip_for_apache inf: ElasticIP ApacheServer
>
> I am now confused at the below points:
>
> 1. To use collocations do we also need to make the groups?
no
> 2. I tried groups and collocation separately but not combined. How to use
> them in combination?
dont
> 3. With both using groups and collocation, if 1 resource is externally
> (outside the control of pacemaker) stopped, why is it not getting re-started
> by the pacemaker, when there is a monitor configured for resource. But if I
> do not use either of two viz. groups & collocation and just configure the
> resource not associating with any other resource, it does get started by the
> monitor properly.
Monitors don't start anything. They detect the failure and prompt pacemaker to
initiate recovery.
Please attach logs if you think pacemaker is not recovering the apache process
correctly.
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
