Original Message-
> From: Andrew Beekhof [mailto:and...@beekhof.net]
> Sent: Wednesday, August 15, 2012 4:26 PM
> To: The Pacemaker cluster resource manager
> Subject: Re: [Pacemaker] Expired fail-count doesn't get cleaned up.
>
> On Thu, Aug 16, 2012 at 9:15 AM, Jan
ffect, right?
Thanks,
Jane
-Original Message-
From: Andrew Beekhof [mailto:and...@beekhof.net]
Sent: Wednesday, August 15, 2012 4:26 PM
To: The Pacemaker cluster resource manager
Subject: Re: [Pacemaker] Expired fail-count doesn't get cleaned up.
On Thu, Aug 16, 2012 at 9:15
sage-
> From: Andrew Beekhof [mailto:and...@beekhof.net]
> Sent: Wednesday, August 15, 2012 3:02 AM
> To: The Pacemaker cluster resource manager
> Subject: Re: [Pacemaker] Expired fail-count doesn't get cleaned up.
>
> On Wed, Aug 15, 2012 at 3:01 PM, Jane Du (jadu) wrot
manager
Subject: Re: [Pacemaker] Expired fail-count doesn't get cleaned up.
On Wed, Aug 15, 2012 at 3:01 PM, Jane Du (jadu) wrote:
> Hi Andrew:
>
> The fail-count is not cleaned up in my setup after 2s.
Based on some more information from David, it appears that there was
one more bu
n S_POLICY_ENGINE -> S_TRANSITION_ENGINE [ input=I_PE_SUCCESS
> cause=C_IPC_MESSAGE origin=handle_response ]
> Aug 14 21:13:40 vm-mgmt-1 crmd: [28547]: info: unpack_graph: Unpacked
> transition 4: 2 actions in 2 synapses
> Aug 14 21:13:40 vm-mgmt-1 crmd: [28547]: info: do_te_invok
: Andrew Beekhof [mailto:and...@beekhof.net]
Sent: Monday, August 13, 2012 7:48 PM
To: mario.penn...@gmail.com; The Pacemaker cluster resource manager
Subject: Re: [Pacemaker] Expired fail-count doesn't get cleaned up.
On Tue, Aug 14, 2012 at 10:15 AM, Mario Penners wrote:
> Hi David,
On 8/13/12 8:01 PM, Andrew Beekhof wrote:
You might be experiencing:
+ David Vossel (5 months ago) 9263480: Low: pengine: cl#5025 -
Automatically clear failures when resource configuration changes.
But if you send us a crm_report tarball coving the period during which
you had problems, we can
On Tue, Aug 14, 2012 at 10:15 AM, Mario Penners wrote:
> Hi David,
>
> I understand the failcount only gets reset after a probe is run. So you
> need to give it a "crm resource reprobe" for the expiry timer to be
> evaluated.
Not for recent versions of 1.1
>
> However: I do NOT know, when the
Hi David,
I understand the failcount only gets reset after a probe is run. So you
need to give it a "crm resource reprobe" for the expiry timer to be
evaluated.
However: I do NOT know, when the probes are run (I see them in my logs
only after failover or start/stop actions are taking place, but
On Tue, Jul 31, 2012 at 7:36 PM, David Coulson wrote:
> I'm running RHEL6 with the tech preview of pacemaker it ships with. I've a
> number of resources which have a failure-timeout="60", which most of the
> time does what it is supposed to.
>
> Last night a resource failed, which was part of a cl
I'm running RHEL6 with the tech preview of pacemaker it ships with. I've
a number of resources which have a failure-timeout="60", which most of
the time does what it is supposed to.
Last night a resource failed, which was part of a clone - While the
resource recovered, the fail-count log never
11 matches
Mail list logo
