Correction - actually, the page cited does mention changing the
ownership of the data files. The thing which bit me was that I'd used
several different data directories, and had to change the ownership of
the files in all of them.
On Wed, 2026-05-13 at 13:45 +0100, Peter Duffy wrote:
> When I upgraded to daedalus, my openldap setup wouldn't work any
> more.
> The reason was that openldap had gone from 2.4 to 2.5, and that
> included several breaking changes: from my point of view, the one
> which
> caused the problem was that they'd dropped the bdb backend, which was
> the one which my directory was using.
>
> It wasn't a critical issue (I haven't used the directory for a while)
> and the fix looked fairly horrendous (I managed a big LDAP directory
> for several years, but it was a long time ago, and I'd forgotten most
> of what I knew) - so I didn't bother about it for a while. But I got
> sick of the complaints from the email client that it couldn't access
> LDAP, so I finally decided to fix it.
>
> It took about an hour, and at the end of it, slapd was happy again,
> and
> the directory can be accessed. Here's the page which proved most
> helpful:
>
> https://discourse.ubuntu.com/t/service-migrating-from-openldap-2-4-x-to-2-5-x/23807
>
> It wasn't the whole story: there were a number of configuration
> attributes (things like olcDbCacheSize, olcDbLinearIndex, etc.) which
> were supported for bdb but not apparently for mdb. Every time I tried
> to run slapadd and restore the configuration, and it wibbled about
> not
> finding a config attribute, I just deleted the line from the
> config.ldif file and tried again. Eventually it worked, and I was
> then
> able to restore the directory backups. However, I was still not out
> of
> the woods: when I tried to start the slapd service, it got
> "permission
> denied" when trying to access the databases. I had to find the data
> files and change the ownership to openldap - that isn't mentioned in
> the above page.
>
> Just thought I'd mention, just in case anyone else is struggling with
> this or hits it in the future.
> _______________________________________________
> Dng mailing list
> Dng@???
> Manage your subscription:
> https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
> Archive: https://lists.dyne.org/lurker/list/dng.en.html