It turns out it was mistake from our end, we were checking too early before
the actual replication was done completely. Now that works properly.
The direction of replication is from AD -> 389 DS
But now we have a new requirement which is to copy from multiple Source
Subtree from Windows to Linux.
To get both subtrees I used the winSyncSubtreePair multivalued attribute.
This is the replication agreement we have right now
nsDS5ReplicaBindDN: cn=replication user,cn=Users,dc=adexample,dc=com
We want to copy both subtrees cn=Users and ou=ItalyGroups from the AD to
389 DS subtree ou=userandgroups,dc=example,dc=com.
Once the 389 Directory Server is installed, and this replication agreement
is configured, I am able to access the 389 DS.
But once I initialize this replication agreement using the following
The dirsrv service crashes.
Can you help me with this problem, Am I configuring something wrong in the
above replication agreement?
On Sun, Jun 30, 2019 at 9:24 PM William Brown <wbrown(a)suse.de> wrote:
> On 25 Jun 2019, at 05:09, Abhisheyk Deb <abhisheykdeb(a)gmail.com> wrote:
> We have the following setup.
> Active Directory Server in US.
> 389 DS Server in Italy.
> We are able to access the Active Directory Server from 389 DS.
> We installed the sync agreement. No body is touching the AD, the number
of objects that should copied is 21. But every time we are running the
replication agreement, the number of objects being copied is always
different. How can that be if there is no change happening at the AD
> Is the replication done over UDP or TCP.
> Also is it because of distance and delay that is causing the
> If some can elaborate in this issue, it would be really helpful.
Sorry for the very late reply,
Replication like this, can be partial - it may not send all objects or
structures, just ones defined in the agreement.
I think we'll need to see your winsync agreement from cn=config to know
more, and to see what kind of objects are being sent, and what is not.
Is it objects from 389 to AD or in the other direction that are/are not
> Thank you
> Abhishek Deb
> 389-users mailing list -- 389-users(a)lists.fedoraproject.org
> To unsubscribe send an email to 389-users-leave(a)lists.fedoraproject.org
> Fedora Code of Conduct:
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
Senior Software Engineer, 389 Directory Server
389-users mailing list -- 389-users(a)lists.fedoraproject.org
To unsubscribe send an email to 389-users-leave(a)lists.fedoraproject.org
Fedora Code of Conduct:
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines