Bug 2290494
| Summary: | 389DirectoryServer Process Stops When Setting up Sorted VLV Index | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Directory Server | Reporter: | secioss <devel> | ||||||
| Component: | 389-ds-base | Assignee: | LDAP Maintainers <idm-ds-dev-bugs> | ||||||
| Status: | CLOSED MIGRATED | QA Contact: | LDAP QA Team <idm-ds-qe-bugs> | ||||||
| Severity: | medium | Docs Contact: | Evgenia Martynyuk <emartyny> | ||||||
| Priority: | unspecified | ||||||||
| Version: | 12.4 | CC: | idm-ds-dev-bugs, vashirov | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2024-06-26 13:51:58 UTC | Type: | Bug | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Embargoed: | |||||||||
| Attachments: |
|
||||||||
|
Description
secioss
2024-06-05 01:56:43 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.
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
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. |