Hello,
If I modify the value of an attribut, the change is applied on the other LDAP server so the replication is working fine.
For a reason that I do not known an entry is missing on one of my LDAP server.
How can I recreate this missing entry ?
The replication seems to not work is this case.
Or have I to do a initialisation from the LDAP where the entry is present ?
Re-initialization (online or offline) will make sure that all entries are identical on both servers and will be kept in sync in the future.
Is the entry really missing or is it just that you do not see it when performing a search ?
One way to check is to export the data (with replication meta-data, and from the server which appears to have the entry missing) to LDIF. And look into the LDIF file if the entry is present or not, if it is a normal entry or a deleted entry.
If the entry is present and normal, it could be an index issue and rebuilding the index should be enough.
If the entry is present but as a deleted entry, this would require more investigation.
If the entry is not present at all, then reinitialization is the only proper way to solve this issue.
regards,
Ludovic
When replication is enabled, entries are not deleted immediately from the database, but marked as deleted. This is done internally by the server which adds the objectclass nsTombstone (among other things). The server will never return an entry with objectclass nsTombstone on a search request.
Regards
Ludovic.
Hi all,
I found the problem.
The entry DN was : uid=userx,ou=persons,ou=internal,dc=company,dc=com
userx had did some "manual" change into ldap under his account.
He added some entries (to test Role) :
objectClass: nsRoleDefinition
objectClass: nsSimpleRoleDefinition
objectClass: nsManagedRoleDefinition
objectClass: ldapSubEntry
I do not known wy after this cange, his entry on one server was deleted.
But anyway, to correct the problem I do :
1) export his entry into a LDIF file
2) delete his entry
3) modify the above LDIF file (remove entries concerning Role)
4) import the new LDIF file
And now it's OK
Regards
Well, ldapsubentry is a "magic" objectclass which makes the entry an operational entry not to be returned with regular entries.
As a result it appears a deleted in regular searches although it's still present on the server.
I do not understand why you would only see this on one server and not all of them though.
regards,
Ludovic
