Hi, On Thu, Jul 16, 2009 at 10:50:27AM +0200, Andrew Beekhof wrote: > On Wed, Jul 15, 2009 at 4:31 PM, Alain.Moulle<[email protected]> wrote: > > Hi, > > > > I've a declared an OCF ?RA and test the start , stop thanks to hb_gui. > > When I start the resource , it starts immediately. > > Then if I ask for stopping, it takes 120s to begin the stop, but stop is > > executed and successful. > > Except if I ask for stopping just after a periodic monitoring issue, > > in this case the stop is taken in account imediately. > > > > I don't see anything in my time parameters which could explain this > > behavior, > > I do. > > > <op id="res-mv-01-op-monitor-180" interval="60" name="monitor" > > start-delay="120" timeout="30"/> > > The first monitor is scheduled to run 120s after the start completes > (are you sure you need this?) and must complete before any further > operations are executed for the resource. This is why the stop takes > so long.
The wonderful world of providing defaults for everything ;-> I'd suggest to (at least) make this feature of the GUI optional and non-default, i.e. filling out various timing parameters. Thanks, Dejan > > is it normal or is it abnormal ? > > > > My timers for the resources declaration are given below. > > By the way, the crm_verify -L returns ?: > > ? ?[r...@devha0 scriptsForHA_ST]# crm_verify -L -V > > ? ?crm_verify[23924]: 2009/07/15_16:35:34 WARN: native_color: Resource > > res-mv-01 cannot run anywhere > > ? ?Warnings found during check: config may not be valid > > and I don't see why ... ??? > > > > <resources> > > ?<primitive class="ocf" id="res-mv-01" provider="pacemaker" type="kvm"> > > ? ?<meta_attributes id="res-mv-01-meta_attributes"> > > ? ? ?<nvpair id="res-mv-01-meta_attributes-target-role" > > name="target-role" value="Started"/> > > ? ?</meta_attributes> > > ? ?<operations id="res-mv-01-operations"> > > ? ? <op id="res-mv-01-op-start-0" interval="0" name="start" timeout="60"/> > > ? ? <op id="res-mv-01-op-stop-0" interval="0" name="stop" timeout="60"/> > > ? ? <op id="res-mv-01-op-monitor-180" interval="60" name="monitor" > > start-delay="120" timeout="30"/> > > ? </operations> > > ? ? ?<instance_attributes id="res-mv-01-instance_attributes"> > > ? ? ? ?<nvpair id="res-mv-01-instance_attributes-ip" name="ip" > > value="101.1.2.32"/> > > ? ? ? ?<nvpair id="res-mv-01-instance_attributes-domainname" > > name="domainname" value="domaine61"/> > > ? ? ?</instance_attributes> > > ?</primitive> > > </resources> > > > > Thanks for help > > Alain > > _______________________________________________ > > 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
