Hi Michael
[email protected] wrote on 07.10.2009 20:53:42:
> does the cluster know on what interface the IP should be added? Perhaps
you
> add a "nic" and a "cidr_netmask" attribute.
I've tried this but it makes no difference, the error message is still the
same. :-(
Configuration looks now like this:
<resources>
<group id="oanRscGroup">
<meta_attributes id="oanRscGroupMetaAttrs">
<nvpair id="oanRscGroupMetaattrIsManaged" name="is-managed"
value="true"/>
</meta_attributes>
<primitive class="ocf" id="rscIpaddr2" provider="heartbeat"
type="IPaddr2">
<operations id="rscIpaddr2Operations">
<op id="rscIpaddr2OpMonitor10s" interval="10s" name="monitor"
start-delay="0" timeout="20s"/>
</operations>
<instance_attributes id="rscIpaddr2InstanceAttributes">
<nvpair id="rscIpaddr2InstanceAttributesIp" name="ip"
value="172.17.206.169"/>
<nvpair id="rscIpaddr2InstanceAttributesNic" name="nic"
value="eth0"/>
<nvpair id="rscIpaddr2InstanceAttributesMask"
name="cidr_netmask" value="255.255.255.0"/>
</instance_attributes>
<meta_attributes id="rscIpaddr2MetaAttributes">
<nvpair id="rscIpaddr2MetaAttributesTargetRole"
name="target-role" value="Started"/>
</meta_attributes>
</primitive>
<primitive class="lsb" id="rsc_asterisk" type="asterisk">
<operations id="snmpWatchOperations">
<op id="rscOperations_asterisk" interval="15s" name="monitor"
start-delay="15" timeout="15s"/>
</operations>
<meta_attributes id="rsc_asterisk_MetaAttrs">
<nvpair id="rsc_asterisk_MetaAttrTargetRole" name="target-role"
value="Started"/>
</meta_attributes>
</primitive>
</group>
</resources>
<constraints>
<rsc_location id="cliPreferOanRscGroup" rsc="oanRscGroup">
<rule id="cliPreferRuleOanRscGroup" score="INFINITY"
boolean-op="and">
<expression id="cliPreferExprOanRscGroup" attribute="#uname"
operation="eq" value="oan-master" type="string"/>
</rule>
</rsc_location>
</constraints>
It is confusing for me that this error leads into the status section of the
cib because of its name "rscIpaddr2_monitor_0":
...
<node_state id="392d5983-173c-41f9-9746-16c9000e7e3e"
uname="oan-master" ha="active" in_ccm="true" crmd="online" join="member"
crm-debug-origin="do_update_resource" expected="member" shutdown="0">
<transient_attributes id="392d5983-173c-41f9-9746-16c9000e7e3e">
<instance_attributes
id="status-392d5983-173c-41f9-9746-16c9000e7e3e">
<nvpair
id="status-392d5983-173c-41f9-9746-16c9000e7e3e-probe_complete"
name="probe_complete" value="true"/>
</instance_attributes>
</transient_attributes>
<lrm id="392d5983-173c-41f9-9746-16c9000e7e3e">
<lrm_resources>
<lrm_resource id="rscIpaddr2" type="IPaddr2" class="ocf"
provider="heartbeat">
<lrm_rsc_op id="rscIpaddr2_monitor_0" operation="monitor"
crm-debug-origin="do_update_resource" crm_feature_set="3.0.1"
transition-key="7:3:7:8c2b1586-1818-4141-a65d-10ab8448c56a"
transition-magic="0:2;7:3:7:8c2b1586-1818-4141-a65d-10ab8448c56a"
call-id="2" rc-code="2" op-status="0" interval="0" last-run="1254990722"
last-rc-change="1254990722" exec-time="60" queue-time="0"
op-digest="07737dce74cd847dd179fca525414a86"/>
</lrm_resource>
...
What is a "lrm_rsc_op"?
Regards,
Yves Schumann
Softwareentwicklungsingenieur Security Solutions Division
IT-Koordinator
______________________________
Ascom (Schweiz) AG
Eichtal, CH-8634 Hombrechtikon
Phone: +41 55 254 66 84
[email protected]
http://www.ascom.com
"Walking on water and developing software from a specification are easy if
both are frozen" -- Edward V. Berard
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
