Dear lister,
I just upgrade to 2.4.6 and also Berkeley db 4.6. I'm using the same slapd.conf that was used with 2.3.38.
I have the problem in the sql backend. Slapd cannot start if slapd.conf has more than 1 sql backend at the same time. If I have 2 sql backend, from -d -1 will complain about the 2nd backend as I snipped.
Return code: -2 backsql_db_open(): schema mapping failed, exiting backend_startup_one: bi_db_open failed! (1)
At first I thought it is about my mappings, but If I comment the first sql backend out. With same second database that slapd used to complain, the slapd could start and run fine (so, the mappings is correct).
It seem like 2 of sql backend cannot stay in one slapd.conf
Anyway, dbd database still can have 2 or more at the same time; slapd can start.
---------------- slapd.conf -------------------- database sql ## This following is for the sample database suffix "dc=example,dc=com" dbname bsql dbuser manager dbpasswd secret subtree_cond "ldap_entries.dn LIKE CONCAT('%',?)" insentry_stmt "INSERT INTO ldap_entries (dn,oc_map_id,parent,keyval) VALUES (?,?,?,?)" has_ldapinfo_dn_ru no # #
# SQL database definitions ##########################################
#database sql ## This following is for the sample database #suffix "dc=clone,dc=com" #dbname setup1 #dbuser richard #dbpasswd sinn #subtree_cond "ldap_entries.dn LIKE CONCAT('%',?)" #insentry_stmt "INSERT INTO ldap_entries (dn,oc_map_id,parent,keyval) VALUES (?,?,?,?)" #has_ldapinfo_dn_ru no ------------------------ END slapd.conf -------------------------------
please suggest Patrick
Patai Sangbutsarakum skrev, on 16-11-2007 22:16:
I just upgrade to 2.4.6 and also Berkeley db 4.6. I'm using the same slapd.conf that was used with 2.3.38.
I have the problem in the sql backend. Slapd cannot start if slapd.conf has more than 1 sql backend at the same time. If I have 2 sql backend, from -d -1 will complain about the 2nd backend as I snipped.
Seems that if it worked with 2.3 latest and doesn't work with 2.4 any longer, you have to file an ITS - that's not the only, single thing that worked with 2.3.39 and doesn't work any longer with 2.4.6 as released (I've found only one prior to yours).
So file an ITS. Repeat the details you gave here, there.
[...]
Best,
--Tonni
openldap-software@openldap.org