wiki: https://fedoraproject.org/wiki/Changes/389_Directory_Server_3.2.0
This is a proposed Change for Fedora Linux. This document represents a proposed Change. As part of the Changes process, proposals are publicly announced in order to receive community feedback. This proposal will only be implemented if approved by the Fedora Engineering Steering Committee 🔗 <https://fedoraproject.org/wiki/Changes/389_Directory_Server_3.2.0#Summary> Summary[ Starting from 389-ds-base version 3.2.0, the directory server no longer supports the deprecated BerkeleyDB, so LDMB database must be used. Users still using BerkeleyDB will have to migrate their data. 🔗 <https://fedoraproject.org/wiki/Changes/389_Directory_Server_3.2.0#Detailed_Description> Detailed Description 389-ds-base support of BerkeleyDB is deprecated since F40: Changes/389_Directory_Server_3.0.0 <https://fedoraproject.org/wiki/Changes/389_Directory_Server_3.0.0>. In F43 with 389-ds-base version 3.2.0: - 389-ds-base dependency towards libdb is removed. - A new 389-ds-base-robdb-libs package implements a BerkeleyDb reader that allows exporting databases into ldif and performing the migration toward lmdb. This package should be supported until at least F45 🔗 <https://fedoraproject.org/wiki/Changes/389_Directory_Server_3.2.0#Upgrade/compatibility_impact> Upgrade/compatibility impact - The directory no longer supports the BerkeleyDB implementation that is obsolete since Fedora 40 [1] <https://fedoraproject.org/wiki/Changes/389_Directory_Server_3.0.0>. - Directory server instances already using lmdb as database are not impacted. (typically those created with Fedora 40 and after) - freeipa is not impacted because it already uses lmdb since Fedora 40 - The other applications that use the directory server through LDAP API are not impacted by the directory server database internal implementation. - Data migration is required if the Directory Server instances are still configured with BerkeleyDB. - In that case, the data migration should then be performed using dsctl dblib bdb2mdb command or manually following the 389ds Berkeley DB deprecation FAQ [2] <https://www.port389.org/docs/389ds/FAQ/Berkeley-DB-deprecation.html#manual-method---export-to-ldif> instructions 🔗 <https://fedoraproject.org/wiki/Changes/389_Directory_Server_3.2.0#User_Experience> User Experience[edit <https://fedoraproject.org/w/index.php?title=Changes/389_Directory_Server_3.2.0&action=edit§ion=12> ] Directory server instances created since Fedora 40 and using the default lmdb database are not impacted (that is typically the case for freeipa users). But users still using BerkeleyDB (either because they have not yet migrated or because they explicitly choose to use BerkeleyDB) are required to migrate to lmdb. If this step is not done, the instance will not be able to start after the upgrade and the following error message is displayed in the dirsrv error log and in the system journal: bdb implementation is no longer supported. Directory server cannot be started without migrating to lmdb first. To migrate, please run: dsctl instanceName dblib bdb2mdb User then needs to migrate the data either using the dsctl command or manually by following the https://www.port389.org/docs/389ds/FAQ/Berkeley-DB-deprecation.html#manual-method---export-to-ldif steps -- -- 389 Directory Server Development Team
-- _______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@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/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
