Default_action_timeout did not seem to make a difference, but changing the cluster-delay did manage to change the timeout of the stonith. This: <nvpair value="120s" id="cluster-delay" name="cluster-delay"/> Gave me a 60s timeout waiting for the Stonith (version 2.0.8). But unfortunately the problem was elsewhere :-(
Thank for putting me on the right track Dave. > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of > Dave Blaschke > Sent: May 2, 2007 2:30 PM > To: General Linux-HA mailing list > Subject: Re: [Linux-HA] External STONITH timeout > > Benjamin Lawetz wrote: > > Hi all, > > > > I've written an external stonith plugin for a Sentry > power switch. > > It works fine from the command line (save that it takes 25s for the > > ssh to login). This causes problems when the STONITH tries > to kill the > > other server. From the logs I can tell the stonith times > out after 30s: > > > > tengine: [25705]: info: te_fence_node: Executing reboot fencing > > operation > > (51) on mysql1.domain.com (timeout=30000) > > > > I've been trying to change that 30s timeout to something > larger, but > > can't figure out where to set this in the cib. Any ideas ?** > > > Have you tried setting/changing the *default_action_timeout > *attribute in the cluster_property_set of crm_config? I'm > not an expert in this area, but the fencing operation timeout > seems to be half this value (fencing op timeout = > default_action_timeout/2) on the two clusters I have... > > Here's the relevant section: > > > > <clone id="DoFencing"> > > <instance_attributes id="DoFencing_clone_attr"> > > <attributes> > > <nvpair id="DoFencing_clone_max" > name="clone_max" value="2"/> > > <nvpair id="DoFencing_clone_node_max" > name="clone_node_max" > > value="1"/> > > </attributes> > > </instance_attributes> > > <primitive id="child_DoFencing" class="stonith" > > type="external/sentry" provider="heartbeat"> > > <operations> > > <op id="DoFencing_monitor" name="monitor" > interval="120s" > > timeout="60s" prereq="nothing"/> > > <op name="DoFencing_start" timeout="120s" > prereq="nothing" > > id="fb449d3f-319c-4bfe-967f-XXXXXXXXXX"/> > > </operations> > > <instance_attributes id="DoFencing_sentry_standard_attr"> > > <attributes> > > <nvpair id="DoFencing_ip" name="ip" > value="10.10.10.140"/> > > </attributes> > > </instance_attributes> > > <instance_attributes id="DoFencing_sentry_mysql2_attr"> > > <rule id="rule_stonith_parameters_for_mysql2"> > > <expression > > id="rule_stonith_parameters_for_mysql2_expression" > attribute="#uname" > > operation="eq" value="mysql2.domain.com"/> > > </rule> > > <attributes> > > <nvpair > id="rule_stonith_parameters_for_mysql2_userid" > > name="userid" value="user2"/> > > <nvpair > id="rule_stonith_parameters_for_mysql2_passwd" > > name="passwd" value="pass2"/> > > </attributes> > > </instance_attributes> > > <instance_attributes id="DoFencing_sentry_mysqql1_attr"> > > <rule id="rule_stonith_parameters_for_mysql1"> > > <expression > > id="rule_stonith_parameters_for_mysql1_expression" > attribute="#uname" > > operation="eq" value="mysql1.domain.com"/> > > </rule> > > <attributes> > > <nvpair > id="rule_stonith_parameters_for_mysql1_userid" > > name="userid" value="user1"/> > > <nvpair > id="rule_stonith_parameters_for_mysql1_passwd" > > name="passwd" value="pass1"/> > > </attributes> > > </instance_attributes> > > </primitive> > > </clone> > > > > > > Thanks for any help > > > > > _______________________________________________ > Linux-HA mailing list > Linux-HA@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@lists.linux-ha.org http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
