-
Bug
-
Resolution: Unresolved
-
Major
-
dirsrv-12.2
-
None
-
sst_idm_ds
-
0
-
False
-
-
Yes
-
None
-
Pass
-
+
-
Bug Fix
-
-
Proposed
Description of problem:
Sub suffix causes the following error when the Directory Server starts
~~~
ERR - id2entry - Could not open id2entry err 0
ERR - dn2entry_ext - The dn "ou=test,dc=example,dc=com" was in the entryrdn index, but it did not exist in id2entry of instance test.
~~~
Version-Release number of selected component (if applicable):
389-ds-base-2.2.7-3.module+el9dsrv+18864+4949f8c5.x86_64
How reproducible:
Always
Steps to Reproduce:
1. Install 389-ds-base-2.2.7-3.module+el9dsrv+18864+4949f8c5.x86_64
2. Set up as follows
DHOST=$(hostname -s)
cat << EOF > /root/$DHOST.inf
[general]
[slapd]
instance_name = $DHOST
root_password = password1
[backend-userroot]
create_suffix_entry = True
suffix = dc=example,dc=com
EOF
dscreate from-file /root/$DHOST.inf
dsconf -D "cn=Directory Manager" -w password1 ldap://$DHOST backend create --suffix="ou=test,dc=example,dc=com" --be-name="test" --parent-suffix="dc=example,dc=com" --create-suffix
3. Restart the Directory Server and find the ERRs.
dsctl $DHOST restart
grep -A1 "Could not open id2entry" /var/log/dirsrv/slapd-9ds0/errors
Actual results:
The ERRs are logged.
Expected results:
The ERRs are not logged.
Additional info:
- The issue doesn't occur with 389-ds-base-2.2.4-3.el9.x86_64
- Indexes for ou=test,dc=example,dc=com and dc=example,dc=com don't work.
- id2entry.db seems to have "ou=test,dc=example,dc=com".
~~~
- dbscan
r -f /var/lib/dirsrv/slapd$DHOST/db/test/entryrdn.db
ou=test,dc=example,dc=com
ID: 1; RDN: "ou=test,dc=example,dc=com"; NRDN: "ou=test,dc=example,dc=com" - dbscan
r -f /var/lib/dirsrv/slapd$DHOST/db/test/id2entry.db | head -2
id 1
rdn: ou=test,dc=example,dc=com
~~~
- external trackers
- links to
-
RHBA-2024:136844 redhat-ds:12 bug fix update