Re: index_param failed on uniqueMember ?

[Andreas Hasenack <andreas@conectiva.com.br>]

On Thu, Feb 10, 2005 at 04:01:30PM -0800, Eddy Tan wrote:
> > > >bdb_equality_candidates: (uniqueMember) index_param
> failed(18)
> > > >
> > > >
> > I had the same problem, when I had a root/uid=0 account in
> > LDAP AND in /etc/passwd. The Lookups got just slow. When 
> > renaming the LDAP-Account to e.g. "admin", the problem 
> > disappeared (as suggested somewhere in the archives...)
> > 
> 
> I´ve double checked but there´s no identical entry in the
> /etc/passwd (and /etc/group) with the ldap entry.
> And the root user on my ldap is using cn=admin since the
> installation, so it never used cn=root.
> 
> There´s no problem with the lookup, etc (not slow whatsoever)
> but I keep getting the error message.
> 
> The complete sniff out of the log is as below:
> 
> Feb 11 10:44:33 eos slapd[22947]: conn=1586 op=2 SRCH
> base="ou=Group,dc=ldap,dc=office,dc=onthe,dc=net,dc=au" scope=1
> filter="(&(objectClass=posixGroup)(|(memberUid=ldap4)(uniqueMember=uid=ldap4,ou=staff,dc=ldap,dc=office,dc=onthe,dc=net,dc=au)))"

That's caused by rfc2307bis support in nss_ldap.
You could recompile nss_ldap without this support I suppose, then it will only search
the memberuid attribute (and not uniqueMember).