search

389ds / 389-ds-base

The enterprise-class Open Source LDAP server for Linux
https://www.port389.org/
Other
200 stars 82 forks source link

d2entry - Could not open id2entry err 0 - at startup when having sub-suffixes #6224

Closed progier389 closed 2 weeks ago

progier389 commented 3 weeks ago

Issue Description 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.
```

Package Version and Platform:

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 $DHOST backend create --suffix="ou=test,dc=example,dc=com" --be-name="test" --parent-suffix="dc=example,dc=com" --create-suffix
  1. Restart the Directory Server and find the ERRs. 
    
dsctl $DHOST restart
grep -A1 "Could not open id2entry" /var/log/dirsrv/slapd-$DHOST/errors


**Expected results**
No error.

**Additional context**
RHEL Bug:   https://issues.redhat.com/browse/DIRSRV-53

Triaged: https://issues.redhat.com/browse/IDMDS-4306
progier389 commented 3 weeks ago

A minor issue related to the internal search that search for referral. I think that we should limit the search to a single backend

progier389 commented 2 weeks ago

0f46d4339..4e3dc9e88 main -> main 8e6ce71d3..ae8ab2141 389-ds-base-3.0 -> 389-ds-base-3.0 dc0d81844..0f35be137 389-ds-base-2.5 -> 389-ds-base-2.5 9501c34df..43057ebc3 389-ds-base-2.4 -> 389-ds-base-2.4 99c01b8b0..47672fb37 389-ds-base-2.3 -> 389-ds-base-2.3 f9c420d11..560b13273 389-ds-base-2.2 -> 389-ds-base-2.2