Hi,
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
dn: cn=UsersSyncAgreement,cn=replica,cn=dc\=example\,dc\=com\,cn=mapping tree,cn=config
changetype: add
objectclass: top
objectclass: nsDSWindowsReplicationAgreement
cn: UsersSyncAgreement
winSyncSubtreePair: cn=Users,dc=adexample,dc=com:ou=userandgroups,dc=example,dc=com
winSyncSubtreePair: ou=ItalyGroups,dc=adexample,dc=com:ou=userandgroups,dc=example,dc=com
nsds7NewWinUserSyncEnabled: on
nsds7NewWinGroupSyncEnabled: on
nsds7WindowsDomain:
adexample.comnsDS5ReplicaRoot: dc=example,dc=com
nsDS5ReplicaHost:
adexample.comnsDS5ReplicaPort: 389
nsDS5ReplicaTransportInfo: LDAP
nsDS5ReplicaBindDN: cn=replication user,cn=Users,dc=adexample,dc=com
nsDS5ReplicaBindMethod: SIMPLE
nsDS5ReplicaCredentials: secret
winSyncInterval: 1200
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
dn: cn=UsersSyncAgreement,cn=replica,cn=dc\=example\,dc\=com\,cn=mapping tree,cn=config
changetype: modify
replace: nsds5BeginReplicaRefresh
nsds5BeginReplicaRefresh: start
The dirsrv service crashes.
Can you help me with this problem, Am I configuring something wrong in the above replication agreement?
Thank you
Abhishek Deb