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
What do you mean by this?
I definitely see the same time on the machines.
Also I can see in the log, that the replication is resumed. There is no
messages about the broken replication after the resume message.
You see the same time NOW. The logs were reflecting a difference at that
Linux ipa31.bph.cxn 3.11.6-201.fc19.x86_64 #1 SMP Sat Nov 2 14:09:09 UTC
2013 x86_64 x86_64 x86_64 GNU/Linux
How can I fix it?
ldapmodify -x -D "cn=directory manager" -W <<EOF
Do this on all of your servers.
I tried this, but no joy. Still not good:/
What I really don't understand, why I cannot login to ui (or to an
installed client machine) if the replication doesn't work.
Is it a normal behaviour?
These issues are probably not related, unless perhaps the time skew is
also throwing off the Kerberos tickets and/or session cache in the IPA
You didn't say how you were trying to log into the UI. Are you using
Kerberos or the form-based authentication?
Freeipa-users mailing list