Re: [389-users] excessive clock skew. Error Code: 2

2010-01-25 Thread Ajeet S Raina
Seems that it can only be the issue. I can see the time difference in between these two servers.Will fix it soon. Thanks. On Mon, Jan 25, 2010 at 10:13 PM, Morris, Patrick wrote: > Ajeet S Raina wrote: > > Incremental update has failed and requires administrator actionSystem > > error. Error Cod

Re: [389-users] excessive clock skew. Error Code: 2

2010-01-25 Thread Morris, Patrick
Ajeet S Raina wrote: > Incremental update has failed and requires administrator actionSystem > error. Error Code: -1 > Replication error acquiring replica: excessive clock skew. Error Code: 2 > > The Output has been taken from consumer Management Console. > Same error at Supplier end too. Keep

Re: [389-users] excessive clock skew. Error Code: 2

2010-01-25 Thread Rich Megginson
Ajeet S Raina wrote: > Guys, > > I have constructed Master to Master Replication on my CentOS. > > Master1: 389-supplier.sap.com > Master2:389-consumer.sap.com > > The Replication was setup through mmr.pl script > do

[389-users] excessive clock skew. Error Code: 2

2010-01-25 Thread Ajeet S Raina
Guys, I have constructed Master to Master Replication on my CentOS. Master1: 389-supplier.sap.com Master2:389-consumer.sap.com The Replication was setup through mmr.pl script downloaded from 389-DS official website, Things seems to be working fine. If I construct any User under Supplier Machine