I figured out what was wrong eventually, and I'd like to share the risults
with you all. 

I realized that the way to query the status is the following:

        cibadmin --query --scope=status | grep pingd

And that if I don't configure and start  the cloned ping gateway resource,
I'll never be able to have an answer like this from that query:

        <nvpair id="status-SDGRMA-pingd" name="pingd" value="1000"/>    
        <nvpair id="status-SDGRMB-pingd" name="pingd" value="1000"/>

So the constraint 
        location loc-active-ping grp-all  rule $id="loc-active-ping-rule"
-inf: not_defined pingd or pingd lte 0

will always shut down every resource dependent from the "pingd" attribute
(the resource group 'grp-all' in this example form my peculiar
configuration)

Everything seems to be working fine now.

Thank you Andrew for your time, your support has been very appreciated
Regards
Guglielmo


-----Messaggio originale-----
Da: linux-ha-boun...@lists.linux-ha.org
[mailto:linux-ha-boun...@lists.linux-ha.org] Per conto di Andrew Beekhof
Inviato: mercoledì 17 ottobre 2012 01:02
A: General Linux-HA mailing list
Oggetto: Re: [Linux-HA] cloned ping gateway not working

On Tue, Oct 16, 2012 at 8:57 PM, Guglielmo Abbruzzese <g.abbruzz...@resi.it>
wrote:
> Hi,
> a question probably easy but I'm stuck on it by now.
> I have Pacemaker installed from the RHEL62 repository, and I have some 
> resources that should be operating just if an external ping gateway 
> answers the ping request.
>
> I performed a simplified configuration in order to  test the following
> behavior: if the ping gateway is not reached the other resource should 
> shut down (and swap on the other node). I also avoided to clone the 
> resource in the test configuration.
>
> There are a couple of  things I'm not able to understand.
>
> 1.  MISSING PING GATEWAY NOT DETECTED. if I detach the network 
> interface leading to the gateway, I'd expect Pacemaker to get that.

How long did you wait?
Based on your config, it could take up to 30s (5 + 5 + 20) for anything to
happen.

> It doesn't happen;
> furthermore, in the message log I get what follows:
>
> Oct 16 11:29:34 SDGRMA lrmd: [29124]: info: perform_op:2884: operation 
> monitor[49] on ocf::ping::resource_ping_gateway for client 29127, its
> parameters: CRM_meta_interval=[5000] host_list=[172.16.8.20] 
> name=[ping_gateway] dampen=[5s] crm_feature_set=[3.0.5] 
> CRM_meta_enabled=[true] CRM_meta_on_fail=[restart] 
> CRM_meta_name=[monitor] multiplier=[1000] CRM_meta_timeout=[20000] 
> CRM_meta_requires=[nothing]  for rsc is already running.
> Oct 16 11:29:34 SDGRMA lrmd: [29124]: info: perform_op:2894: 
> postponing all ops on resource resource_ping_gateway by 1000 ms
>
> 2. DIFFICULTY SETTING THE "DON'T RUN ON UNCONNECTED NODES" OPTION 
> (example
> 9.3 in Pacemaker online docs).  If I try to set this constraint, even 
> if the ping gateway is available the virtual ip stops (until the 
> constraint is removed). What's wrong?
>
> crm configure log-active ping rule -inf: not_defined 
> resource_ping_gateway or resource_ping_gateway lte 0 (pls see cib down 
> here)

This should be:

    crm configure log-active ping rule -inf: not_defined ping_gateway or
ping_gateway lte 0

because of:

   <nvpair id="resource_ping_gateway-instance_attributes-name"
name="name" value="ping_gateway"/>

> I've read somewhere it is possible to use something like that to check 
> the pingd status
>     "crm_attribute -G -t status -N  -n pingd"
> But I can't find any "pingd" attribute in my cib.

Thats because (as above) you called it "ping_gateway".


