[Linux-HA] Failback

[John R Mocho]

Make sure you include the -D flag to clear the fail-count, or
-G to query the fail-count value -- along with the -U/-u and -r options.
Otherwise, the command will fail due to not having anything to do.

John.

On Tue, 12 Sep 2006, Zachár Balázs wrote:

> Date: Tue, 12 Sep 2006 19:47:53 +0200
> From: Zachár Balázs <zachar at direkt-kfki.hu>
> Reply-To: General Linux-HA mailing list <linux-ha at lists.linux-ha.org>
> To: General Linux-HA mailing list <linux-ha at lists.linux-ha.org>
> Subject: Re: [Linux-HA] Failback
> 
> Yes I thought that, but when I checked I got error messages... Now I
> check it again:
>
> a-linux:~ # crm_failcount -U a-linux -r group_1
> crm_failcount[6945]: 2006/09/12_19:42:30 ERROR: main:crm_attribute.c
> Triggered non-fatal assert at crm_attribute.c:344 : attr_value != NULL
> Error performing operation: Required data for this CIB API call not found
> a-linux:~ #
>
>
>
> John R Mocho írta:
>>
>> Have you checked the fail-count counter for that resource?
>>
>> check out the crm_failcount command...
>>
>> On Tue, 12 Sep 2006, [ISO-8859-2] Zachár Balázs wrote:
>>
>>> Date: Tue, 12 Sep 2006 18:15:35 +0200
>>> From: "[ISO-8859-2] Zachár Balázs" <zachar at direkt-kfki.hu>
>>> Reply-To: General Linux-HA mailing list <linux-ha at lists.linux-ha.org>
>>> To: General Linux-HA mailing list <linux-ha at lists.linux-ha.org>
>>> Subject: [Linux-HA] Failback
>>>
>>> Hello!
>>>
>>> I have an Active/Passive cluster with heartbeat v2. After I generate an
>>> error to test (ifdown eth0 and there is an alias IPaddress whics is
>>> managed with the standard OCF RA), the cluster is works and the
>>> resources are start on b-node. After that I "repair" the a-node (ifup
>>> eth0) and I would like to migrate the resources back to the a-node whith
>>> this command on b-node:
>>>
>>> #crm_resource -M -r group_1
>>>
>>> After that the resources stop on b-node but not start on a-node... If i
>>> do this on b-node:
>>>
>>> #crm_resource -U -r group_1
>>>
>>> They start again on b-node.
>>>
>>> Now I do this on a-node:
>>>
>>> #crm_resource -W -r group_1
>>> resource group_1 not running
>>>
>>> now i do thison a-node:
>>> #cibadmin -S
>>> #crm_resource -W -r group_1
>>> resource group_1 is running on: b-node
>>>
>>>
>>> OK the CIB is ok, but if i would like to migrate back again the
>>> resources to the a-node, they still stop on b-node but not start on
>>> a-node...
>>>
>>> Why? I think a-node not active or something...
>>>
>>>
>>> Sorry my poor english
>>> Thanks,
>>> Balázs
>>> _______________________________________________
>>> 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
>
> _______________________________________________
> 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
>