On 06/07/2016 11:30 AM, Mark Reynolds wrote:
On 06/07/2016 11:03 AM, Job Cacka wrote:
On 06/06/2016 05:02 PM, Job Cacka wrote:
Okay, so I think the gidNumber index just needs to be regenerated:
db2index.pl -n userroot _D "cn=directory manager" -w PASSWORD -t
gidNumber
Running that command with a '-D' instead of '_D' fixed the ldapsearch
problem when looking for gidNumber.
Sorry about the typo.
Are there other indexes that should be reindexed? How often should
that occur? I could setup a script to run every Sunday at midnight
for instance.
Typically you never need to reindex your attributes unless you change
an index's configuration, or create a new index.
I forgot to mention, it's also possible you added the index for
gidNumber and never ran db2index. In this case, the index will only
start recording entry ID's as they are modified. This is why removing
the gidNumber value and re-adding it fixed the issue, and it could also
explain why some entries were affected while others were not.
You can always reindex all your attributes by running the above
command without the -t option:
db2index.pl -n userroot -D "cn=directory manager" -w PASSWORD
Now, there is a known issue with index corruption that was fixed in:
389-ds-base-1.2.11.15-70.el6
Its possible you ran into this bug, but it takes a special type of
modify operation for the corruption to occur. See the ticket for more
info:
https://fedorahosted.org/389/ticket/48370
https://bugzilla.redhat.com/show_bug.cgi?id=1282457
Regards,
Mark
Thanks,
Job
--
389-users mailing list
389-users@xxxxxxxxxxxxxxxxxxxxxxx
https://lists.fedoraproject.org/admin/lists/389-users@xxxxxxxxxxxxxxxxxxxxxxx
--
389-users mailing list
389-users@xxxxxxxxxxxxxxxxxxxxxxx
https://lists.fedoraproject.org/admin/lists/389-users@xxxxxxxxxxxxxxxxxxxxxxx
--
389-users mailing list
389-users@xxxxxxxxxxxxxxxxxxxxxxx
https://lists.fedoraproject.org/admin/lists/389-users@xxxxxxxxxxxxxxxxxxxxxxx
