Bug 677575 - winsync stops working after server restart
Summary: winsync stops working after server restart
Keywords:
Status: CLOSED DUPLICATE of bug 676655
Alias: None
Product: 389
Classification: Retired
Component: Sync Service
Version: 1.2.8
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Rich Megginson
QA Contact: Chandrasekar Kannan
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-02-15 09:40 UTC by Juan Carlos Camargo
Modified: 2015-01-04 23:46 UTC (History)
3 users (show)

Fixed In Version:
Clone Of: 676655
Environment:
Last Closed: 2011-02-15 15:05:43 UTC
Embargoed:


Attachments (Terms of Use)

Description Juan Carlos Camargo 2011-02-15 09:40:00 UTC
+++ This bug was initially created as a clone of Bug #676655 +++

After a restart of the directory service, the error.log shows "Replica has no update vector, it has never been initialized..". 

use service dirsrv restart to restart the server

--- Additional comment from rmeggins on 2011-02-10 17:41:23 EST ---

Cannot reproduce - steps

1) setup windows sync between current 1.2.8 and Windows 2008
2) added users to DS - confirm they are synced to windows
3) added users to AD - confirm they are synced to ds

service dirsrv restart

added user to DS - confirm synced to ad
added user to AD - confirm synced to ds

Note: this may be broken due to Bug 676689 - crash while adding a new user to be synced to windows

--- Additional comment from juancar on 2011-02-15 02:02:55 EST ---

I can reproduce it.

1) setup winsync between either 1.2.7 or 1.2.8 and windows 2008/2003
2) added users to either side: sync occurs.

service dirsrv restart (sometimes hangs). But wether it hanged or not, sync has been stopped, the error logs shows the same message of first post.

Cant tell if this was broken due to Bug676689. I was able to add users on the 389ds side flawlessly.

Comment 1 Rich Megginson 2011-02-15 15:05:43 UTC
Don't need a new bug for this - I just reopened 676655

*** This bug has been marked as a duplicate of bug 676655 ***


Note You need to log in before you can comment on or make changes to this bug.