Already working replication agreement for a second suffix can not be parsed after server restart.
Two directory servers are setup with setup-ds and configured for two suffixes: example.com and domain.com
While adding single master-slave replication for one suffix (domain.com) it's working after setup but stops after restart of supplier with error:
389-ds version: 1.2.11.15
(I run in the error while trying to replicate a kolab 3.1. instance on debian wheezy and centos 6.5 which is using the 389-ds in the version of Enterprise Linux 6's EPEL. But I could reproduce it on a plain 389-ds installation without the kolab schema also.)
[18/Feb/2014:20:35:26 +0100] NSMMReplicationPlugin - changelog program - _cl5AppInit: fetched backend dbEnv (11a4d90) [18/Feb/2014:20:35:26 +0100] NSMMReplicationPlugin - changelog program - _cl5NewDBFile: semaphore /var/lib/dirsrv/slapd-test389ds0/changelogdb/3f12d603-98d211e3-be33f1f9-9beb3121.sema [18/Feb/2014:20:35:26 +0100] NSMMReplicationPlugin - changelog program - _cl5NewDBFile: maxConcurrentWrites=2 [18/Feb/2014:20:35:26 +0100] NSMMReplicationPlugin - changelog program - _cl5GetEntryCount: 3 changes for replica 3f12d603-98d211e3-be33f1f9-9beb3121 [18/Feb/2014:20:35:26 +0100] NSMMReplicationPlugin - changelog program - _cl5AddDBFile: Added new DB object 1373140 [18/Feb/2014:20:35:26 +0100] NSMMReplicationPlugin - changelog program - _cl5DBOpenFileByReplicaName: created new DB object 1373140 [18/Feb/2014:20:35:26 +0100] NSMMReplicationPlugin - changelog program - _cl5DBOpen: opened 1 existing databases in /var/lib/dirsrv/slapd-test389ds0/changelogdb [18/Feb/2014:20:35:26 +0100] NSMMReplicationPlugin - Found replication agreement named "cn=testreplica,cn=replica,cn=dc\3Dexample\2Cdc\3Dcom,cn=mapping tree,cn=config". [18/Feb/2014:20:35:26 +0100] NSMMReplicationPlugin - : Update window will close at Wed Feb 19 00:00:00 2014 [18/Feb/2014:20:35:26 +0100] NSMMReplicationPlugin - The replication agreement named "cn=testreplica,cn=replica,cn=dc\3Dexample\2Cdc\3Dcom,cn=mapping tree,cn=config" could not be correctly parsed. No replication will occur with this replica.
apt-get install 389-ds* setup-ds
ldif for creating second suffix add_domain.ldif
replication.ldif for the consumer replication_consumer.ldif
replication.ldif for supplier replication_supplier.ldif
add some users on the supplier add_users_supplier.ldif
full error log errors
This wasn't a bug but a wrong replica entry together with an less meaningfull error message.
There had been different domains in dn and replicaroot:
dn: cn=replica,cn=dc\=example\,dc\=com,cn=mapping tree,cn=config nsds5replicaroot: dc=domain,dc=com
Metadata Update from @jankow: - Issue set to the milestone: N/A
389-ds-base is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in 389-ds-base's github repository.
This issue has been cloned to Github and is available here: - https://github.com/389ds/389-ds-base/issues/1040
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Metadata Update from @spichugi: - Issue close_status updated to: wontfix (was: Invalid)
Login to comment on this ticket.