Thanks for the pings ;)
I got a bit farther with my configuration, but I'm stuck again and was
hopping someone could help me out.
The ip address is still not being transitioned to the active host. I
ran crm_verify. And here is what I got. I don't understand why the
pings are failing or what the router-no-connectivity warning is about.
# crm_verify -LV
crm_verify[19672]: 2009/09/08_23:21:14 ERROR: unpack_rsc_op: Hard
error - ping:0_monitor_0 failed with rc=5: Preventing connected from
re-starting on vm-ubuntu-1
crm_verify[19672]: 2009/09/08_23:21:14 ERROR: unpack_rsc_op: Hard
error - ping:0_monitor_0 failed with rc=5: Preventing connected from
re-starting on vm-ubuntu-2
crm_verify[19672]: 2009/09/08_23:21:14 WARN: unpack_rsc_location: No
resource (con=router-no-connectivity, rsc=clusterip)
crm_verify[19672]: 2009/09/08_23:21:14 WARN: native_color: Resource
ping:0 cannot run anywhere
crm_verify[19672]: 2009/09/08_23:21:14 WARN: native_color: Resource
ping:1 cannot run anywhere
crm_verify[19672]: 2009/09/08_23:21:14 WARN: native_color: Resource
clusterip:0 cannot run anywhere
Warnings found during check: config may not be valid
Here is my current config. I'm now running pacemaker-heartbeat 1.0.5
from the latest launchpad build.
<cib validate-with="pacemaker-1.0" crm_feature_set="3.0.1"
have-quorum="1" dc-uuid="9b229d79-fceb-4cc7-b131-fd690e97a990"
admin_epoch="0" epoch="41" num_updates="10">
<configuration>
<crm_config>
<cluster_property_set id="cib-bootstrap-options">
<nvpair id="cib-bootstrap-options-dc-version"
name="dc-version"
value="1.0.5-3840e6b5a305ccb803d29b468556739e75532d56"/>
<nvpair id="cib-bootstrap-options-cluster-infrastructure"
name="cluster-infrastructure" value="Heartbeat"/>
<nvpair id="cib-bootstrap-options-stonith-enabled"
name="stonith-enabled" value="false"/>
<nvpair id="cib-bootstrap-options-symmetric-cluster"
name="symmetric-cluster" value="true"/>
</cluster_property_set>
</crm_config>
<nodes>
<node id="9b229d79-fceb-4cc7-b131-fd690e97a990"
uname="vm-ubuntu-1" type="normal"/>
<node id="75031981-ed3c-40e9-b527-ccabe5a7e91d"
uname="vm-ubuntu-2" type="normal"/>
</nodes>
<resources>
<clone id="connected">
<meta_attributes id="connected_attributes">
<nvpair id="connected_globally_unique"
name="globally_unique" value="true"/>
<nvpair id="connected_target_role" name="target_role"
value="started"/>
</meta_attributes>
<primitive id="ping" provider="pacemaker" class="ocf" type="ping">
<instance_attributes id="ping-attrs">
<nvpair id="pingd-name" name="name" value="gateway-ping"/>
<nvpair id="pingd-dampen" name="dampen" value="5s"/>
<nvpair id="pingd-multiplier" name="multiplier" value="1000"/>
<nvpair id="pingd-hosts" name="host_list" value="172.16.209.2"/>
</instance_attributes>
<operations>
<op id="ping-monitor" interval="3s" name="monitor"/>
</operations>
</primitive>
</clone>
<clone id="router">
<meta_attributes id="router_attributes">
<nvpair id="router_globally_unique" name="globally_unique"
value="true"/>
<nvpair id="router_target_role" name="target_role" value="started"/>
<!-- <nvpair id="router_notify" name="notify" value="true"/> -->
</meta_attributes>
<primitive id="clusterip" class="ocf" type="IPaddr2"
provider="heartbeat">
<!-- Make sure the cluster ip address is active -->
<operations>
<op id="clusterip_monitor" name="monitor" interval="3s"/>
</operations>
<instance_attributes id="clusterip_attributes">
<nvpair id="clusterip_allow_migrate" name="allow-migrate"
value="true"/>
<nvpair id="clusterip_ip" name="ip" value="172.16.209.200"/>
<nvpair id="clusterip_cidr_netmask" name="cidr_netmask" value="24"/>
<nvpair id="clusterip_hash_mode" name="clusterip_hash"
value="sourceip-sourceport"/>
<nvpair id="cluster_nic" name="nic" value="eth0"/>
<nvpair id="cluster_mac" name="mac" value="01:00:5e:10:D1:C8"/>
</instance_attributes>
</primitive>
</clone>
</resources>
<constraints>
<rsc_location id="router-no-connectivity" rsc="clusterip">
<rule id="ping-exclude-rule" score="-INFINITY">
<expression id="ping-exclude" attribute="gateway-ping"
operation="not_defined"/>
</rule>
<rule id="ping-include-rule" score="INFINITY">
<expression id="ping-include" attribute="gateway-ping"
operation="defined"/>
</rule>
</rsc_location>
</constraints>
</configuration>
...
On Tue, Sep 8, 2009 at 2:18 AM, Andrew Beekhof<[email protected]> wrote:
> On Mon, Sep 7, 2009 at 5:35 PM, Michael Hale<[email protected]> wrote:
>
>> <constraints>
>> <rsc_location id="router-no-connectivity" rsc="router">
>> <rule id="ping-exclude-rule" score="-INFINITY" >
>> <expression id="ping-exclude" attribute="ping-gateway"
>> operation="not_defined"/>
>
> You need the _attribute_ name here, not the resource name.
> By default, the resource creates an attribute called "pingd", so change
> attribute="ping-gateway"
> to
> attribute="pingd"
> and you should find it works
> _______________________________________________
> Linux-HA mailing list
> [email protected]
> http://lists.linux-ha.org/mailman/listinfo/linux-ha
> See also: http://linux-ha.org/ReportingProblems
>
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