>
> -------
>
> Any suggestion will be really appreciated.
> Thanks a lot
> G.
> -------
>
> TEST CIB
>
> I set 2 resources: a ping gateway (still to clone) and a virtual IP.
>
> <cib epoch="82" num_updates="0" admin_epoch="0"
> validate-with="pacemaker-1.2" crm_feature_set="3.0.5"
update-origin="SDGRMA"
> update-client="cibadmin" cib-last-written="Mon Oct 15 18:47:45 2012"
> have-quorum="1" dc-uuid="SDGRMA">
>   <configuration>
>     <crm_config>
>       <cluster_property_set id="cib-bootstrap-options">
>         <nvpair id="cib-bootstrap-options-dc-version" name="dc-version"
> value="1.1.6-3.el6-a02c0f19a00c1eb2527ad38f146ebc0834814558"/>
>         <nvpair id="cib-bootstrap-options-cluster-infrastructure"
> name="cluster-infrastructure" value="openais"/>
>         <nvpair id="cib-bootstrap-options-expected-quorum-votes"
> name="expected-quorum-votes" value="2"/>
>         <nvpair id="cib-bootstrap-options-no-quorum-policy"
> name="no-quorum-policy" value="ignore"/>
>         <nvpair id="cib-bootstrap-options-symmetric-cluster"
> name="symmetric-cluster" value="false"/>
>         <nvpair id="cib-bootstrap-options-stonith-enabled"
> name="stonith-enabled" value="false"/>
>         <nvpair id="cib-bootstrap-options-start-failure-is-fatal"
> name="start-failure-is-fatal" value="false"/>
>       </cluster_property_set>
>     </crm_config>
>     <nodes>
>       <node id="SDGRMA" type="normal" uname="SDGRMA"/>
>       <node id="SDGRMB" type="normal" uname="SDGRMB"/>
>     </nodes>
>     <resources>
>       <primitive class="ocf" id="resource_ping_gateway"
provider="pacemaker"
> type="ping">
>         <instance_attributes
id="resource_ping_gateway-instance_attributes">
>           <nvpair id="resource_ping_gateway-instance_attributes-host_list"
> name="host_list" value="172.16.8.20"/>
>           <nvpair id="resource_ping_gateway-instance_attributes-dampen"
> name="dampen" value="5s"/>
>           <nvpair
id="resource_ping_gateway-instance_attributes-multiplier"
> name="multiplier" value="1000"/>
>           <nvpair id="resource_ping_gateway-instance_attributes-name"
> name="name" value="ping_gateway"/>
>         </instance_attributes>
>         <operations>
>           <op enabled="true" id="resource_ping_gateway-startup"
> interval="5s" name="monitor" on-fail="restart" requires="nothing"
> timeout="20s"/>
>           <op id="resource_ping_gateway-start-0" interval="0" name="start"
> timeout="180s"/>
>           <op id="resource_ping_gateway-stop-0" interval="0" name="stop"
> timeout="180s"/>
>         </operations>
>         <meta_attributes id="resource_ping_gateway-meta_attributes">
>           <nvpair id="resource_ping_gateway-meta_attributes-target-role"
> name="target-role" value="Started"/>
>         </meta_attributes>
>       </primitive>
>       <primitive class="ocf" id="resource_vrt_ip" provider="heartbeat"
> type="IPaddr2">
>         <instance_attributes id="resource_vrt_ip-instance_attributes">
>           <nvpair id="resource_vrt_ip-instance_attributes-ip" name="ip"
> value="192.168.15.73"/>
>           <nvpair id="resource_vrt_ip-instance_attributes-nic" name="nic"
> value="bond0"/>
>         </instance_attributes>
>         <meta_attributes id="resource_vrt_ip-meta_attributes">
>           <nvpair id="resource_vrt_ip-meta_attributes-target-role"
> name="target-role" value="Started"/>
>           <nvpair id="resource_vrt_ip-meta_attributes-multiple-active"
> name="multiple-active" value="stop_start"/>
>           <nvpair id="resource_vrt_ip-meta_attributes-migration-threshold"
> name="migration-threshold" value="3"/>
>           <nvpair id="resource_vrt_ip-meta_attributes-failure-timeout"
> name="failure-timeout" value="0"/>
>         </meta_attributes>
>         <operations>
>           <op enabled="true" id="resource_vrt_ip-startup" interval="60"
> name="monitor" on-fail="restart" requires="nothing" timeout="180s"/>
>           <op id="resource_vrt_ip-start-0" interval="0" name="start"
> timeout="180s"/>
>           <op id="resource_vrt_ip-stop-0" interval="0" name="stop"
> timeout="180s"/>
>         </operations>
>       </primitive>
>     </resources>
>     <constraints>
>       <rsc_location id="loc-1a" node="SDGRMA" rsc="resource_ping_gateway"
> score="200"/>
>       <rsc_location id="loc-1b" node="SDGRMB" rsc="resource_ping_gateway"
> score="0"/>
>       <rsc_location id="loc-2a" node="SDGRMA" rsc="resource_vrt_ip"
> score="200"/>
>       <rsc_location id="loc-2b" node="SDGRMB" rsc="resource_vrt_ip"
> score="0"/>
>     </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

_______________________________________________
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