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 1309964 - Crash in slapi_get_object_extension
Summary: Crash in slapi_get_object_extension
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: 389-ds-base
Version: 7.2
Hardware: All
OS: Linux
urgent
urgent
Target Milestone: rc
: ---
Assignee: Noriko Hosoi
QA Contact: Viktor Ashirov
URL:
Whiteboard:
Depends On: 1302823
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-02-19 06:05 UTC by Jan Kurik
Modified: 2019-10-10 11:15 UTC (History)
7 users (show)

Fixed In Version: 389-ds-base-1.3.4.0-27.el7
Doc Type: Bug Fix
Doc Text:
When a persistent search (psearch) was launched by a bind user without sufficient permissions, the access permissions object in cache previously failed to reset to point the initial pblock structure to the permanent structure. As a consequence, the ACL plug-in could crash the server due to a missing pblock object. This update ensures that the initial pblock object is reset to the permanent pblock and prevents the server from crashing in this situation.
Clone Of: 1302823
Environment:
Last Closed: 2016-03-31 22:04:44 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:0550 0 normal SHIPPED_LIVE 389-ds-base bug fix update 2016-04-01 01:52:44 UTC

Description Jan Kurik 2016-02-19 06:05:42 UTC
This bug has been copied from bug #1302823 and has been proposed
to be backported to 7.2 z-stream (EUS).

Comment 5 Sankar Ramalingam 2016-03-10 10:54:48 UTC
1). Enable memberOf plugin
[root@vm-idm-004 MMR_WINSYNC]# PORT="1189" ; ldapsearch -x -LLL -p $PORT -h localhost -D "cn=Directory Manager" -w Secret123 -b "cn=MemberOf Plugin,cn=plugins,cn=config" nsslapd-pluginEnabled
dn: cn=MemberOf Plugin,cn=plugins,cn=config
nsslapd-pluginEnabled: on

[root@vm-idm-004 MMR_WINSYNC]# PORT="1189" ; ldapsearch -x -LLL -p $PORT -h localhost -D "cn=Directory Manager" -w Secret123 -b "cn=MemberOf Plugin,cn=plugins,cn=config" memberofGroupattr
dn: cn=MemberOf Plugin,cn=plugins,cn=config
memberofGroupattr: member
memberofGroupattr: uniqueMember

2). Add about 2k users
[root@vm-idm-004 MMR_WINSYNC]# for PORT in `echo "1189"`; do Users=`ldapsearch -x -p $PORT -h localhost -D "cn=Directory Manager" -w Secret123 -b "dc=passsync,dc=com" |grep -i "dn: uid=*" |wc -l`; echo "User entries on PORT-$PORT is $Users"; done
User entries on PORT-1189 is 2016

3). Add 2k users to groups.
[root@vm-idm-004 MMR_WINSYNC]# ./AddEntry.sh Groups 1189 "ou=groups,dc=passsync,dc=com" grpcrashgrp 3 localhostNo of entries added will be 3
Adding 3 Groups to 
adding new entry "cn=grpcrashgrp3,ou=groups,dc=passsync,dc=com"

adding new entry "cn=grpcrashgrp2,ou=groups,dc=passsync,dc=com"

adding new entry "cn=grpcrashgrp1,ou=groups,dc=passsync,dc=com"

[root@vm-idm-004 MMR_WINSYNC]# PORT="1189"; ldapsearch -x -p $PORT -h localhost -D "cn=Directory Manager" -w Secret123 -b "cn=grpcrashgrp3,ou=groups,dc=passsync,dc=com" |grep -i uniqueMember | wc -l
2016


4). Run Psearch as a normal user
PORT=1189 ; /usr/lib64/mozldap/ldapsearch -r -p $PORT -h localhost -D "uid=sssssusr1,ou=people,dc=passsync,dc=com" -w Secret123 -b "dc=passsync,dc=com" -C ps:any objectclass=*


5). Run ldapmodify for the group entry and continue for an hour
[root@vm-idm-004 export]# ./bug_verify.sh 
Ldapmodify ran for about 1hr

[root@vm-idm-004 export]# cat bug_verify.sh 
#!/bin/sh

add_no=1 ; del_no=2 ; TimeNow=`date +"%-H%M"` ; After1Hour=`expr $TimeNow + 100` ; while [ $TimeNow -lt $After1Hour ]; do
ldapmodify -x -p 1189 -h localhost -D "cn=Directory Manager" -w Secret123 << EOF > /dev/null
dn: cn=grpcrashgrp3,ou=groups,dc=passsync,dc=com
changetype: modify
add: uniqueMember
uniqueMember: uid=newusr$add_no,ou=people,dc=passsync,dc=com
EOF
       
ldapmodify -x -p 1189 -h localhost -D "cn=Directory Manager" -w Secret123 << EOF > /dev/null
dn: cn=grpcrashgrp3,ou=groups,dc=passsync,dc=com
changetype: modify
delete: uniqueMember
uniqueMember: uid=oldusr$del_no,ou=people,dc=passsync,dc=com
EOF
  sleep 0.3 ; TimeNow=`date +"%-H%M"` ; del_no=`expr $del_no + 1`; add_no=`expr $add_no + 1`; done ; echo "Ldapmodify ran for about 1hr"

6). Check the status of slapd.
[root@vm-idm-004 ~]# systemctl restart dirsrv.target ; echo $?
0
[root@vm-idm-004 ~]# ps -eaf |grep -i ns-slapd > /dev/null; echo $?
0

Packages tested:
[root@vm-idm-004 ~]# rpm -qa |grep -i 389-ds
389-ds-base-devel-1.3.4.0-28.el7_2.x86_64
389-ds-base-debuginfo-1.3.4.0-28.el7_2.x86_64
389-ds-base-libs-1.3.4.0-28.el7_2.x86_64
389-ds-base-1.3.4.0-28.el7_2.x86_64


No crashes observed. Hence, marking the bug as Verified.

Comment 7 errata-xmlrpc 2016-03-31 22:04:44 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2016-0550.html


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