True, but for that you'd have to check for that and not expect everything to be fine when the main ldap is already set up right. Or at least the maintainer would have to have written an actual backup script or at least written a description that actually works. I would also have taken a path of just having the upgrade fail and roll back when such incompatibilities are found.
What would be the easiest way to get slapd back up and running? Would a simple "changetype: modify" and "replace: " for any changes that actually needed to be done do the trick? I mean the main part in the description was to just replace all mentions of hdb with lmdb, that wouldn't be that much work.
Richard
Am 24.07.2023 um 19:16 schrieb Quanah Gibson-Mount:
--On Monday, July 24, 2023 8:13 PM +0200 Richard Rosner rrosner@fsmuw.rwth-aachen.de wrote:
That's very interesting. I'm only doing what the guide tells me to do. If it tells me this is supposed to work, I expect it to work. So it seems I'll have to take this up to the maintainer of the package as their backup script is broken.
It's more of a literal backup of the exact contents of cn=config (since cn=config is text) than a backup meant to be used by slapadd. Since it's from OpenLDAP 2.4, you would have to have a 2.4 slapat to export it to LDIF. It's unfortunate, because an actual backup made by slapcat prior to the upgrade would be easier to work with for the purposes of upgrading to LMDB.
The general advice for the last 7-8 years was to update your system to use LMDB while on OpenLDAP 2.4.
--Quanah