RE: index_param failed on uniqueMember ?

[Eddy Tan <eddy_hs@yahoo.com>]

>> filter="(&(objectClass=posixGroup)(|(memberUid=ldap1)
>> (uniqueMember=uid=ldap1,ou=staff,
>> dc=ldap,dc=office,dc=onthe,dc=net,dc=au)))"
>>
>> Feb 11 14:35:41 slapd[23900]: conn=12 op=2 SRCH
attr=gidNumber
>> Feb 11 14:35:41 slapd[23900]: <= bdb_equality_candidates:
>> (uniqueMember) index_param failed (18)
>>
> 
> Why don't you just build your own OpenLDAP 2.2 install
> separate from the debian install.  Debian is never going to be

> as up to date as you'll need it to run a directory service.
> 

Hi Quanah,

I've somehow managed to build OL 2.2.23 on the debian server but
still got that same error message? 

With the new OL 2.2.23 all stuff work fine as it used to be (I
could do ldapsearch, ldapmodify, ldapadd, etc both through port
389/636).

That error log comes up /only/ after doing "ssh" or "su" on
/any/ machines. Now I tend to think it might not be OL probs but
something to do with nss_ldap or pam_ldap. 

But... I dunno where to trace it (been done all suggestion on
this phorum, i.e. checked if there's double entry on ldap and
/etc/{passwd|group}, put 'index uniqueMember pres' inside
slapd.conf, nothing solves it :-(

Anyone experienced the same problem? 




		
__________________________________ 
Do you Yahoo!? 
Yahoo! Mail - now with 250MB free storage. Learn more.
http://info.mail.yahoo.com/mail_250