[ClusterLabs] Different Times in the Corosync Log?

[Ken Gaillot]

Whoa, I think you win some sort of fubar prize. :-)

AFAIK, any OS-level time or timezone change affects all processes
equally. (I occasionally deal with cluster logs where the OS time
jumped backward or forward, and all logs system-wide are equally
affected.)

Some applications have their own timezone setting that can override the
system default, but pacemaker isn't one of them. It's even more bizarre
when you consider that the daemons here are the children of the same
process (pacemakerd), and thus have an identical set of environment
variables and so forth. (And as Jan pointed out, they appear to have
been started within a fraction of a second of each other.)

Apparently there is a dateshift kernel module that can put particular
processes in different apparent times, but I assume you'd know if you
did that on purpose. :-) It does occur to me that the module would be a
great prank to play on someone (especially combined with a cron job
that randomly altered the configuration).

If you figure this out, I'd love to hear what it was. Gremlins ...

On Tue, 2018-08-21 at 11:45 +0200, Jan Pokorný wrote:
> On 21/08/18 08:43 +0000, Eric Robinson wrote:
> > > I could guess that the processes run with different timezone
> > > settings (for whatever reason).
> > 
> > That would be my guess, too, but I cannot imagine how they ended up
> > in that condition. 
> 
> Hard to guess, the PIDs indicate the expected state of covering a
> very
> short interval sequentially (i.e. no intermittent failure recovered
> with
> a restart of lrmd, AFAICT).  In case it can have any bearing, how do
> you start pacemaker -- systemd, initscript, as a corosync plugin,
> something else?
-- 
Ken Gaillot <kgaillot at redhat.com>