On 11/05/2013 04:34 PM, Tamas Papp wrote:
On 11/05/2013 03:58 PM, Rich Megginson wrote:
On 11/05/2013 07:53 AM, Tamas Papp wrote:
On 11/05/2013 03:17 PM, Rich Megginson wrote:
This has been fixed upstream and in some releases - to allow
replication to proceed despite excessive clock skew - what is your
389-ds-base version and platform?
What is the clock skewed? The date and time is the same on both
VMs are notorious for having the clocks get out of sync - even
Eventually you were right, it looks, that the problem is related to the
virtualization, thanks for the tip.
Although I wouldn't say, it's because of messy VMs. It definitely must
be a software bug or misconfiguration, otherwise a VM should always
looks the same as a bare metal machine.
Actually in my specific case I don't see the reason, why it is working
with <clock offset='utc'/> and not with <clock offset='localtime'/> if
the time in the VM synchronized after bootup.
You can file a ticket.
It looks a software bug to me. But using UTC on (only) one machine is
definitely a misconfiguration:)
Freeipa-users mailing list