olcDbURI error

[Jaap Winius <jwinius@umrk.nl>]

Hi folks,

After applying some changes to a consumer server used for testing  
purposes, my attempts to run slapcat result in the following error:

####################################
slapd-chain: first underlying database  
"olcDatabase={0}ldap,olcOverlay={0}chain,olcDatabase={1}hdb,cn=config"  
cannot contain attribute "olcDbURI".
config error processing  
olcDatabase={0}ldap,olcOverlay={0}chain,olcDatabase={1}hdb,cn=config:
slapcat: bad configuration file!
####################################
(Debian squeeze, slapd v2.4.23-6)

After having configure syncrepl on the same host, I used slapcat to  
compare its newly replicated database to the one on the provider. At  
that point it still worked and the databases proved to be identical.

I then proceeded to configure chaining and a referral. The above  
slapcat error appeared after I made the following changes (which  
applied successfully):

###########################################################################
# 1.
dn: olcDatabase={1}hdb,cn=config
changetype: modify
add: olcUpdateref
olcUpdateref: ldap://ldaps.example.com

# 2.
dn: cn=module{0},cn=config
changetype: modify
add: olcModuleLoad
olcModuleLoad: {1}back_ldap

# 3.
dn: olcOverlay={0}chain,olcDatabase={1}hdb,cn=config
objectClass: olcOverlayConfig
objectClass: olcChainConfig
olcOverlay: {0}chain
olcChainReturnError: TRUE

# 4.
dn: olcDatabase={0}ldap,olcOverlay={0}chain,olcDatabase={1}hdb,cn=config
objectClass: olcLDAPConfig
objectClass: olcChainDatabase
olcDatabase: {0}ldap
olcDbURI: ldap://ldaps.example.com
olcDbRebindAsUser: TRUE
olcDbIDAssertBind: bindmethod=simple
  binddn="cn=ldaps2,dc=example,dc=com"
  credentials=bilineatus
  mode=self
###########################################################################

Afterwards, slapd could no longer be restarted either, with the same  
error showing up in the syslog.

I am aware that this is a known bug:

http://www.openldap.org/its/index.cgi/Software%20Bugs?id=6540;selectid=6540

According to the report, a patch was made available on April the 29th,  
but I'm not sure if it actually fixed anything. At any rate, my Debian  
slapd version is dated from the 23rd of September and still has this  
problem.

However, Followup 17 (31 July) in the bug report refers to a "simple  
fix". Unfortunately, I haven't yet been able to find what that's  
supposed to be.

This seems to me to be a serious bug, but for the time being I'd be  
happy with simple workaround. Can anyone help?

Thanks,

Jaap