Red Hat Directory Server replication halt: Unable to acquire replica: error: excessive clock skew

Solution Verified - Updated -

Issue

  • In my production Red Hat Directory Server cluster, replication to one of the consumers is currently broken.
    The error message I'm getting is excessive clock skew, however, the clocks are currently in sync and updated with NTP.
[16/Sep/2013:13:22:00 -0400] NSMMReplicationPlugin - conn=4726 op=3 replica="dc=example,dc=com": Unable to acquire replica: error: excessive clock skew
[16/Sep/2013:13:22:00 -0400] - csngen_adjust_time: adjustment limit exceeded; value - 1191158, limit - 86400
[16/Sep/2013:13:22:00 -0400] - CSN generator's state:
[16/Sep/2013:13:22:00 -0400] -  replica id: 65535
[16/Sep/2013:13:22:00 -0400] -  sampled time: 1379352120
[16/Sep/2013:13:22:00 -0400] -  local offset: 0
[16/Sep/2013:13:22:00 -0400] -  remote offset: 14396
[16/Sep/2013:13:22:00 -0400] -  sequence number: 0
[16/Sep/2013:13:22:00 -0400] NSMMReplicationPlugin - conn=4727 op=3 repl="dc=example,dc=com": Excessive clock skew from supplier RUV
[16/Sep/2013:13:22:00 -0400] NSMMReplicationPlugin - conn=4727 op=3 replica="dc=example,dc=com": Unable to acquire replica: error: excessive clock skew
  • I have tried re-initializing the consumer, but it still complains about clockskew.
  • I also have restarted dirsrv on both the supplier and consumer with no luck.

Environment

  • Red Hat Directory Server 9/10/11/12
  • Red Hat Enterprise Linux 6/7/8/9

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content