RE: Simple Paged Results Extension

[Ben Lentz <BLentz@channing-bete.com>]

-----Original Message-----
From: Pierangelo Masarati [mailto:ando@sys-net.it]
Sent: Wednesday, February 18, 2004 10:52 AM
To: BLentz@channing-bete.com
Cc: openldap-software@OpenLDAP.org
Subject: RE: Simple Paged Results Extension



>
>
> -----Original Message-----
> From: Pierangelo Masarati [mailto:ando@sys-net.it]
> Sent: Tuesday, February 17, 2004 3:37 PM
> To: BLentz@channing-bete.com
> Cc: openldap-software@OpenLDAP.org
> Subject: Re: Simple Paged Results Extension
>
>
>
>> Greetings, I have a third-party webmail client that queries corporate
>> contacts via LDAP. It was written specifically for an Exchange server.
>> I get the following errors from slapd when the client performs a
>> query: (OpenLDAP 2.1.22):
>> => get_ctrls: oid="1.2.840.113556.1.4.319" (critical)
>> <= get_ctrls: n=1 rc=12 err="critical extension is not recognized"
>> send_ldap_result: conn=0 op=0 p=3
>> send_ldap_result: err=12 matched="" text="critical extension is not
>> recognized"
>> send_ldap_response: msgid=1 tag=101 err=12
>>
>> (OpenLDAP 2.2.5):
>> => get_ctrls: oid="1.2.840.113556.1.4.319" (critical)
>> => get_ctrls: oid="2.16.840.1.113730.3.4.2" (noncritical)
>> <= get_ctrls: n=2 rc=0 err=""
>> send_ldap_result: conn=0 op=0 p=3
>> send_ldap_result: err=12 matched="" text="control unavailable in
>> context" send_ldap_response: msgid=12 tag=101 err=12
>>
>> I've got no control over the client software and no longer want to use
>> Exchange. I believe an OpenLDAP solution would be superior. Any help
>> anyone can provide would be much appreciated.
>
> use back-bdb or back-hdb; they support that control.
>
> p.
>
> --
> Pierangelo Masarati
> mailto:pierangelo.masarati@sys-net.it
>
> Thanks! That being the case, I'm now having a new problem:
> If I compile with '--enable=bdb --with-bdb-module=static' instead of
> '--enable-bdb --enable-ldbm --with-ldbm-api=berkeley' and use 'database
> bdb' instead of 'database   ldbm' in slapd.conf, slapd crashes after
> trying to write it's first record and cannot restart again without
> freezing up until the contents of /var/lib/ldap (slapd.conf: directory
> /var/lib/ldap) are purged.
>
> I am trying to compile openldap with bdb support against Berkeley DB
> 4.2.52 statically, because my system (and all it's other software) is
> running Berkeley DB 4.1.25 and I can't upgrade everything. Is it
> possible to compile OpenLDAP 2.2 with Berkeley DB 4.1, run with
> 'database   bdb', support the Simple Paged Results Extension, and not
> have slapd crash? Or do I need to continue to try to get OpenLDAP built
> with Berkeley DB 4.2, and somehow co-exist with the rest of my Berkeley
> DB 4.1  based system?

use 4.2.52; you don't need to build it statically,
you can set the library path to the db-4.2 libraryes
only for OpenLDAP stuff.

p.

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


I still can't keep slapd from crashing every time I do an
ldapmodify/ldapadd. After it crashes, it won't restart again until
/var/lib/ldap is cleared out. This doesn't happen when I use ldbm.

slapd crashes with:
<= index_entry_add( 1, "dc=com" ) success
bdb_dn2entry("cn=ldapsync,")
=> bdb_dn2id( "" )
<= bdb_dn2id: get failed: DB_NOTFOUND: No matching key/data pair found
(-30990)
=> bdb_dn2id_add( "cn=ldapsync,", 0x00000002 )
slapd: dn.c:696: dnParent: Assertion `( ( ( ( (p[ 0 ]) >= 'a' && (p[ 0 ]) <=
'z' ) || ( (p[ 0 ]) >= 'A' && (p[ 0 ]) <= 'Z' ) ) ) || ( ( (p[ 0 ]) >= '0'
&& (p[ 0 ]) <= '9' ) ) )' failed.
Aborted

ldapmodify crashes with:
Enter LDAP Password:
adding new entry "dc=com"
ldapadd: update failed: dc=com
ldap_add: Can't contact LDAP server (-1)