I think the issue may related to https://bugzilla.redhat.com/show_bug.cgi?id=788140 We have CentOS Directory Server 8.1 on our RHEL5 master and a much newer version of 389 DS on CentOS 7 from EPEL. I have also been reviewing https://access.redhat.com/documentation/en-US/Red_Hat_Directory_Server/8.2/html/Installation_Guide/upgrade.html and that specifically states: "Directory Server 8.2 normalizes DN syntax during the upgrade process from 8.1." I'm hoping if we upgrade to 8.2 this might improve things. In response to the questions that Mark asked: Can you be more specific? Errors? Logging? Steps to reproduce? Not really... There are no errors being logged at our current log level. I've been unable to determine why some entries have a dc=company, dc=com and others have no space between , and dc. We generally use Apache Directory Studio to make all our changes. What is happening exactly? What is in the access and errors logs? There's nothing much in the logs. As I say I will be turning the log levels up to see if we can get more. How exactly are you renaming the entry? If we use Directory Studio to remove the extra space groups uniqueMember DN then the changes are propagated correctly to RHEL5 and Centos 6 instances but CentOS 7 389 creates a new entry without the space and leaves the original there as well! It's effectively a duplicate :( As our CentOS 7 servers are consumers only, the only way we can remove these entries or change them is to update our RHEL5 master and then re-initialise the Centos7 consumers. Are you saying that the same entry on the master is different on the consumer? The consumer has a space in the dn while the master does not? After initialising both look identical. Certain changes on the master aren't correctly replicated to or handled on the CentOS 7 versions of 389. i.e. The replication instructions don't seem match any entries with a space after a comma in an entries DN: So any changes to one of these on the master seem to result in a new entry on the CentOS 7 389 and a zombie entry (with the space) is then stuck. Hope this clarifies things a bit. I will update tomorrow after upgrading our RHEL5 instances to CentOS DS 8.2. It may not fix things but it might make our lives easier to migrate the directory master to CentOS 7 as well. _______________________________________________ 389-users mailing list -- 389-users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to 389-users-leave@xxxxxxxxxxxxxxxxxxxxxxx
