On Пан, 25 мая 2026, Ian Kumlien wrote:
On Mon, May 25, 2026 at 11:18 AM Alexander Bokovoy <[email protected]> wrote:
On Пан, 25 мая 2026, Ian Kumlien wrote:
>So they are two different setups running the same version.
>
>I find nothing in 389-ds that points to the shm - the problem is more
>that migration as in ipa-server-upgrade hasn't fixed this even if it
>should in my opinion
On my fresh test deployment I also have no /dev/shm/slapd-IPA-TEST and
'dsctl IPA-TEST healthcheck' produces no errors. This is Fedora Rawhide,
so it uses lmdb by default.
I looked at the healthcheck code. This particular check (in ds.backends)
ensures old BDB files removed after migration. But it is coded without
defence from the file path missing but defined (or derived when missing)
in configuration.
I think what you could do is set it to the correct value:
# dsconf slapd-IPA-TEST backend config set --db-home-directory
/var/lib/dirsrv/slapd-IPA-TEST/db
So, dsconf slapd-XERCES-LAN backend config get | grep shm returns nothing.
Changing it changes nothing (in the output of get) and the error is
still there after ...
Then I'd suggest opening an issue for 389-ds:
https://github.com/389ds/389-ds-base/issues/
--
/ Alexander Bokovoy
Sr. Principal Software Engineer
Security / Identity Management Engineering
Red Hat Limited, Finland
--
_______________________________________________
FreeIPA-users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedorahosted.org/archives/list/[email protected]
Do not reply to spam, report it:
https://forge.fedoraproject.org/infra/tickets/issues/new
