On Thu, Jul 3, 2008 at 22:29, Raghuram Bondalapati
<[EMAIL PROTECTED]> wrote:
> Hi folks,
>
> I have setup a two node HA cluster with IPaddr as OCF resource and xinetd as
> LSB resource with a colocation constraint on INFINITY.
> The failover of services to second node works fine when the first node
> running the listed services goes down or is rebooted. If the xinted process
> is killed manually on first node it gets restarted automatically on the same
> node.
>
> However I am having trouble with xinetd service failover when i kill the
> xinetd process and prevent it from starting by changing the permission on
> the binary to 000.  I assume at this point HA should fence the node running
> xinetd service and then failover the service to second node. However  that's
> not happening and the xinted service is down.

It would if you defined a fencing resource.

>
> Any help figuring out what i am doing wrong is very much appreciated.
>
>
> The cluster is setup with CRM options of
>
> Symmetric Cluster
> Default Resource Stickiness: 10000
> Default Resource Failure Stickiness: -10001
>
>  <cib generated="true" admin_epoch="0" have_quorum="true" ignore_dtd="false"
> num_peers="2" cib_feature_revision="2.0" crm_feature_set="2.0"
> ccm_transition="14" dc_uuid="03fd6ad6-e7b1-4722-96d8-54e3be84a59c"
> epoch="53" num_updates="1" cib-last-written="Thu Jul  3 13:25:37 2008">
>   <configuration>
>     <crm_config>
>       <cluster_property_set id="cib-bootstrap-options">
>         <attributes>
>           <nvpair id="cib-bootstrap-options-dc-version" name="dc-version"
> value="2.1.3-node: a3184d5240c6e7032aef9cce6e5b7752ded544b3"/>
>           <nvpair id="cib-bootstrap-options-stonith-enabled"
> name="stonith-enabled" value="true"/>
>           <nvpair id="cib-bootstrap-options-default-resource-stickiness"
> name="default-resource-stickiness" value="10000"/>
>           <nvpair
> id="cib-bootstrap-options-default-resource-failure-stickiness"
> name="default-resource-failure-stickiness" value="-10001"/>
>         </attributes>
>       </cluster_property_set>
>     </crm_config>
>     <nodes>
>       <node id="1f0ffb39-b275-4e92-b6ca-8a3d00f2fb44" uname="vcs9473"
> type="normal"/>
>       <node id="03fd6ad6-e7b1-4722-96d8-54e3be84a59c" uname="vcs9472"
> type="normal"/>
>     </nodes>
>     <resources>
>       <primitive id="ip_resource" class="ocf" type="IPaddr"
> provider="heartbeat">
>         <instance_attributes id="eab77edc-f1ab-4f86-8a68-afe65a45d098">
>           <attributes>
>             <nvpair name="ip" value="172.25.52.245"
> id="bafe2639-e510-4484-a234-862bad7acad1"/>
>           </attributes>
>         </instance_attributes>
>         <meta_attributes id="ip_resource_meta_attrs">
>           <attributes/>
>         </meta_attributes>
>       </primitive>
>       <primitive id="xinted_resource" class="lsb" type="xinetd"
> provider="heartbeat">
>         <operations>
>           <op id="6f3399d7-31fe-4706-af01-5d58d96c3017" name="monitor"
> interval="15" timeout="15" start_delay="15" disabled="false" role="Started"
> on_fail="fence"/>
>         </operations>
>         <meta_attributes id="xinted_resource_meta_attrs">
>           <attributes/>
>         </meta_attributes>
>       </primitive>
>     </resources>
>     <constraints>
>       <rsc_colocation id="colocation_" from="ip_resource"
> to="xinted_resource" score="INFINITY" symmetrical="false"/>
>     </constraints>
>   </configuration>
> </cib>
> _______________________________________________
> Linux-HA mailing list
> Linux-HA@lists.linux-ha.org
> http://lists.linux-ha.org/mailman/listinfo/linux-ha
> See also: http://linux-ha.org/ReportingProblems
>
_______________________________________________
Linux-HA mailing list
Linux-HA@lists.linux-ha.org
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems

Reply via email to