On Thu, 2016-02-04 at 09:32 -0600, Derek Belcher wrote: > William, > > Thank you for your reply. So it looks like running the following > command: > > # /usr/lib64/dirsrv/slapd-YOURID/db2index -n MYBACKEND -t entryrdn > > And then initializing the master that was having the errors, it did > not fix > the issue... in fact, I am getting the same exact issue. Here is > something > interesting though, if I move one of the affected users in Active > Directory > to another group, it replicates back over to the LDAP side and I can > reinitialize the affected master fine.... But when I move the user > back to > the group container that he is supposed to be in, the users failed to > sync > to the affected master again... > > [04/Feb/2016:09:01:41 -0600] - import userRoot: WARNING: Skipping > entry > "uid=user1,ou=Users,ou=Place1,ou=Place2,ou=Groups,dc=mydomain,dc=net" > which > has no parent, ending at line 0 of file "(bulk import)" > [04/Feb/2016:09:01:41 -0600] - import userRoot: WARNING: bad entry: > ID 29 > Okay. db2index didn't solve this. Can you please run: sudo dbscan -f /var/lib/dirsrv/slapd-INSTANCE/db/userRoot/entryrdn.db -k 29 sudo dbscan -f /var/lib/dirsrv/slapd-INSTANCE/db/userRoot/id2entry.db -K 29 I think this works while DS is online, but err on the side of caution and stop the instance first. I suspect there may be a corruption in the entry but we need to look a bit closer to really know why. It may even be that the parent entry has an issue, so we might need to look at that ID next .... -- Sincerely, William Brown Software Engineer Red Hat, Brisbane
Attachment:
signature.asc
Description: This is a digitally signed message part
-- 389 users mailing list 389-users@%(host_name)s http://lists.fedoraproject.org/admin/lists/389-users@xxxxxxxxxxxxxxxxxxxxxxx
