Hi, On Wed, Jan 20, 2010 at 09:45:46PM +0100, Markus M. wrote: > Dejan Muhamedagic wrote: > > >>Operations' defaults (advisory minimum): > >> > >> stop timeout=100 > >> > >>So it seems for the "stop" action there is a timeout of 100 seconds > >>defined. But at cluster shutdown i can see this in the ha-debug log: > > > >It says above that it's "advisory minimum" (the wording should > >probably be changed). You have to set the timeouts yourself. > > Sorry, maybe i've misunderstood something... i thought _i've set the > timeout_ by making the ocf resource agent meta-data function > returning the value of 100 seconds for the stop action? Is there > another place to set the timeout for the stop action of this ra?
Yes, in the cluster configuration. Like this: primitive rsc_c001n07 ocf:heartbeat:IPaddr \ params ip="127.0.0.16" cidr_netmask="32" \ op stop timeout="100s" Thanks, Dejan > The timeout is occuring after 20 seconds: > > >>Jan 18 14:31:35 node1 crmd: [12844]: info: te_rsc_command: > >>Initiating action 5: stop oracle_primary_stop_0 on node1 (local) > ... > >>Jan 18 14:31:55 node1 lrmd: [12841]: WARN: oracle_primary:stop > >>process (PID 14386) timed out (try 1). Killing with signal SIGTERM > >>(15). > > Regards > Markus > > _______________________________________________ > Pacemaker mailing list > Pacemaker@oss.clusterlabs.org > http://oss.clusterlabs.org/mailman/listinfo/pacemaker _______________________________________________ Pacemaker mailing list Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker