Huh? Why didn't you just use ldapmodify to modify it? Or, slapcat your cn=config db, fix it in the LDIF, and reload it?
Couldn't use ldapmodify to modify it because slapd wasn't running. Couldn't use ldapmodify to modify it whilst Ubuntu version was installed because that would break *that* version. Couldn't use ldapmodify to modify it whilst new version was installed because new version wouldn't start.
I think, in retrospect, that I was hitting two problems - the wrong path in cn=config and the wrong command to try and build a new cn=config from LDIF. It is possible that the correct command (which I eventually found in another mail thread) avoids this whole issue.
On 12 December 2013 16:14, Quanah Gibson-Mount quanah@zimbra.com wrote:
--On Thursday, December 12, 2013 1:40 PM +0000 Philip Colmer philip.colmer@linaro.org wrote:
dn: cn=module{0} objectClass: olcModuleList cn: module{0} olcModulePath: /usr/lib/ldap olcModuleLoad: {0}back_hdb
olcModulePath, if defined, is referenced INSTEAD OF any environment variables like PATH or LD_LIBRARY_PATH.
/usr/lib/ldap is the Ubuntu path. The new location is /usr/local/libexec/ldap. Since I can't edit the ldif file, I put in a symbolic link.
Huh? Why didn't you just use ldapmodify to modify it? Or, slapcat your cn=config db, fix it in the LDIF, and reload it?
--Quanah
--
Quanah Gibson-Mount Architect - Server Zimbra, Inc.
Zimbra :: the leader in open source messaging and collaboration