This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
Bug 2290494 - 389DirectoryServer Process Stops When Setting up Sorted VLV Index
Summary: 389DirectoryServer Process Stops When Setting up Sorted VLV Index
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Directory Server
Classification: Red Hat
Component: 389-ds-base
Version: 12.4
Hardware: Unspecified
OS: Linux
unspecified
medium
Target Milestone: ---
: ---
Assignee: LDAP Maintainers
QA Contact: LDAP QA Team
Evgenia Martynyuk
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2024-06-05 01:56 UTC by secioss
Modified: 2024-06-26 13:51 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2024-06-26 13:51:58 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Screenshots that reproduce the above issue (12.22 KB, application/zip)
2024-06-05 01:56 UTC, secioss
no flags Details
This is the English version of 20240604_Redhat.xlsx. (11.93 KB, application/zip)
2024-06-05 02:23 UTC, secioss
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker   DIRSRV-62 0 None None Red Hat Issue Tracker 2024-06-26 13:51:56 UTC

Description secioss 2024-06-05 01:56:43 UTC
Created attachment 2036370 [details]
Screenshots that reproduce the above issue

It was unclear whether to specify the version of 389ds with the version specified above, so the OS and 389ds packages that occurred below are listed. Please verify.

I am writing to inquire about the issue mentioned in the subject line. When executing the command specified in "Issue 1," following the steps outlined in "Execution Command 1," the LDAP process (dirsrv@389ds) encounters an error and stops, as described in "Error Message."

Furthermore, as per "Issue 2," after executing the command specified in "Execution Command 2" following the steps outlined, though the addition of data is successful with the sort order "uid:2.5.13.2," the process encounters a similar error upon restarting.

Could you please provide insight into the cause of these errors and any possible solutions?

[OS Information]
NAME="Red Hat Enterprise Linux"
VERSION="8.9 (Ootpa)"
ID="rhel"
ID_LIKE="fedora"
VERSION_ID="8.9"
PLATFORM_ID="platform:el8"
PRETTY_NAME="Red Hat Enterprise Linux 8.9 (Ootpa)"
ANSI_COLOR="0;31"
CPE_NAME="cpe:/o:redhat:enterprise_linux:8::baseos"
HOME_URL="https://www.redhat.com/"
DOCUMENTATION_URL="https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8"
BUG_REPORT_URL="https://bugzilla.redhat.com/"
REDHAT_BUGZILLA_PRODUCT="Red Hat Enterprise Linux 8"
REDHAT_BUGZILLA_PRODUCT_VERSION=8.9
REDHAT_SUPPORT_PRODUCT="Red Hat Enterprise Linux"
REDHAT_SUPPORT_PRODUCT_VERSION="8.9"

[DirectoryService]
389-ds-base-1.4.3.37-2.module+el8.9.0+20974+3405b7e6.x86_64
389-ds-base-libs-1.4.3.37-2.module+el8.9.0+20974+3405b7e6.x86_64
389-ds-base-legacy-tools-1.4.3.37-2.module+el8.9.0+20974+3405b7e6.x86_64

[Issue 1]
Create search entries
Add index to entries (--sort with "uid:2.5.13.2" specified)
LDAP process (dirsrv@389ds) stops due to error upon adding index.

[Execution Command 1]
dsconf -D "cn=<rootDN>" -w <password> ldaps://localhost backend vlv-index add-search --name "VLV People" --search-base "ou=People,<baseDN>" --search-filter "<filter>" --search-scope 2 userRoot
dsconf -D "cn=<rootDN>" -w <password> ldaps://localhost backend vlv-index add-index --index-name "SORT_UID" --sort "uid:2.5.13.2" --parent-name "VLV People" --index-it "<baseDN>"

[Issue 2]
Create search entries
Add index to entries (--sort with "uid" specified)
Execute ldapsearch command with VLV options to confirm VLV index search in access logs.
Add index to entries (--sort with "uid:2.5.13.2" specified)
LDAP process (dirsrv@389ds) does not stop upon adding index.
LDAP process (dirsrv@389ds) encounters an error upon adding data after restarting the process.

[Execution Command 2]
dsconf -D "cn=<rootDN>" -w <password> ldaps://localhost backend vlv-index add-search --name "VLV People" --search-base "ou=People,<baseDN>" --search-filter "<filter>" --search-scope 2 userRoot
dsconf -D "cn=<rootDN>" -w <password> ldaps://localhost backend vlv-index add-index --index-name "SORT_UID" --sort "uid" --parent-name "VLV People" --index-it "dc=<baseDN>"
ldapsearch -D "cn=<rootDN>" -w <password> -H ldaps://localhost -b "ou=People,<baseDN>" -x "<filter>" "distinguishedName" -E 'sss=uid:2.5.13.2' -E 'vlv=0/999999/0/0'
dsconf -D "cn=<rootDN>" -w <password> ldaps://localhost backend vlv-index add-index --index-name "SORT_UID_2" --sort "uid:2.5.13.2" --parent-name "VLV People" --index-it "<baseDN>"

