Frank,
Congratulations on getting your stonith config to work. Unfortunately,I've not
been so lucky or I don't understand stonith very well. I've done the exact same
configuration as you've but for some reason , the stonith RA doesn't start at
all. I'm using version 2.0.8 and the ssh stonith agent to test my
configuration. I too have two nodes : active and standby, where I want active
to stonith standby and vice versa.
I've attached a snapshot of my stonith configuration for you to look at . I
would really appreciate if you could point out any mistakes I might have made...
<crm_config>
<cluster_property_set id="cib-bootstrap-options">
<attributes>
<nvpair id="cib-bootstrap-options-default-resource-stickiness"
name="default-resource-stickiness" value="INFINITY"/>
<nvpair id="cib-bootstrap-options-stonith" name="stonith-enabled"
value="TRUE"/>
<nvpair id="cib-bootstrap-options-quorum" name="no-quorum-policy"
value="IGNORE"/>
</attributes>
</cluster_property_set>
</crm_config>
<nodes>
<node id="6f6d5305-43e3-46f9-a8d7-7966218bab0b" uname="standby"
type="normal"/>
<node id="bf83d809-e951-4c04-b605-28b5ead6ccfe" uname="active"
type="normal"/>
</nodes>
<resources>
...
...
<clone id="stonith_active">
<instance_attributes id="stonith_active_attr">
<attributes>
<nvpair id="stonith_active_clone_max" name="clone_max" value="1"/>
<nvpair id="stonith_active_clone_node_max" name="clone_node_max"
value="1"/>
</attributes>
</instance_attributes>
<primitive id="Stonith_active" class="stonith" type="external/rsh"
provider="heartbeat">
<operations>
<op id="4" name="start" timeout="10s" prereq="nothing"/>
<op id="5" name="monitor" timeout="5s" interval="15s"/>
</operations>
<instance_attributes id="rsh_active_instance_attr">
<attributes>
<nvpair id="rsh_attr_active" name="hostlist" value="active"/>
</attributes>
</instance_attributes>
</primitive>
</clone>
<clone id="stonith_standby">
<instance_attributes id="stonith_standby_attr">
<attributes>
<nvpair id="stonith_standby_clone_max" name="clone_max" value="1"/>
<nvpair id="stonith_standby_clone_node_max" name="clone_node_max"
value="1"/>
</attributes>
</instance_attributes>
<primitive id="Stonith_standby" class="stonith" type="external/rsh"
provider="heartbeat">
<operations>
<op id="6" name="start" timeout="10s" prereq="nothing"/>
<op id="7" name="monitor" timeout="5s" interval="15s"/>
</operations>
<instance_attributes id="rsh_standby_instance_attr">
<attributes>
<nvpair id="rsh_attr_standby" name="hostlist" value="standby"/>
</attributes>
</instance_attributes>
</primitive>
</clone>
</resources>
<constraints>
<rsc_location id="proxy_stonith_active_rsc_location"
rsc="stonith_active">
<rule id="prefered_location_proxy_stonith_active_rsc" score="INFINITY">
<expression id="prefered_location_proxy_stonith_active_rsc_expr"
attribute="#uname" operation="eq" value="standby"/>
</rule>
</rsc_location>
<rsc_location id="proxy_stonith_standby_rsc_location"
rsc="stonith_standby">
<rule id="prefered_location_proxy_stonith_standby_rsc"
score="INFINITY">
<expression id="prefered_location_proxy_stonith_standby_rsc_expr"
attribute="#uname" operation="eq" value="active"/>
</rule>
</rsc_location>
</constraints>
Regards,
Abhi.
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Frank
Sent: Wednesday, November 21, 2007 1:04 PM
To: [email protected]
Subject: [Linux-HA] Re: Linux-HA Digest, Vol 48, Issue 69
> Date: Tue, 20 Nov 2007 12:25:28 +0100
> From: Andrew Beekhof <[EMAIL PROTECTED]>
> Subject: Re: [Linux-HA] confused about setting drac5 stonith
> To: General Linux-HA mailing list <[email protected]>
> Message-ID: <[EMAIL PROTECTED]>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed; delsp=yes
>
>
> On Nov 20, 2007, at 11:48 AM, Frank wrote:
>
>
>> Hi,
>> I've seen some discussions about this, but I'm still confused.
>> I'm using the drac5 stonith plugin from Thomas Paschy (thanks
>> thomas) but I don't know how to cofigure it to work fine.
>>
>> We have a cluster with 2 nodes, each one with its public address, and
>> each one with a drac5 device with a private address; le'ts call them
>> node1, node2, node1_drac and node2_drac. So node1 can make a reset to
>> node2 connenting to node2_drac, and node2 can make a reset to node1
>> connenting to node1_drac
>>
>> So we have created two stonith resources called stonith_node1_drac
>> (with node1_drac address) and stonith_node2_drac (with node2_drac
>> address); stonith_node1_drac needs to run on node node2 because it is
>> node2 which can reboot node1, an stonith_node2_drac needs to run on
>> node node1 because it is node1 which can reboot node2
>>
>> If we started this way, they starts ok. But when we forced a stonith
>> condition on node2 (killing heartbeat) node 1 is not able to reset
>> node2; we got this on logs:
>>
>> pengine[8955]: 2007/11/20_11:05:05 WARN: stage6: Scheduling Node
>> kripton for STONITH
>> pengine[8955]: 2007/11/20_11:05:05 info: native_stop_constraints:
>> drac_argon_stop_0 is implicit after kripton is fenced
>> pengine[8955]: 2007/11/20_11:05:05 WARN: process_pe_message:
>> Transition 80: WARNINGs found during PE processing. PEngine Input
>> stored in: /var/lib/heartbeat/pengine/pe-warn-75.bz2
>> pengine[8955]: 2007/11/20_11:05:05 info: process_pe_message:
>> Configuration WARNINGs found during PE processing. Please run
>> "crm_verify -L" to identify issues.
>> stonithd[3978]: 2007/11/20_11:05:35 ERROR: Failed to STONITH the node
>> kripton: optype=RESET, op_result=TIMEOUT
>> tengine[8954]: 2007/11/20_11:05:35 info: tengine_stonith_callback:
>> call=-43, optype=1, node_name=kripton, result=2, node_list=,
>> action=8:80:84a50e41-ffda-4c9a-959a-76a61919413a
>> tengine[8954]: 2007/11/20_11:05:35 ERROR: tengine_stonith_callback:
>> Stonith of kripton failed (2)... aborting transition.
>>
>> (kripton is node2 and argon is node1) It seems that there is
>> something messy with the addresses.
>> Can anyone help?
>>
>
> not without logs, configurations and the version your using
>
>
We are using heartbeat 2.1.2
I think I have understood the problem. When node1 wants to stonith node2 and
asks its stonith device which hosts it can stonith, device answers it can
stonith node2_drac, but not node2; so node1 doesn't know how to stonith node2 I
fixed the problem adding an extra parameter "hostname" to drac5 plugin so it
can returns hostname when asked for which host it fences and it uses ipaddr to
access to the drac of the host (original drac5 plugin have only ipaddr,login
and password parameters). And it works!
But I suppose that there is a similar problem witch drac3 plugin included in
heatbeat; so how can people use it ? Does anybody know?
Frank
--
Aquest missatge ha estat analitzat per MailScanner a la cerca de virus i
d'altres continguts perillosos, i es considera que està net.
For all your IT requirements visit: http://www.transtec.co.uk
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
The information contained in this electronic message and any attachments to
this message are intended for the exclusive use of the addressee(s) and may
contain proprietary, confidential or privileged information. If you are not the
intended recipient, you should not disseminate, distribute or copy this e-mail.
Please notify the sender immediately and destroy all copies of this message and
any attachments.
WARNING: Computer viruses can be transmitted via email. The recipient should
check this email and any attachments for the presence of viruses. The company
accepts no liability for any damage caused by any virus transmitted by this
email.
www.wipro.com
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
