On 22/08/18 03:58 +, Eric Robinson wrote:
>> -Original Message-
>> From: Users On Behalf Of Jan Pokorný
>> Sent: Tuesday, August 21, 2018 2:45 AM
>> To: users@clusterlabs.org
>> Subject: Re: [ClusterLabs] Different Times in the Corosync Log?
>&g
>
> Whoa, I think you win some sort of fubar prize. :-)
It's always nice to feel special.
>
> 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
> -Original Message-
> From: Users On Behalf Of Jan Pokorný
> Sent: Tuesday, August 21, 2018 2:45 AM
> To: users@clusterlabs.org
> Subject: Re: [ClusterLabs] Different Times in the Corosync Log?
>
> On 21/08/18 08:43 +, Eric Robinson wrote:
> >> I coul
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
On 21/08/18 08:43 +, 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
The corosync log show different times for lrmd messages than for cib or crmd
messages. Note the 4 hour difference. What?
Aug 20 13:08:27 [107884] 001store01acib: info: cib_perform_op:
+
