RE: filter problem

["Pierangelo Masarati" <ando@sys-net.it>]

> Pierangelo Masarati wrote:
>
>> For instance, you may start from telling us what software
>> version you're using (on what OS), what data you actually
>> stored in it (the exact LDIF, without any proprietary or
>> sensitive info) and exactly what operation (command and options)
>> you're performing.
>
> uhm, of course, sorry...
>
> OS Redhat ES 3
> OpenLDAP v. should be the one that comes with RH

should be 2.0.27-ish.  In this case, in the evidence of a bug, the only
solution would be to upgrade to a supported release, or ask your vendor
(RedHat) for specific support.

>
> this is the respective ldif:
>
> dn: uid=bvmaster,ou=TeZebraUser,ou=Access
> cn: BVMaster, BVMaster
> gid: 1109856477632
> givenName: BVMaster
> objectClass: top
> objectClass: person
> objectClass: organizationalPerson
> objectClass: inetOrgPerson
> objectClass: nsLicenseUser
> objectClass: mailRecipient
> objectClass: xxxxIntranetPerson

what about the definition of objectClass "xxxxIntranetPerson" ?

> sn: BVMaster
> uid: bvmaster
> userPassword: xxxxxx
>
>
> the search is done with ldapsearch -x -h 'myhost' -p myport -v -b
> 'ou=Access' 'objectClass=xxxxIntranetPerson'
>
> and doesn't return the entry bvmaster. Same from within any LDAPBrowser.

would a slapcat/slapadd of the database, or at least a slapindex, cure the
problem?  I'm trying to figure out if, by chance, your indices for
objectClass got somehow corrupted.

p.

-- 
Pierangelo Masarati
mailto:pierangelo.masarati@sys-net.it


    SysNet - via Dossi,8 27100 Pavia Tel: +390382573859 Fax: +390382476497