-----BEGIN PGP SIGNED MESSAGE-----
>>> What is the default behaviour if no equality type is
If no equality matching is specified for the attribute type:
- the attribute (of the type) cannot be used for naming;
- when adding the attribute (or replacing all values), no two
values may be equivalent (see 2.2);
- individual values of a multi-valued attribute are not to be
independently added or deleted;
- attribute value assertions (such as matching in search
filters and comparisons) using values of such a type cannot be
Which means, you are not supposed to use it in a search filter.
Ahh that's good to know. This kind of thing should be in the RHDS documentation
as we couldn't find anything about the topic, and it's an invaluable piece of
knowledge in solving this issue.
However, 389 provides a default equality matching rule, which is
essentially a memcmp(3). When you create an index, it attempts to
use the equality matching rule to create the equality index. I guess
the indexing code is getting confused. Do you have
file? If so, does it have anything in it? dbscan
The db4 file in question was empty. I am assuming that this indicates an issue
with the indexing yielding no data, but if it was empty, and an index search was
performed I am assuming that is why our search begins to return no data.
You can also force the indexing to use a particular matching rule -
you specify the matching rule to use for the index by using the
However, I would advise you _not_ to use an attribute type without an
explicitly specified equality rule in a search filter.
I have added the nsMatchingRule to our config, and upon re-index our searches
work now. Thanks for this tip.
That's a good piece of advice. I will also investigate our schemas and such
that lack an equality rule, and I will see if they violate this.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
-----END PGP SIGNATURE-----