When slapcat-ing a 2.4 accesslog database and slapadd-ing it to a 2.5 instance, slapd will segfault on startup (specifically logpurge) due to a missing minCSN, which was added in 2.5 [1].
Though I haven't done too much analysis on the correct fix, 2 options are:
1. Add the minCSN to your accesslog LDIF. I simply used the entryCSN of the accesslog suffix. 2. Check that li->li_mincsn is not null in log_old_lookup(). Simple patch attached.
I attached a minimal slapd conf and accesslog.ldif to duplicate the issue.
[1] https://git.openldap.org/openldap/openldap/-/commit/66a743f119c85ee83f2efcdd...
--On Thursday, October 14, 2021 11:54 AM -0400 David Hawes dhawes@vt.edu wrote:
When slapcat-ing a 2.4 accesslog database and slapadd-ing it to a 2.5 instance, slapd will segfault on startup (specifically logpurge) due to a missing minCSN, which was added in 2.5 [1].
Though I haven't done too much analysis on the correct fix, 2 options are:
- Add the minCSN to your accesslog LDIF. I simply used the entryCSN
of the accesslog suffix. 2. Check that li->li_mincsn is not null in log_old_lookup(). Simple patch attached.
Thanks, filed as https://bugs.openldap.org/show_bug.cgi?id=9720
Regards, Quanah
--
Quanah Gibson-Mount Product Architect Symas Corporation Packaged, certified, and supported LDAP solutions powered by OpenLDAP: http://www.symas.com
openldap-technical@openldap.org
-
David Hawes -
Quanah Gibson-Mount