You don't think that might be a little short? Any failure that happened more than 10s is going to be ignored, leading to the pengine message you saw.
On 16 Oct 2014, at 12:21 am, Sahil Aggarwal <sahilaggarw...@gmail.com> wrote: > failure timeout for resource is 10s. > > On Wed, Oct 15, 2014 at 2:51 AM, Andrew Beekhof <and...@beekhof.net> wrote: > > On 15 Oct 2014, at 4:23 am, Sahil Aggarwal <sahilaggarw...@gmail.com> wrote: > > > > > Hello Team Pacemaker, > > > > I am facing a constant issue with Pacemaker, it does not restart the > > Service even when he knows that the Service is down. It generates a message > > saying "Ignoring Expired Failure" for the service. > > What is the failure timeout set to? > > > Pacemaker and Corosync version are given below. OS CentOS 6.2 > > > > corosync-1.4.1-4.el6_2.2.x86_64 pacemaker-1.1.9-2.el6.x86_64 > > > > Log which pengine provide is: > > > > pengine[45232]: notice: unpack_rsc_op: Ignoring expired failure > > (calculated) Server_last_failure_0 (rc=7, > > magic=0:7;14:5699:0:459093cc-f3a1-483b-b853-53a1d9791361) > > > > Some more info is: > > > > 1.This is a two node cluster. There is time difference of 10 min b/w the > > two nodes. > > > > > > -- > > Regards, > > Sahil > > Mobile - 09467607999 > > fbAddress-www.facebook.com/SahilAggarwalg > > > > > -- > Sahil > Mobile - 09467607999 > fbAddress-www.facebook.com/SahilAggarwalg
signature.asc
Description: Message signed with OpenPGP using GPGMail
_______________________________________________ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org