[ClusterLabs] Different Times in the Corosync Log?

[Jan Pokorný]

On 22/08/18 03:58 +0000, Eric Robinson wrote:
>> -----Original Message-----
>> From: Users <users-bounces at clusterlabs.org> On Behalf Of Jan Pokorný
>> Sent: Tuesday, August 21, 2018 2:45 AM
>> To: users at clusterlabs.org
>> Subject: Re: [ClusterLabs] Different Times in the Corosync Log?
>> 
>> 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?
> 
> Depends on how new the cluster is. With these, I start it with 'pcs
> cluster start'.

Ok, in case you don't use anything like pam_env PAM module (you've
already checked that, right?), my blind guess is that this could be
due to incorrect permissions for /etc/localtime or it's target in case
it's a symlink.  That way, root-privileged processes (lrmd in your
example) can format the timestamps correctly in localtime_r(3) whereas
non-privileged (like cib and crmd) are doomed to assume UTC.

In case it might help, try setting this in your
/etc/{default,sysconfig}/pacemaker file:

> TZ=:[filespec]

Quick and dirty fix leveraging existing /etc/localtime file (can be
a copy, not necessarily a symlink), assuming /etc/sysconfig/pacemaker
is the correct environment file and that the command is run as root:

 echo "TZ=:$(find /usr/share/zoneinfo -type d -o -exec sha256sum {} \; \
  | grep -F "$(sha256sum /etc/localtime | sed 's| .*||g')" \
  | sed 's|.*/usr/share/zoneinfo/||;q')" >>/etc/sysconfig/pacemaker

Let us know your progress.

-- 
Nazdar,
Jan (Poki)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <https://lists.clusterlabs.org/pipermail/users/attachments/20180827/b32e4434/attachment-0002.sig>