[Linux-HA] Question about unmanaged resources

Andrew Beekhof beekhof at gmail.com
Mon Feb 12 01:40:21 MST 2007


any chance you could send though
  /var/lib/heartbeat/pengine/pe-warn-747.raw
and
  /var/lib/heartbeat/pengine/pe-warn-748.raw

that should help me figure it out

On 2/2/07, Rainer Ternes <ternesr at web.de> wrote:
>
> > version? configuration? logs?
>
>
> Version is 2.08
>
> complete log file is attached
>
>
> ha.cf:
>
> keepalive 250ms
> deadtime 30
> warntime 10
> initdead 120
> udpport 694
> bcast   eth0
> ucast eth0 192.168.0.253
> auto_failback off
> node    vpnay
> node    vpnby
> ping 192.168.10.20
> deadping 1
> debug 1
> apiauth ccm uid=hacluster
> apiauth cms uid=hacluster
> apiauth ping gid=haclient uid=root
> apiauth pingd uid=root
> crm on
> use_logd yes
>
>
> cib.xml:
>
> <cib admin_epoch="0" have_quorum="true" ignore_dtd="false" num_peers="1" cib_feature_revision="1.3" generated="false" epoch="18" num_updates="507" cib-last-written="Fri Feb  2 11:14:04 2007" ccm_transition="1">
> <configuration>
> <crm_config/>
> <nodes>
> <node id="779f2c82-52e3-4be5-aba6-5dde45b0f769" uname="vpnay" type="normal"/>
> <node id="197173f9-c84f-4165-84f7-177165772766" uname="vpnby" type="normal"/>
> </nodes>
> <resources>
> <clone id="pingd">
> <instance_attributes id="pingd">
> <attributes>
> <nvpair id="pingd-clone_node_max" name="clone_node_max" value="1"/>
> <nvpair id="pingd-multiplier" name="multiplier" value="100"/>
> <nvpair id="pingd-dampen" name="dampen" value="0"/>
> </attributes>
> </instance_attributes>
> <primitive id="pingd-child" provider="heartbeat" class="ocf" type="pingd">
> <operations>
> <op id="pingd-child-monitor" name="monitor" interval="20s" timeout="40s" prereq="nothing"/>
> <op id="pingd-child-start" name="start" prereq="nothing"/>
> </operations>
> </primitive>
> </clone>
> <primitive id="GatewayIPaddr" class="ocf" type="IPaddr" provider="heartbeat">
> <instance_attributes id="GatewayIPaddr_instance_attrs">
> <attributes>
> <nvpair id="cb95566f-8867-4887-be50-977e4c68d7a4" name="ip" value="192.168.0.23"/>
> <nvpair id="82319791-2851-4605-8d14-60bcafa509ec" name="netmask" value="24"/>
> <nvpair id="3fdad4d3-c16e-4af8-b74a-94404105b7de" name="nic" value="eth0"/>
> </attributes>
> </instance_attributes>
> <operations>
> <op id="63b024b9-acfd-49e4-92ba-85866c8362ac" name="start" timeout="90" disabled="false" role="Started" prereq="nothing" on_fail="restart" start_delay="0"/>
> <op id="598c5a8d-815a-46c1-b4ec-044d2a7c49dd" name="monitor" interval="5s" timeout="20s" start_delay="1s" disabled="false" role="Started" prereq="nothing" on_fail="restart"/>
> </operations>
> </primitive>
> </resources>
> <constraints>
> <rsc_location id="checkVPNA" rsc="pingd">
> <rule id="prefered_checkVPNA" score="-INFINITY">
> <expression attribute="#uname" id="b2d881b5-570d-4f49-8194-fdbd61bb46b7" operation="eq" value="vpnby"/>
> </rule>
> </rsc_location>
> <rsc_location id="GatewayIPaddr:preferred" rsc="GatewayIPaddr">
> <rule id="GatewayIPaddr:default:vpny" score="100">
> <expression attribute="#uname" id="GatewayIPaddr:default:vpnby:nameexpr" operation="eq" value="vpnby"/>
> </rule>
> <rule id="GatewayIPaddr:prefer:vpnby" score="-INFINITY" boolean_op="and">
> <expression attribute="#uname" id="GatewayIPaddr:prefer:vpnby:nameexpr" operation="eq" value="vpnay"/>
> <expression attribute="pingd" id="GatewayIPaddr:prefer:vpnby:pingdexpr" operation="eq" value="0"/>
> </rule>
> <rule id="GatewayIPaddr:prefer:vpnay" score="INFINITY" boolean_op="and">
> <expression attribute="#uname" id="GatewayIPaddr:prefer:vpnay:nameexpr" operation="eq" value="vpnay"/>
> <expression attribute="pingd" id="GatewayIPaddr:prefer:vpnay:pingdexpr" operation="eq" value="1"/>
> </rule>
> </rsc_location>
> </constraints>
> </configuration>
> </cib>
> > On 2/2/07, Rainer Ternes <ternesr at web.de> wrote:
> > > Hi,
> > >
> > > im looking for a smart explanation why the resource IPaddr is changing
> > > its status to unmanaged when the value of keepalive in ha.cf is
> > > decreased to much.
> > >
> > >
> > > Thanks in advance for at least good ideas!
> > >
> > > Rainer
> > >
> > > _______________________________________________
> > > Linux-HA mailing list
> > > Linux-HA at 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 at lists.linux-ha.org
> http://lists.linux-ha.org/mailman/listinfo/linux-ha
> See also: http://linux-ha.org/ReportingProblems
>
>


More information about the Linux-HA mailing list