[389-users] Re: [Freeipa-users] Fedora 40: new warning in ipa-healthckeck

[Rob Crittenden]

Cross-posting this on the 389-users list.

rob

Jochen Kellner via FreeIPA-users wrote:
>  
>  Hi,
>  
>  I've upgraded my freeipa server to Fedora 40 (the system was installed
>  several releases ago). After the upgrade I get the following new warning
>  from ipa-healthcheck:
>  
>    {
>      "source": "ipahealthcheck.ds.backends",
>      "check": "BackendsCheck",
>      "result": "WARNING",
>      "uuid": "875db8e3-029c-46f7-87e5-bf9a216d9637",
>      "when": "20240426184431Z",
>      "duration": "0.031642",
>      "kw": {
>        "key": "DSBLE0005",
>        "items": [
>          "nsslapd-dbcachesize",
>          "nsslapd-db-logdirectory",
>          "nsslapd-db-transaction-wait",
>          "nsslapd-db-checkpoint-interval",
>          "nsslapd-db-compactdb-interval",
>          "nsslapd-db-compactdb-time",
>          "nsslapd-db-transaction-batch-val",
>          "nsslapd-db-transaction-batch-min-wait",
>          "nsslapd-db-transaction-batch-max-wait",
>          "nsslapd-db-logbuf-size",
>          "nsslapd-db-page-size",
>          "nsslapd-db-locks",
>          "nsslapd-db-locks-monitoring-enabled",
>          "nsslapd-db-locks-monitoring-threshold",
>          "nsslapd-db-locks-monitoring-pause",
>          "nsslapd-db-private-import-mem",
>          "nsslapd-db-deadlock-policy"
>        ],
>        "msg": "Found configuration attributes that are not applicable for
> the configured backend type."
>      }
>    },
>  
>  According to
>  https://www.port389.org/docs/389ds/FAQ/Berkeley-DB-deprecation.html the
>  bdb backend is deprecated. The system was installed with
>  389-ds-base < 1.4.4.9-1.fc33.x86_64 (I see the upgrade to that version
>  in /var/log/dnf.rpm.log*. Since 3.0 new installations should use LMBD as
>  the backend. Is that true for new installations?
>  
>  What is the desired action that I should take?
>  
>  I can remove the options from the dirsrv configuration. Should I?
>  
>  Shall I switch to lmdb manually? Or is that something that
>  ipa-server-upgrade should be doing?
>  
>  Otherwise I can suppress the message in ipa-healthcheck for now. But I
>  guess I should fix my installation before the deprecated support really
>  gets dropped... Is deploying a new replica and decommisioning the old
>  server we the preferred action?
>  
>  Jochen
>