it's now also fixed upstream
On 6/5/07, Claes Lindvall <[EMAIL PROTECTED]> wrote:
Ok. Its fine with me. I know how to get rid of the counting-error, and
that is good enough for now.
Thanks.
/Claes
Andrew Beekhof skrev:
> On 6/5/07, Claes Lindvall <[EMAIL PROTECTED]> wrote:
>> And here comes the output from cibadmin -Ql attached in a file (xml.txt)
>> The output from crm_mon -i 2 is
>>
>> ============
>> Last updated: Tue Jun 5 08:03:38 2007
>> Current DC: lx11 (19469e0b-4e6f-4688-b827-863b2d2bec66)
>> 2 Nodes configured.
>> 1 Resources configured.
>> ============
>>
>> Node: lx11 (19469e0b-4e6f-4688-b827-863b2d2bec66): online
>> Node: lx10 (0c6792aa-4a4f-467a-964e-15efa08bd7b5): online
>
> ahhhh!
>
> so its not actually showing the resource, just giving the wrong "count"
>
> ok, i can probably do something about that (though not in time for SP1
> which just went gold)
>
>
>>
>> Im running SLES 10 and the version of heartbeat is:
>>
>> heartbeat-pils-2.0.7-1.2
>> heartbeat-ldirectord-2.0.7-1.2
>> yast2-heartbeat-2.13.10-1.3
>> heartbeat-stonith-2.0.7-1.2
>> heartbeat-cmpi-2.0.7-1.2
>> heartbeat-2.0.7-1.2
>>
>>
>> /Claes
>>
>> Claes Lindvall skrev:
>> >
>> > Hi
>> >
>> > I will post an output from cibadmin -Ql and from the crm_mon tomorrow
>> > - I dont have it here in my home.
>> > In the meanwhile here is what I do:
>> >
>> > I fire up my cluster and by monitoring the /var/log/messages and with
>> > "crm_mon -i 2"
>> > I wait for it to get online. Then I add a resource with "cibadmin -C
>> > -o resource -x <xml-fil>"
>> > It adds to the cluster starts up nice.
>> > "crm_mon -i 2" shows me that the resource was added - now I have "one"
>> > resource in my cluster.
>> > I stop it with "crm_resource -r <resource-name> -p target_role -v
>> > stopped.
>> > I goes down and then I remove the resource with "cibadmin -D -o
>> > resource -x <the-same-xml-file-which-I-used-to-create>
>> > I check with "crm_resource -L" to be sure that it is gone from my
>> > cluster, and gone it is.
>> > But my "crm_mon -i 2" is till showing the there is "one" resource in
>> > my cluster.
>> > I then run the command "crm_resource -C -r <resource>" and then my
>> > "crm_mon -i 2" is showing
>> > that there is not any resources in my cluster.
>> >
>> > More info will come tomorrow...
>> >
>> > /Claes Lindvall
>> >
>> >
>> > Andrew Beekhof skrev:
>> >> On 6/4/07, matilda matilda <[EMAIL PROTECTED]> wrote:
>> >>> Hi Claes,
>> >>>
>> >>> interestingly you can delete a ressource with crm_resource, but you
>> >>> can't add
>> >>> one.
>> >>
>> >> its the difference between:
>> >> delete name
>> >> and
>> >> add name, class, type, parameters, operations, meta-options, etc
>> etc
>> >>
>> >>> When I delete one with crm_resource everything seems to go right.
>> >>>
>> >>> Andrew: Is the phenomena mentioned by Claes a bug? Or simple a
>> >>> missunderstanding
>> >>> of us?
>> >>
>> >> if the resources are indeed stopped - then its a bug
>> >>
>> >> can you paste the output of crm_mon that is incorrect?
>> >> and include the result of "cibadmin -Ql" (as an attachment) from the
>> >> same time.
>> >> _______________________________________________
>> >> 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
>> >
>> >
>>
>>
>> <cib generated="true" admin_epoch="0" epoch="1" num_updates="20"
>> have_quorum="true" num_peers="2" ccm_transition="2"
>> cib_feature_revision="1.3"
>> dc_uuid="19469e0b-4e6f-4688-b827-863b2d2bec66">
>> <configuration>
>> <crm_config/>
>> <nodes>
>> <node id="19469e0b-4e6f-4688-b827-863b2d2bec66" uname="lx11"
>> type="normal"/>
>> <node id="0c6792aa-4a4f-467a-964e-15efa08bd7b5" uname="lx10"
>> type="normal"/>
>> </nodes>
>> <resources/>
>> <constraints/>
>> </configuration>
>> <status>
>> <node_state id="19469e0b-4e6f-4688-b827-863b2d2bec66"
>> uname="lx11" crmd="online" crm-debug-origin="do_update_resource"
>> shutdown="0" in_ccm="true" ha="active" join="member" expected="member">
>> <lrm id="19469e0b-4e6f-4688-b827-863b2d2bec66">
>> <lrm_resources>
>> <lrm_resource id="IP1" type="IPaddr" class="ocf"
>> provider="heartbeat">
>> <lrm_rsc_op id="IP1_monitor_0" operation="monitor"
>> crm-debug-origin="do_update_resource"
>> transition_key="3:b1c0df56-39be-43bf-ae85-fb57f8664704"
>> transition_magic="4:7;3:b1c0df56-39be-43bf-ae85-fb57f8664704"
>> call_id="2" crm_feature_set="1.0.6" rc_code="7" op_status="4"
>> interval="0" op_digest="91ce11f11140997eec0ca8ab4b1ad709"/>
>> <lrm_rsc_op id="IP1_start_0" operation="start"
>> crm-debug-origin="do_update_resource"
>> transition_key="3:b1c0df56-39be-43bf-ae85-fb57f8664704"
>> transition_magic="0:0;3:b1c0df56-39be-43bf-ae85-fb57f8664704"
>> call_id="3" crm_feature_set="1.0.6" rc_code="0" op_status="0"
>> interval="0" op_digest="91ce11f11140997eec0ca8ab4b1ad709"/>
>> <lrm_rsc_op id="IP1_stop_0" operation="stop"
>> crm-debug-origin="do_update_resource"
>> transition_key="4:b1c0df56-39be-43bf-ae85-fb57f8664704"
>> transition_magic="0:0;4:b1c0df56-39be-43bf-ae85-fb57f8664704"
>> call_id="4" crm_feature_set="1.0.6" rc_code="0" op_status="0"
>> interval="0" op_digest="91ce11f11140997eec0ca8ab4b1ad709"/>
>> </lrm_resource>
>> </lrm_resources>
>> </lrm>
>> <transient_attributes id="19469e0b-4e6f-4688-b827-863b2d2bec66">
>> <instance_attributes
>> id="status-19469e0b-4e6f-4688-b827-863b2d2bec66">
>> <attributes>
>> <nvpair
>> id="status-19469e0b-4e6f-4688-b827-863b2d2bec66-probe_complete"
>> name="probe_complete" value="true"/>
>> </attributes>
>> </instance_attributes>
>> </transient_attributes>
>> </node_state>
>> <node_state id="0c6792aa-4a4f-467a-964e-15efa08bd7b5"
>> uname="lx10" crmd="online" crm-debug-origin="do_update_resource"
>> shutdown="0" in_ccm="true" ha="active" join="member" expected="member">
>> <lrm id="0c6792aa-4a4f-467a-964e-15efa08bd7b5">
>> <lrm_resources>
>> <lrm_resource id="IP1" type="IPaddr" class="ocf"
>> provider="heartbeat">
>> <lrm_rsc_op id="IP1_monitor_0" operation="monitor"
>> crm-debug-origin="do_update_resource"
>> transition_key="3:b1c0df56-39be-43bf-ae85-fb57f8664704"
>> transition_magic="4:7;3:b1c0df56-39be-43bf-ae85-fb57f8664704"
>> call_id="2" crm_feature_set="1.0.6" rc_code="7" op_status="4"
>> interval="0" op_digest="91ce11f11140997eec0ca8ab4b1ad709"/>
>> </lrm_resource>
>> </lrm_resources>
>> </lrm>
>> <transient_attributes id="0c6792aa-4a4f-467a-964e-15efa08bd7b5">
>> <instance_attributes
>> id="status-0c6792aa-4a4f-467a-964e-15efa08bd7b5">
>> <attributes>
>> <nvpair
>> id="status-0c6792aa-4a4f-467a-964e-15efa08bd7b5-probe_complete"
>> name="probe_complete" value="true"/>
>> </attributes>
>> </instance_attributes>
>> </transient_attributes>
>> </node_state>
>> </status>
>> </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
>
>
_______________________________________________
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
