[Pacemaker] WARN: action_timer_callback: Ignoring timeout while not in transition

Andrew Beekhof andrew at beekhof.net
Mon Feb 27 06:07:45 EST 2012


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.mni.mcgill.ca> 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.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




More information about the Pacemaker mailing list