Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1166460

Summary: Valgrind reports invalid read and crashes in ldbm_usn_init
Product: Red Hat Enterprise Linux 6 Reporter: Marc Sauton <msauton>
Component: 389-ds-baseAssignee: Noriko Hosoi <nhosoi>
Status: CLOSED DUPLICATE QA Contact: Sankar Ramalingam <sramling>
Severity: medium Docs Contact:
Priority: high    
Version: 6.6CC: jgalipea, msauton, nkinder, rmeggins
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-02-19 01:50:34 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:

Description Marc Sauton 2014-11-21 03:01:54 UTC
Description of problem:

ns-slapd 1.2.11 / RHDS 9.1 crash:

with stack trace similar to
https://fedorahosted.org/389/ticket/47659

will likely provide a hotfix, this bug report is for a backport request in 1.2.11


messages:         Nov 20 14:30:43 somehost kernel: ns-slapd[9933]: segfault at 0 ip 00007fa012731a76 sp 00007f9fa57fa308 error 4 in libnss3.so[7fa0126dd000+136000]
messages-20141026:Oct 20 23:20:36 somehost kernel: ns-slapd[2080]: segfault at 0 ip 00007fd3ff481a76 sp 00007fd3539f7308 error 4 in libnss3.so[7fd3ff42d000+136000]
messages-20141102:Oct 26 22:41:25 somehost kernel: ns-slapd[9306]: segfault at 0 ip 00007f0f3a9d5a76 sp 00007f0eaebfc308 error 4 in libnss3.so[7f0f3a981000+136000]
messages-20141109:Nov  8 12:05:39 somehost kernel: ns-slapd[513]:  segfault at 0 ip 00007ffa2f5fba76 sp 00007ff9ca5f52f8 error 4 in libnss3.so[7ffa2f5a7000+136000]
messages-20141116:Nov 15 07:19:26 somehost kernel: ns-slapd[2623]: segfault at 0 ip 00007f7204c43a76 sp 00007f7160df92f8 error 4 in libnss3.so[7f7204bef000+136000]


Core was generated by `/usr/sbin/ns-slapd -D /etc/dirsrv/slapd-ds1 -i /var/run/dirsrv/slapd-ds1'.
Program terminated with signal 11, Segmentation fault.
#0  0x00007fdd44dfb320 in ldbm_usn_init (li=0x7ca4f0) at ldap/servers/slapd/back-ldbm/ldbm_usn.c:83
83              slapi_log_error(SLAPI_LOG_BACKLDBM, "ldbm_usn_init",

(gdb) bt
#0  0x00007fdd44dfb320 in ldbm_usn_init (li=0x7ca4f0) at ldap/servers/slapd/back-ldbm/ldbm_usn.c:83
#1  0x00007fdd44e08a44 in ldbm_back_start (pb=<value optimized out>) at ldap/servers/slapd/back-ldbm/start.c:300
#2  0x00007fdd4e3f094a in plugin_call_func (list=0x7c9b90, operation=212, pb=0x9ba2e0, call_one=1) at ldap/servers/slapd/plugin.c:1453
#3  0x00007fdd4e3f1398 in plugin_call_one (argc=7, argv=0x7fff263f56c8, errmsg=<value optimized out>, operation=-44) at ldap/servers/slapd/plugin.c:1421
#4  plugin_dependency_startall (argc=7, argv=0x7fff263f56c8, errmsg=<value optimized out>, operation=-44) at ldap/servers/slapd/plugin.c:1210
#5  0x000000000041f4b0 in main (argc=7, argv=0x7fff263f56c8) at ldap/servers/slapd/main.c:1174
(gdb)
(gdb) list
78
79          /* Search each namingContext in turn */
80          for ( sdn = slapi_get_first_suffix( &node, 0 ); sdn != NULL;
81                sdn = slapi_get_next_suffix_ext( &node, 0 )) {
82              be = slapi_mapping_tree_find_backend_for_sdn(sdn);
83              slapi_log_error(SLAPI_LOG_BACKLDBM, "ldbm_usn_init",
84                          "backend: %s%s\n", be->be_name, isglobal?" (global mode)":"");
85              rc = usn_get_last_usn(be, &last_usn);
86              if (0 == rc) { /* only when the last usn is available */
87                  if (isglobal) {
(gdb)



Thread 1 (Thread 0x7fdd4e8727c0 (LWP 57780)):
#0  0x00007fdd44dfb320 in ldbm_usn_init (li=0x7ca4f0) at ldap/servers/slapd/back-ldbm/ldbm_usn.c:83
        sdn = <value optimized out>
        node = 0x757f80
        rc = <value optimized out>
        be = <value optimized out>
        last_usn = 0
        global_last_usn = <value optimized out>
        isglobal = 1
        isfirst = <value optimized out>



Version-Release number of selected component (if applicable):

reported and stack trace read with
389-ds-base-1.2.11.15-30.el6_5.x86_64
redhat-release-server-6Server-6.5.0.1.el6.x86_64

and
389-ds-base-1.2.11.15-34.el6_5.x86_64
redhat-release-server-6Server-6.5.0.1.el6.x86_64

likely on any 1.2.11


How reproducible:
N/A

Steps to Reproduce:
1. N/A
2.
3.

Actual results:


Expected results:


Additional info:

Comment 3 Sankar Ramalingam 2014-12-17 15:23:17 UTC
Is this reproducible with latest builds of 389-ds-base-1.2.11.15-48?

Can you add steps to reproduce this crash?

Comment 5 Noriko Hosoi 2015-02-19 01:50:34 UTC

*** This bug has been marked as a duplicate of bug 1193243 ***