[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: Solved: index_param failed

On Sun, 2005-01-16 at 23:31 +0100, Wolf-Agathon Schaly wrote:
Further lets look at the entire line - index_param failed was not the
full story. The full line of error message is

<= bdb_equality_candidates: (uniqueMember) index_param failed (18)

That made me think ... Where in goods name came the "equality candidat"
from and why is that damn system looking for uniqueMember. I looked at
my LDIF - no non unique definition.
But only for all "human beings" ... hmmm and some "non human" accounts
like mailman and dovecot.

What is the solution:
At the end it is logic and easy - but you have to know.

If you have an entry in you passwd/shadow AND your OpenLDAP database
you'll see this kind of messages. You simply need to delete either one
account in LDAP or your passwd.
BEWARE: DO NOT DELETE root from passwd but from LDAP - just in case your
LDAP is currupt, you'll never be able to login you your system.

this is not a solution in my case. there is not any entry which are both in passwd and ldap, but i still got the error message: <= bdb_equality_candidates: (uniqueMember) index_param failed (18) anybody knows the solution?

  Levente                               "Si vis pacem para bellum!"