[Pacemaker] Pacemaker 1.0.3 errors

[Andrew Beekhof]

Never mind, ignore all that. I see the problem.
What I dont understand is why no-one else has been seeing this.

Anyway, it really is a logging issue that you can safely ignore.

On Mon, May 4, 2009 at 9:15 AM, Andrew Beekhof <andrew at beekhof.net> wrote:
> On Thu, Apr 30, 2009 at 10:35 PM, Pavel Georgiev <neron at neron.org> wrote:
>> I get an awful lot of ' Action * took *s to complete' error since switching
>> from 1.0.2 to 1.0.3:
>
> [snip]
>
>> I`m running the prebuild rpms for centos5 (5.2 in my case).
>
> What hardware?
>
> I was expecting an ntpd clock jump, or a return of -1 from time(), but
>  this is really strange...
>
> May  1 05:52:08 ltsilver10-srv2 crmd: [24825]: info: main: CRM Hg
> Version: b133b3f19797c00f9189f4b66b513963f9d25db9
> May  1 05:52:08 ltsilver10-srv2 crmd: [24825]: info: crmd_init: Starting crmd
> May  1 05:52:08 ltsilver10-srv2 crmd: [24825]: ERROR: do_fsa_action:
> Action A_LOG    took 1236042029s to complete
>
> Starting from the UNIX epoch, the command would have to have been
> running until "Tue Mar  3 02:00:29 CET 2009" for the error to be true.
> Either that or the second call to times() returned "Sun Mar  1
> 03:51:39 CET 1970", which is also highly unlikely.
>
> So its clearly wrong, but I can't figure out why.
> All I can think of is an endian issue (hence the question about what
> hardware you're running).
>