Bug 677575

Summary:	winsync stops working after server restart
Product:	[Retired] 389	Reporter:	Juan Carlos Camargo <juancar>
Component:	Sync Service	Assignee:	Rich Megginson <rmeggins>
Status:	CLOSED DUPLICATE	QA Contact:	Chandrasekar Kannan <ckannan>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	1.2.8	CC:	benl, juancar, rmeggins
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	676655	Environment:
Last Closed:	2011-02-15 15:05:43 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

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 ***