[389-users] Re: Help with dblib bdb2mdb

For healthcheck, I see 2 possibilities:
 [1] NSSLAPD_DB_LIB=bdb is set in your environment (saying lib389 that bdb is used ...) 
 [2] There is a bug somewhere. (which seems a bit weird since 'dsconf supplier1 backend config  get' is working as expected ...)
       BTW, Which exact 389-ds-base version are you using ? and on which platform ?

On Thu, Aug 29, 2024 at 7:24 PM Alessio <alciregi@posteo.net> wrote:

On 29.08.2024 18:15, Pierre Rogier wrote:
> [3] Healthcheck reports '"BDB is still used as backend"'
>      That one is worrisome and a bit surprising because the db type
> set set off line by writing directly in the dse.ldif        after
> exporting the databases (and before importing them)
> 'dsconf supplier1 backend config  get | grep -i
> nsslapd-backend-implement ' or
> 'grep -i nsslapd-backend-implement
> /etc/dirsrv/slapd-instanceName/dse.ldif' should tell you which
> database is really used.

Thank you very much for the prompt answer, Pierre.
Yes, these two commands report that nsslapd-backend-implement is mdb.
So I should be confident that the migration was successful.
What about healthcheck stating otherwise?

Thanks,
Alessio

--
_______________________________________________
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 389-users-leave@lists.fedoraproject.org
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.fedoraproject.org/archives/list/389-users@lists.fedoraproject.org
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue

--

--

389 Directory Server Development Team