Hi, On Wed, Oct 10, 2007 at 05:58:08PM +0200, Cavailles, Philippe wrote: > > A compter du 1er juin 2007, l'adresse de messagerie de votre correspondant > ci-dessus comme celles de tous les collaborateurs des sociétés françaises > d'Egis changent pour le format unique suivant : [EMAIL PROTECTED] > Merci de modifier vos annuaires en conséquence. > ------------------------------------- > >From 1st June 2007, your above correspondant and all staff of Egis Group > >French companies have a new e-mail address based on the following format: > >[EMAIL PROTECTED] > Please update your contact database accordingly. > > > Dear all, > I am using HAv2 (2.1.2-4) with Linux RedHat ES4 on a DELL PowerEdge that > implement an IPMI interface. > I want to configure an IPMI stonith agent that is able to reboot a failed > node, but I am facing some configuration > problems. > > In CIB "crm_config" part I have set "stonith-enabled" and > "always-stonith-failed-nodes" parameter to "true" as specified
This parameter doesn't exist... > in http://www.linux-ha.org/NodeFencingImplementation, chapter > "STONITHing failed nodes in general". though it does on the web page. Perhaps it's yet to be implemented ;-) NB: Always run crm_verify on your configuration. > ---------------------------------------------------------------------- > <crm_config> > <cluster_property_set id="cluster_property_set"> > <attributes> > <nvpair id="transition-idle-timer" name="transition-idle-timer" > value="60s"/> > <nvpair id="symetric-cluster" name="symetric-cluster" value="true"/> > <nvpair id="stonith-enabled" name="stonith-enabled" value="true"/> > <nvpair id="no-quorum-policy" name="no-quorum-policy" value="stop"/> > <nvpair id="default-resource-stickiness" name="default-resource-stickiness" > value="INFINITY"/> > <nvpair id="is-managed-default" name="is-managed-default" value="true"/> > <nvpair id="stop-orphan-resources" name="stop-orphan-resources" > value="true"/> > <nvpair id="stop-orphan-actions" name="stop-orphan-actions" value="true"/> > <nvpair id="always-stonith-failed-nodes" name="always-stonith-failed-nodes" > value="true"/> > </attributes> > </cluster_property_set> > </crm_config > ---------------------------------------------------------------------- > > I am using the external stonith pluging provided by Martin > (http://lists.community.tummy.com/pipermail/linux-ha-dev/2007-February/013989.html) > and I have created two resources with a location constraint in > order to force each resource to run on a separate node. The > plugin seems to works correctly, I am able to check the power > status of each node (monitor action is executed periodically), > but, when a note become "offline" heartbeat doesn't request the > stonith plugin to stop and restart the failed node. What do you mean by "offline"? > ---------------------------------------------------------------------- > <primitive id="cluster1-stonith" class="stonith" provider="heartbeat" > type="external/ipmi_stonith" resource_stickiness="INFINITY"> > <operations> > <op id="op-cluster1-stonith-1" name="stop" timeout="60s"/> > <op id="op-cluster1-stonith-2" name="start" timeout="30s"/> > <op id="op-cluster1-stonith-3" name="monitor" timeout="5s" interval="10s"/> > </operations> > <instance_attributes id="c4f5a286-5dca-459e-90d6-ac649068b97f"> > <attributes> > <nvpair id="ia-cluster1-stonith-0" name="target_role" value="started"/> > <nvpair id="ia-cluster1-stonith-1" name="hostname" value="cluster1"/> > <nvpair id="ia-cluster1-stonith-2" name="ipaddr" value="192.168.31.220"/> > <nvpair id="ia-cluster1-stonith-3" name="userid" value="root"/> > <nvpair id="ia-cluster1-stonith-4" name="passwd" value="xxxxx"/> > </attributes> > </instance_attributes> > </primitive> > > <primitive id="cluster2-stonith" class="stonith" provider="heartbeat" > type="external/ipmi_stonith" resource_stickiness="INFINITY"> > <operations> > <op id="op-cluster2-stonith-1" name="stop" timeout="60s"/> > <op id="op-cluster2-stonith-2" name="start" timeout="30s"/> > <op id="op-cluster2-stonith-3" name="monitor" timeout="5s" interval="10s"/> > </operations> > <instance_attributes id="6a60de8a-9e90-4a9e-bd83-a4d5e1174619"> > <attributes> > <nvpair id="ia-cluster2-stonith-0" name="target_role" value="started"/> > <nvpair id="ia-cluster2-stonith-1" name="hostname" value="cluster2"/> > <nvpair id="ia-cluster2-stonith-2" name="ipaddr" value="192.168.31.221"/> > <nvpair id="ia-cluster2-stonith-3" name="userid" value="root"/> > <nvpair id="ia-cluster2-stonith-4" name="passwd" value="xxxxx"/> > </attributes> > </instance_attributes> > </primitive> > ---------------------------------------------------------------------- > ---------------------------------------------------------------------- > <rsc_location id="cluster1-stonith-placement" rsc="cluster1-stonith"> > <rule id="ri-cluster1-stonith-placement-1" score="INFINITY"> > <expression id="ri-ex-cluster1-stonith-placement-1" value="cluster2" > attribute="#uname" operation="eq"/> > </rule> > <rule id="ri-cluster1-stonith-placement-2" score="-INFINITY"> > <expression id="ri-ex-cluster1-stonith-placement-2" value="cluster2" > attribute="#uname" operation="ne"/> > </rule> > </rsc_location> > > <rsc_location id="cluster2-stonith-placement" rsc="cluster2-stonith"> > <rule id="ri-cluster2-stonith-placement-1" score="INFINITY"> > <expression id="ri-ex-cluster2-stonith-placement-1" value="cluster1" > attribute="#uname" operation="eq"/> > </rule> > <rule id="ri-cluster2-stonith-placement-2" score="-INFINITY"> > <expression id="ri-ex-cluster2-stonith-placement-2" value="cluster1" > attribute="#uname" operation="ne"/> > </rule> > </rsc_location> > ---------------------------------------------------------------------- If you have only two nodes, then the first rule in both rsc_locations suffices. > Could you advice? In general, Heartbeat won't stonith a cooperating node, i.e. a node with which we can communicate. Can you also post logs? Thanks, Dejan > > Thank you, > Best regards, > Philippe > > > > > Content-Description: philippe.cavailles.vcf > begin:vcard > fn:Philippe CAVAILLES > n:CAVAILLES;Philippe > org:egisavia > adr;quoted-printable:BP 20603;;4BIS rue Paul Mespl=C3=A9;TOULOUSE > CEDEX1;;31106;FRANCE > email;internet:[EMAIL PROTECTED] > tel;work:(33)5 62 24 56 17 > x-mozilla-html:TRUE > version:2.1 > end:vcard > > Ce message et toutes les pi?ces jointes (ci-apr?s le ??message??) sont > confidentiels et ?tablis ? l?intention exclusive > de ses destinataires. Toute utilisation de ce message non conforme ? sa > destination, toute diffusion ou toute publication, > totale ou partielle, est interdite, sauf autorisation expresse. Si vous > recevez ce message par erreur, merci de le > d?truire sans en conserver de copie et d?en avertir imm?diatement > l?exp?diteur. Internet ne permettant pas de garantir > l?int?grit? de ce message, EGIS SA et ses filiales d?clinent toute > responsabilit? au titre de ce message s?il a ?t? > modifi?, alt?r?, d?form? ou falsifi?. Par ailleurs et malgr? toutes les > pr?cautions prises pour ?viter la pr?sence de virus > dans nos envois, nous vous recommandons de prendre, de votre c?t?, les > mesures permettant d'assurer la non-introduction > de virus dans votre syst?me informatique. > > > This email message and any attachments (?the email?) are confidential and > intended only for the recipient(s) indicated. > If you are not an intented recipient, please be advised that any use, > dissemination, forwarding or copying of this email > whatsoever is prohibited without EGIS SA and its subsidiaries's prior written > consent. If you have received this email > in error, please delete it without saving a copy and notify the sender > immediately. Internet emails are not necessarily > secured, and declines responsibility for any changes that may have been made > to this email after it was sent.While we > take all reasonable precautions to ensure that viruses are not transmitted > via emails, we recommend that you take your > own measures to prevent viruses from entering your computer system. > _______________________________________________ > 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
