What your solution? 2009/9/29 Artur Kamiński <[email protected]>
> Dejan Muhamedagic pisze: > > Hi, > > > > On Tue, Sep 29, 2009 at 05:04:51PM +0200, artur.k wrote: > > > >> I have 4 nods heartbeat (2.1.4-7~bpo50+1 debian). were restarted all > servers and shows crm_mon > >> > >> Refresh in 1s... > >> > >> ============ > >> Last updated: Tue Sep 29 16:46:55 2009 > >> Current DC: lb-1 (2c5cda0b-8130-4e86-a308-559741c2861e) > >> 4 Nodes configured. > >> 4 Resources configured. > >> ============ > >> > >> Node: lb-4 (2e8f9314-a756-4370-b46c-15ac6a0fed25): OFFLINE > >> Node: lb-3 (20b19ab6-9313-49f9-b450-62b41d895795): online > >> Node: lb-2 (12a49fff-7248-49c2-913e-47a220eac033): online > >> Node: lb-1 (2c5cda0b-8130-4e86-a308-559741c2861e): online > >> > >> ip1 (ocf::heartbeat:IPaddr): Started lb-2 (unmanaged) FAILED > >> ip3 (ocf::heartbeat:IPaddr): Started lb-3 > >> ip4 (ocf::heartbeat:IPaddr): Started lb-3 > >> > >> Failed actions: > >> ip1_stop_0 (node=lb-2, call=13, rc=1): complete > >> ip2_monitor_20000 (node=lb-2, call=11, rc=7): complete > >> > >> Why has appeared "unmanaged" and how to prevent this ? > >> > > > > The stop operation failed with exit code 1. The logs should say > > more. Look for lrmd.*ip1. > > > > Thanks, > > > > Dejan > > > > > >> <cib generated="true" admin_epoch="0" have_quorum="true" > ignore_dtd="false" num_peers="4" cib_feature_revision="2.0" crm_feat > >> ure_set="2.0" epoch="43" num_updates="4" cib-last-written="Tue Sep 29 > 16:43:05 2009" ccm_transition="4" dc_uuid="2c5cda0b-8130 > >> -4e86-a308-559741c2861e"> > >> <configuration> > >> <crm_config> > >> <cluster_property_set id="cib-bootstrap-options"> > >> <attributes> > >> <nvpair id="cib-bootstrap-options-dc-version" > name="dc-version" value="2.1.4-node: aa909246edb386137b986c5773344b98 > >> c6969999"/> > >> <nvpair id="cib-bootstrap-options-no-quorum-policy" > name="no-quorum-policy" value="ignore"/> > >> <nvpair id="cib-bootstrap-options-default-action-timeout" > name="default-action-timeout" value="10s"/> > >> <nvpair id="cib-bootstrap-options-symmetric-cluster" > name="symmetric-cluster" value="true"/> > >> <nvpair id="cib-bootstrap-options-transition-idle-timeout" > name="transition-idle-timeout" value="5min"/> > >> </attributes> > >> </cluster_property_set> > >> </crm_config> > >> <nodes> > >> <node id="2e8f9314-a756-4370-b46c-15ac6a0fed25" uname="lb-4" > type="normal"/> > >> <node id="20b19ab6-9313-49f9-b450-62b41d895795" uname="lb-3" > type="normal"/> > >> <node id="12a49fff-7248-49c2-913e-47a220eac033" uname="lb-2" > type="normal"/> > >> <node id="2c5cda0b-8130-4e86-a308-559741c2861e" uname="lb-1" > type="normal"/> > >> </nodes> > >> <resources> > >> <primitive class="ocf" provider="heartbeat" type="IPaddr" > id="ip1"> > >> <instance_attributes id="ia-ip1"> > >> <attributes> > >> <nvpair name="ip" id="ia-ip1-1" value="x1"/> > >> <nvpair name="nic" id="ia-ip1-2" value="eth0"/> > >> <nvpair name="netmask" id="ia-ip1-3" value="26"/> > >> </attributes> > >> </instance_attributes> > >> <operations> > >> <op name="monitor" timeout="5s" role="Started" id="a1" > interval="20s"/> > >> </operations> > >> </primitive> > >> <primitive class="ocf" provider="heartbeat" type="IPaddr" > id="ip3"> > >> <instance_attributes id="ia-ip3"> > >> <attributes> > >> <nvpair name="ip" id="ia-ip3-1" value="x"/> > >> <nvpair name="nic" id="ia-ip3-2" value="eth0"/> > >> <nvpair name="netmask" id="ia-ip3-3" value="26"/> > >> </attributes> > >> </instance_attributes> > >> <operations> > >> <op name="monitor" timeout="5s" role="Started" id="a3" > interval="20s"/> > >> </operations> > >> </primitive> > >> ........... > >> </resources> > >> <constraints> > >> <rsc_location id="l-1-1" rsc="ip1" node="lb-1" score="INFINITY"/> > >> <rsc_location id="l-2-1" rsc="ip2" node="lb-2" score="INFINITY"/> > >> <rsc_location id="l-3-1" rsc="ip3" node="lb-3" score="INFINITY"/> > >> <rsc_location id="l-4-1" rsc="ip4" node="lb-4" score="INFINITY"/> > >> </constraints> > >> </configuration> > >> </cib> > >> > >> _______________________________________________ > >> 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 > > > > __________ Information from ESET NOD32 Antivirus, version of virus > signature database 4467 (20090929) __________ > > > > The message was checked by ESET NOD32 Antivirus. > > > > http://www.eset.com > > > > > > > > > > > > I found a solution :) > _______________________________________________ > Linux-HA mailing list > [email protected] > http://lists.linux-ha.org/mailman/listinfo/linux-ha > See also: http://linux-ha.org/ReportingProblems > -- Att, Maiquel _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
