[Date Prev][Date Next] [Chronological] [Thread] [Top]

using back-sql with cn=config


Has anyone out there managed to successfully convert slapd.conf into cn=config with back-sql enabled ?

I'm on Debian 6 / OpenLDAP 2.4.33 with back-sql support (./configure --enable-sql)

According tohttp://www.openldap.org/software/release/changes.html, back-sql supports dynamic config as of version 2.4.27.

So I converted slapd.conf to slapd.d, conversion went well.

However, when I start slapd, I get the following message :
# /usr/local/libexec/slapd -u openldap -g openldap -d -1
50ff3f0a<<<  dnPrettyNormal:<cn=root,dc=example,dc=com>,<cn=root,dc=example,dc=com>
50ff3f0a olcSqlInsEntryStmt: value #0:<olcSqlInsEntryStmt>  extra cruft after<SQL expression>.
50ff3f0a config error processing olcDatabase={1}sql,cn=config:
<olcSqlInsEntryStmt>  extra cruft after<SQL expression>
50ff3f0a send_ldap_result: conn=-1 op=0 p=0
50ff3f0a send_ldap_result: err=19 matched="" text=""
50ff3f0a slapd destroy: freeing system resources.
50ff3f0a slapd stopped.
50ff3f0a connections_destroy: nothing to destroy.

The error message seems to be "extra cruft after<SQL expression>"

If I edit slapd.d/cn=config/olcDatabase={1}sql.ldif and I comment the line starting with olcSqlInsEntryStmt, then slapd starts fine.

So what's the right syntax for olcSqlInsEntryStmt ???