Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: Linux-HA: Pacemaker

WARN: action_timer_callback: Ignoring timeout while not in transition

 

 

Linux-HA pacemaker RSS feed   Index | Next | Previous | View Threaded


Jean-Francois.Malouin at bic

Feb 25, 2012, 2:54 PM

Post #1 of 3 (318 views)
Permalink
WARN: action_timer_callback: Ignoring timeout while not in transition

Hi,

I manually moved a few resources this morning on a very simple
active/active 2-node cluster with drbd *not* in dual-primary mode.
(pacemaker 1.0.9, corosync 1.2.1 from Debian Squeeze)

Since then I'm getting these WARN messages, exactly 5mins after
the pengine recheck timer pops in:

Feb 25 17:36:15 puck crmd: [6376]: info: crm_timer_popped: PEngine Recheck Timer (I_PE_CALC) just popped!
Feb 25 17:36:15 puck crmd: [6376]: info: do_state_transition: State transition S_IDLE -> S_POLICY_ENGINE [ input =I_PE_CALC cause=C_TIMER_POPPED origin=crm_timer_popped ]

[...]

Feb 25 17:41:15 puck crmd: [6376]: WARN: action_timer_callback: Timer popped (timeout=240000, abort_level=0, complete=true)
Feb 25 17:41:15 puck crmd: [6376]: WARN: action_timer_callback: Ignoring timeout while not in transition

What do those mean?

Thanks!
jf

_______________________________________________
Pacemaker mailing list: Pacemaker [at] oss
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


andrew at beekhof

Feb 27, 2012, 3:07 AM

Post #2 of 3 (296 views)
Permalink
Re: WARN: action_timer_callback: Ignoring timeout while not in transition [In reply to]

Could be a bug. Looks like an action completed but we didn't clean up
its timer.
There shouldn't be any problem except for some noise in the logs.

An upgrade would likely fix this if its annoying you.

On Sun, Feb 26, 2012 at 9:54 AM, Jean-Francois Malouin
<Jean-Francois.Malouin [at] bic> wrote:
> Hi,
>
> I manually moved a few resources this morning on a very simple
> active/active 2-node cluster with drbd *not* in dual-primary mode.
> (pacemaker 1.0.9, corosync 1.2.1 from Debian Squeeze)
>
> Since then I'm getting these WARN messages, exactly 5mins after
> the pengine recheck timer pops in:
>
> Feb 25 17:36:15 puck crmd: [6376]: info: crm_timer_popped: PEngine Recheck Timer (I_PE_CALC) just popped!
> Feb 25 17:36:15 puck crmd: [6376]: info: do_state_transition: State transition S_IDLE -> S_POLICY_ENGINE [ input =I_PE_CALC cause=C_TIMER_POPPED origin=crm_timer_popped ]
>
> [...]
>
> Feb 25 17:41:15 puck crmd: [6376]: WARN: action_timer_callback: Timer popped (timeout=240000, abort_level=0, complete=true)
> Feb 25 17:41:15 puck crmd: [6376]: WARN: action_timer_callback: Ignoring timeout while not in transition
>
> What do those mean?
>
> Thanks!
> jf
>
> _______________________________________________
> Pacemaker mailing list: Pacemaker [at] oss
> 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

_______________________________________________
Pacemaker mailing list: Pacemaker [at] oss
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


Jean-Francois.Malouin at bic

Feb 27, 2012, 11:14 AM

Post #3 of 3 (306 views)
Permalink
Re: WARN: action_timer_callback: Ignoring timeout while not in transition [In reply to]

* Andrew Beekhof <andrew [at] beekhof> [20120227 06:08]:
> Could be a bug. Looks like an action completed but we didn't clean up
> its timer.
> There shouldn't be any problem except for some noise in the logs.
>
> An upgrade would likely fix this if its annoying you.

Thanks Andrew for the answer.
I'll cope with the noise and filter thoses out with a logcheck rule.

jf

>
> On Sun, Feb 26, 2012 at 9:54 AM, Jean-Francois Malouin
> <Jean-Francois.Malouin [at] bic> wrote:
> > Hi,
> >
> > I manually moved a few resources this morning on a very simple
> > active/active 2-node cluster with drbd *not* in dual-primary mode.
> > (pacemaker 1.0.9, corosync 1.2.1 from Debian Squeeze)
> >
> > Since then I'm getting these WARN messages, exactly 5mins after
> > the pengine recheck timer pops in:
> >
> > Feb 25 17:36:15 puck crmd: [6376]: info: crm_timer_popped: PEngine Recheck Timer (I_PE_CALC) just popped!
> > Feb 25 17:36:15 puck crmd: [6376]: info: do_state_transition: State transition S_IDLE -> S_POLICY_ENGINE [ input =I_PE_CALC cause=C_TIMER_POPPED origin=crm_timer_popped ]
> >
> > [...]
> >
> > Feb 25 17:41:15 puck crmd: [6376]: WARN: action_timer_callback: Timer popped (timeout=240000, abort_level=0, complete=true)
> > Feb 25 17:41:15 puck crmd: [6376]: WARN: action_timer_callback: Ignoring timeout while not in transition
> >
> > What do those mean?
> >
> > Thanks!
> > jf
> >
> > _______________________________________________
> > Pacemaker mailing list: Pacemaker [at] oss
> > 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
>
> _______________________________________________
> Pacemaker mailing list: Pacemaker [at] oss
> 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

_______________________________________________
Pacemaker mailing list: Pacemaker [at] oss
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

Linux-HA pacemaker RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact Gossamer Threads
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.