[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
Proxy Cache Overlay error: index out of bounds
- To: openldap-software@OpenLDAP.org
- Subject: Proxy Cache Overlay error: index out of bounds
- From: Andrew Reilly <andrew.reilly@gmail.com>
- Date: Thu, 11 Nov 2004 12:42:47 -0500
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding; b=JeBLxL+MmNZwceJI/MyV0JCsxwNoXUuRlcMTLXois8jltBCgpyT71EfK7BgYihgfMUbUSFgiDHEs6OR8loEcCoMct/aqWsLpHwEgtEGM+Z/F5LC9P9EjhgrZ9HYl083LFKq+XMtXdcMqzE8J5AKdmF0SNiUJP53UFSFeHIlCxKc=
I am in the process of attempting to upgrade a slapd-meta server to
openldap-2.2.17. One of the chief reasons for the upgrade was to take
advantage of the Proxy Cache Overlay functionality. Initial testing
has gone well, and I have managed to construct a number of working
attribute sets and cacheable templates.
Each of these attribute sets and maching cacheable templates were
configured and tested with only one attribute set in the slapd.conf
file at a time. After I added any two of the attribute sets
everything still functioned as expected. Then I added a third set and
the result was an error during startup:
Starting slapd: /usr/local/proxy-ldap/etc/openldap/slapd.conf; line
110 index out of bounds
Has anyone seen this error before? I've googled it and looked through
the Issue Tracking System with no results. As I said, any
combination of two sets works fine but the addition of any third
functioning rule set seems to result in this error. The build process
completed without a hitch. Is there something I'm missing?
Environment:
openldap-2.2.17
db-4.2.52
Redhat ES 3.0
TIA,
andrew