[Error Message (/var/log/dirsrv/slapd-389ds/access)]
ERR - mr_wrap_mr_index_sv_fn - No plugin specified

[Reference Site]
https://access.redhat.com/documentation/en-us/red_hat_directory_server/12/html/managing_indexes/proc_creating-a-vlv-index-using-the-command-line-to-improve-the-speed-of-vlv-queries_assembly_using-the-virtual-list-view-control-to-request-a-contiguous-subset-of-a-large-search-result

Kazuki Sasaki
SECIOSS Co., Ltd.

Comment 1 secioss 2024-06-05 02:23:31 UTC
Created attachment 2036371 [details]
This is the English version of 20240604_Redhat.xlsx.

Since the materials posted at the time were in Japanese, we have attached the English version.

Comment 2 Viktor Ashirov 2024-06-06 02:35:27 UTC
Hi,

thank you for the bug report.
I reproduced this on RHEL9 too, changing the RHDS version to 12.4.

After running these commands on a fresh instance I see a server crash:
# dsconf localhost backend vlv-index add-search --name "VLV People" --search-base "ou=People,dc=example,dc=com" --search-filter '(objectClass=*)' --search-scope 2 userRoot
# dsconf localhost backend vlv-index add-index --index-name "SORT_UID" --sort "uid:2.5.13.2" --parent-name "VLV People" --index-it "dc=example,dc=com"


# coredumpctl gdb
...

Program terminated with signal SIGSEGV, Segmentation fault.
#0  bdb_dbival2dbt (isresponse=<optimized out>, dbt=0x7fb9eefebd00, dbi=0x8) at ldap/servers/slapd/back-ldbm/db-bdb/bdb_layer.c:6400
6400        dbt->data = dbi->data;
[Current thread is 1 (Thread 0x7fb9eefed640 (LWP 27200))]
(gdb) bt
#0  bdb_dbival2dbt (isresponse=<optimized out>, dbt=0x7fb9eefebd00, dbi=0x8) at ldap/servers/slapd/back-ldbm/db-bdb/bdb_layer.c:6400
#1  bdb_dbival2dbt (dbi=dbi@entry=0x8, dbt=dbt@entry=0x7fb9eefebd00, isresponse=isresponse@entry=0)
    at ldap/servers/slapd/back-ldbm/db-bdb/bdb_layer.c:6389
#2  0x00007fba0b3c1633 in bdb_public_db_op (db=0x7fb9f86baa00, txn=0x7fb9f86df000, op=DBI_OP_PUT, key=0x8, data=0x7fb9eefebde0)
    at ldap/servers/slapd/back-ldbm/db-bdb/bdb_layer.c:6702
#3  0x00007fba0b3b1e75 in do_vlv_update_index
    (txn=0x7fb9eefebf50, li=<optimized out>, pb=<optimized out>, pIndex=0x7fb9f842bf00, entry=0x7fb9f859e1e0, insert=1)
    at ldap/servers/slapd/back-ldbm/vlv.c:801
#4  0x00007fba0b3cae99 in bdb_db2index (pb=0x7fb9f806c680) at ldap/servers/slapd/back-ldbm/db-bdb/bdb_ldif2db.c:2031
#5  0x00007fba0b3ac263 in ldbm_back_ldbm2index (pb=0x7fb9f806c680) at ldap/servers/slapd/back-ldbm/ldif2ldbm.c:228
#6  0x00007fba0f762d19 in task_index_thread (arg=0x7fb9f806c680) at ldap/servers/slapd/task.c:1805
#7  0x00007fba0f962bd4 in _pt_root (arg=0x7fb9f8541d00) at pthreads/../../../../nspr/pr/src/pthreads/ptthread.c:201
#8  0x00007fba0f289c02 in start_thread (arg=<optimized out>) at pthread_create.c:443
#9  0x00007fba0f30ec40 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81

Comment 3 Viktor Ashirov 2024-06-26 13:51:58 UTC
This BZ has been automatically migrated to Red Hat Issue Tracker https://issues.redhat.com/browse/DIRSRV-62. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated. Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.


Note You need to log in before you can comment on or make changes to this bug.