[ltb-dev] [LDAP Tool Box - Feature #369] (Assigned) Upgrading OpenLDAP and debugging procedures

noreply at lsc-project.org noreply at lsc-project.org
Mon Nov 28 16:23:59 CET 2011

Issue #369 has been updated by Clément OUDOT.

Category set to OpenLDAP RPM
Status changed from New to Assigned
Assigned to set to Clément OUDOT

Hi Nick,

of course the upgrade will not touch your configuration. To know why, you can check the openldap-ltb.spec and look for %config macros, that tell RPM not to replace the configuration:

%files -n openldap-ltb
%defattr(-, root, root, 0755)
%config(noreplace) %{ldapserverdir}/etc/openldap/slapd.conf
%config(noreplace) %{ldapserverdir}/etc/openldap/ldap.conf
%config(noreplace) /etc/default/slapd
%config(noreplace) /etc/logrotate.d/openldap
%exclude %{check_password_conf}
%exclude %{ldapserverdir}/%{_lib}/check_password.so

If we decide to upgrade BDB, then we need to do a backup/restore from the data. But for now, the upgrade is OK.

Feature #369: Upgrading OpenLDAP and debugging procedures

Author: Nick Milas
Status: Assigned
Priority: Normal
Assigned to: Clément OUDOT
Category: OpenLDAP RPM
Target version: 


Just a question: Can we simply upgrade your really fine LTB OpenLDAP releases e.g. from v2.4.26 to .27 by running rpm -Uvh ?

Will upgrade respect (keep safe): 

1. Current Configuration (cn=config or slapd.conf based as specified in /usr/local/openldap/etc/openldap/)?
2. Actual data and custom DB_CONFIG file (as maintained by BDB in /usr/local/openldap/var/openldap-data/)?
3. Custom schema directory in default directory (/usr/local/openldap/etc/openldap/)? Default schema directory in our installation includes custom schemas.
4. Customized /etc/default/slapd?
5. Customized ldap.conf (in /usr/local/openldap/etc/openldap/)?
6. Any other custom settings (which?)?

...or we should keep backups and restore after upgrade? 

Yes, I know backups are always welcome, but I am wondering about the normal/expected upgrade procedure/behavior.

Also, if we want to use the debugging package in order to do back trace with debugging symbols, is there any suggested practice/methodology?

Please, advise!

Thanks both for your packages and for your assistance,

You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://tools.lsc-project.org/my/account
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ltb-project.org/pipermail/ltb-dev/attachments/20111128/04345f22/attachment.htm>

More information about the ltb-dev mailing list