Hello 389's,
Yesterday, queries with that used the cn attribute as the filter
returned incomplete results. After a few hours of debugging, we decided
the drop and recreate the cn index and that fixed the problem. No idea
how the index got corrupted. No admin work performed on the server just
data reads and writes. Luckily this was a test server. Is there anything
we can do to prevent this from happening on the production servers?
Server version: 389-ds-base-1.2.11.15-34.el6_5.x86_64
Thank you,
Adrian
