Uploaded image for project: 'Red Hat Directory Server'
  1. Red Hat Directory Server
  2. DIRSRV-53

Sub suffix causes "id2entry - Could not open id2entry err 0" error when the Directory Server starts

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done-Errata
    • Icon: Major Major
    • dirsrv-12.5
    • dirsrv-12.2
    • 389-ds-base
    • None
    • rhel-sst-idm-ds
    • 0
    • False
    • Hide

      None

      Show
      None
    • Yes
    • None
    • Bug Fix
    • Hide
      .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:

      [literal,subs="+quotes"]
      ....
      [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.
      ....

      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.
      Show
      .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: [literal,subs="+quotes"] .... [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. .... 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.
    • 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".
        ~~~
      1. 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"
      2. dbscan r -f /var/lib/dirsrv/slapd$DHOST/db/test/id2entry.db | head -2
        id 1
        rdn: ou=test,dc=example,dc=com
        ~~~

              progier Pierre Rogier
              rhn-support-msugaya Muneaki Sugaya
              IdM DS QE IdM DS QE
              Evgenia Martyniuk Evgenia Martyniuk
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: