excessive clock skew problem with MMR

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



That's what I'm trying to avoid.  The clock skew was caused by vmware,
but I've gotten that settled down.  Unfortunately, there's something in
FDS (csngen_adjust_time?) that seems to be stuck.  I'm not sure what it
is referencing, as the clocks between the two are on time, now.

Thanks,
Jay

On Mon, 2008-01-21 at 16:24 -0500, dandantheitman wrote:
> My VM time skew issue, was not because it was a VM in and of itself
> issue, I resolved it by installing vm tools on it.  Once this was
> resolved, I made sure that both my boxes were pointing to my ntp
> server.
> 
> after that I back up lse.ldif file, and tar ed up the /opt/fedora-ds
> directory.  Then I blew the whole Directory server away, and rebuilt
> it from scratch, and restored the ldap and have not had any problems
> with it since.
> 
> Dan
> 
> On 21/01/2008, Jeremiah Coleman <jay.coleman at cctechnol.com> wrote:
> >
> > My 2 FDS systems will no longer replicate, due to excessive clock skew.
> > Specifically, this is what I get in the log:
> >
> > [21/Jan/2008:11:03:53 -0600] NSMMReplicationPlugin - conn=15 op=3
> > replica="dc=cctechnol,dc=com": Unable to acquire replica: error:
> > excessive clock skew
> > [21/Jan/2008:11:03:53 -0600] - csngen_adjust_time: adjustment limit
> > exceeded; value - 1872704, limit - 86400
> > [21/Jan/2008:11:03:53 -0600] NSMMReplicationPlugin - conn=16 op=3
> > replica="dc=cctechnol,dc=com": Unable to acquire replica: error:
> > excessive clock skew
> > [21/Jan/2008:11:03:55 -0600] - csngen_adjust_time: adjustment limit
> > exceeded; value - 1872702, limit - 86400
> > [21/Jan/2008:11:03:55 -0600] NSMMReplicationPlugin - conn=17 op=3
> > replica="dc=cctechnol,dc=com": Unable to acquire replica: error:
> > excessive clock skew
> >
> > I found a discussion of this problem in the archives, but the solution I
> > found there did not work for me.  I removed the replication agreements,
> > shutdown the servers, exported the userRoot database from one and
> > imported it to the other.  Deleted everything in changelogdb.  Restarted
> > the servers and added the replication agreement.  Same error.
> >
> > Anyone know of something else to try?
> >
> > Thanks,
> > Jay
> >
> > --
> > Jeremiah Coleman
> > Systems Administrator
> > C & C Technologies
> > 337-261-0660 x3421
> > jcoleman at cctechnol.com
> >
> >
> > --
> > Fedora-directory-users mailing list
> > Fedora-directory-users at redhat.com
> > https://www.redhat.com/mailman/listinfo/fedora-directory-users
> >
> 
> 
-- 
Jeremiah Coleman
Systems Administrator
C & C Technologies
337-261-0660 x3421
jcoleman at cctechnol.com





[Index of Archives]     [Fedora User Discussion]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [Fedora News]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Maintainers]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Legacy]     [Fedora Desktop]     [Fedora Fonts]     [ATA RAID]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Centos]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora QA]     [Fedora Triage]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Tux]     [Yosemite News]     [Yosemite Photos]     [Linux Apps]     [Maemo Users]     [Gnome Users]     [KDE Users]     [Fedora Tools]     [Fedora Art]     [Fedora Docs]     [Maemo Users]     [Asterisk PBX]     [Fedora Sparc]     [Fedora Universal Network Connector]     [Fedora ARM]

  Powered by Linux