Chapter 4. Red Hat Directory Server 12.5 Learn about important updates and new features, known issues, and bug fixes implemented in Directory Server 12.5. 4.1. Important updates and new features Learn about new features and important updates in Red Hat Directory Server 12.5. Directory Server now delivers the 389-ds-base component from the RHEL AppStream Previously, the 389-ds-base component was delivered as part of RHEL and RHDS modules. With this update, because of demodularization efforts, RHDS no longer delivers its own copy of 389-ds-base and uses 389-ds-base from the RHEL AppStream instead. ( DIRSRV-6 ) Important updates and new features in the 389-ds-base package Important updates in Red Hat Directory Server 12.5 that are included in the 389-ds-base package are documented in Red Hat Enterprise Linux 9.5 Release Notes: 389-ds-base rebased to version 2.5.2 4.2. Bug fixes Learn about bugs fixed in Red Hat Directory Server 12.5 that have a significant impact on users. dsidm now prompts to create an ou entry Previously, when you used the dsidm utility to create a user or a group but the Organizational Unit ( ou ) entry that the user or the group must belong to did not exist, you saw the following error: With this update, if the ou entry does not exist, the dsidm utility now prompts you to create this entry. ( DIRSRV-16 ) dsctl now displays the -v option in the usage section Previously, the verbose option ( -v ) for the dsctl test db2bak -h command was not displayed in the action section of the help description ( --help , -h ). With this update, the help description now also displays the -v option. ( DIRSRV-21 ) Creating a replication agreement with dsconf now completes without a delay Previously, when you created a replication agreement by using the dsconf utility, the command hanged for a minute and only then proceeded further. With this update, a replication agreement is now created without any delays. ( DIRSRV-35 ) The Directory Server web console no longer fails to enable the audit failure logging Previously, if you attempted to enable the audit failure logging by using the Directory Server web console, the process failed. With this update, the issue has been fixed, and you can enable the audit failure logging as expected. ( DIRSRV-47 ) When starting an instance with a sub-suffix, an incorrect error is no longer logged Previously, when starting an instance with a sub-suffix, you could see the following incorrect message in the error log: The root cause of the message was that during backend initialization, a subtree search was performed on the backend to determine if the subtree contained smart referrals. In addition, the issue had a minor performance impact on search operations for the first ten minutes after the server started. With this update, the incorrect message is no longer logged and no performance impact occurs when the server starts. ( DIRSRV-53 ) Directory Server now updates the password history for pre-hashed passwords as expected Previously, when you updated your password with a hashed value, the updated password hash was not listed in your password history. With this update, the issue has been fixed, and both hashed and non-hashed password updates are now listed in the password history. ( DIRSRV-60 ) Log file timestamps now have the correct time zone Previously, the log file timestamps had the wrong timezone offset if the timezone offset was not a multiple of an hour, like America/St_johns timezone which is UTC-3:30. With this update, the timezone offset is calculated correctly. ( DIRSRV-61 ) The web console now enables replication for a sub-suffix as expected Previously, enabling replication for a sub-suffix by using the Directory Server web console failed with an error. With this update, the issue has been fixed, and you can now enable replication, and the proper replication tab is displayed in the web console. ( DIRSRV-67 ) Directory Server SNMP agent now starts as expected if an SELinux policy is enforced Previously, SELinux reported an Access Vector Cache (AVC) error when using the Directory Server SNMP agent and the agent failed to start if an SELinux policy was enforced. This was due to the SNMP agent having the incorrect permissions. With this update, the SNMP agent permissions have been changed and the SELinux policy configuration has been fixed. ( DIRSRV-76 ) Directory Server 12.5 bug fixes that are included in the 389-ds-base package are documented in Red Hat Enterprise Linux 9.5 Release Notes: Directory Server no longer ignores nsslapd-idletimeout Search operations now return large groups faster One-level scoped search no longer fails to return sub-suffixes The Referential Integrity plug-in no longer leads to the server failure The dscreate ds-root command now accepts a relative path Offline import of LDIF files now runs correctly The dsconf schema matchingrules list command now displays the new inchainMatch matching rule 4.3. Technology Previews Learn about unsupported Technology Previews in Red Hat Directory Server 12.5 that are included in the 389-ds-base package and documented in Red Hat Enterprise Linux 9.5 Release Notes: LMDB database type is available in Directory Server as a Technology Preview 4.4. Deprecated functionality Learn about deprecated functionalities in Red Hat Directory Server 12.5 that are included in the 389-ds-base package and documented in Red Hat Enterprise Linux 9.5 Release Notes: BDB backend is deprecated in 389-ds-base 4.5. Known issues Learn about known problems and, if applicable, workarounds in Directory Server 12.5. Directory Server web console does not automatically update settings that are changed outside the web console Because of the design of the Directory Server module in the Red Hat Enterprise Linux 8 web console, the web console does not automatically display the latest settings if you change the configuration outside of the console window. For example, if you change the configuration using the command line while the web console is open, the new settings are not automatically updated in the web console. This applies also if you change the configuration by using the web console on a different computer. To work around the problem, manually refresh the web console in the browser if the configuration was changed outside the console window. (BZ#1654281) (BZ#1751047) Directory Server can import LDIF files only from /var/lib/dirsrv/slapd- instance_name /ldif/ Since RHEL 8.3, Red Hat Directory Server (RHDS) uses its own private directories, and the PrivateTmp systemd directive is enabled by default for the LDAP services. As a result, RHDS can only import LDIF files from the /var/lib/dirsrv/slapd- instance_name /ldif/ directory. If the LDIF file is stored in a different directory, such as /var/tmp , /tmp , or /root , the import fails with an error similar to the following: To work around this problem, complete the following steps: Move the LDIF file to the /var/lib/dirsrv/slapd- instance_name /ldif/ directory: Set permissions that allow the dirsrv user to read the file: Restore the SELinux context: For more information, see the solution article LDAP Service cannot access files under the host's /tmp and /var/tmp directories . (BZ#2075525) Known issues in the 389-ds-base package Red Hat Directory Server 12.5 known issues that affect 389-ds-base package are documented in Red Hat Enterprise Linux 9.5 Release Notes: dsconf config replace cannot handle multivalued attributes The online backup and the online automembership rebuild tasks can acquire two locks resulting in a deadlock

Commands:
Error: 105 - 4 - 32 - No such object - [] - dc=example,dc=com
[time_stamp] - ERR - id2entry - Could not open id2entry err 0 [time_stamp] - ERR - dn2entry_ext - The dn "dc=example,dc=com" was in the entryrdn index, but it did not exist in id2entry of instance userRoot.
Could not open LDIF file "/tmp/example.ldif", errno 2 (No such file or directory)
mv /tmp/ example.ldif /var/lib/dirsrv/slapd- instance_name__/ldif/
chown dirsrv /var/lib/dirsrv/slapd- instance_name /ldif/ example.ldif
restorecon -Rv /var/lib/dirsrv/slapd- instance_name /ldif/