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 1314241 - Double free while adding entries
Summary: Double free while adding entries
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: 389-ds-base
Version: 6.0
Hardware: All
OS: Linux
urgent
urgent
Target Milestone: rc
: ---
Assignee: Noriko Hosoi
QA Contact: Viktor Ashirov
URL:
Whiteboard:
: 1196464 (view as bug list)
Depends On: 1265851
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-03 09:25 UTC by Jaroslav Reznik
Modified: 2019-10-10 11:25 UTC (History)
9 users (show)

Fixed In Version: 389-ds-base-1.2.11.15-72.el6_7
Doc Type: Bug Fix
Doc Text:
When a callback at BE_TXN in the backend add function failed on a cached entry, the function was attempting to free the entry twice instead of removing it from the cache and then freeing it. This update adds remove and free code to the backend add function and the function no longer attempts to free cached entries twice.
Clone Of: 1265851
Environment:
Last Closed: 2016-03-22 14:47:27 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:0468 0 normal SHIPPED_LIVE 389-ds-base bug fix update 2016-03-22 18:46:51 UTC

Description Jaroslav Reznik 2016-03-03 09:25:10 UTC 
This bug has been copied from bug #1265851 and has been proposed
to be backported to 6.7 z-stream (EUS).
Comment 7 Amita Sharma 2016-03-10 12:07:11 UTC 
Followed https://bugzilla.redhat.com/show_bug.cgi?id=1265851#c3

[root@ipaqa64vml slapd-PKI-IPA]# rpm -qa | grep 389
389-ds-base-1.2.11.15-72.el6_7.x86_64
389-ds-base-libs-1.2.11.15-72.el6_7.x86_64

1. IPA master-replica configuration ::
Master :: ipaqa64vml.testrelm.test
Slave :: sgi-uv2-01.testrelm.test

2. core dump is enabled

3. executed steps.sh 

[root@ipaqa64vml export]# ./steps.sh 
Password for admin: 
root.test's password: 
ipa: INFO: Setting agreement cn=meTosgi-uv2-01.testrelm.test,cn=replica,cn=dc\=testrelm\,dc\=test,cn=mapping tree,cn=config schedule to 2358-2359 0 to force synch
ipa: INFO: Deleting schedule 2358-2359 0 from agreement cn=meTosgi-uv2-01.testrelm.test,cn=replica,cn=dc\=testrelm\,dc\=test,cn=mapping tree,cn=config
Update in progress
Update in progress
Update in progress
Update in progress
Update succeeded
-------------------------
Added user "user_22474_0"
-------------------------
  User login: user_22474_0
  First name: fi
  Last name: la
  Full name: fi la
  Display name: fi la
  Initials: fl
  Home directory: /home/user_22474_0
  GECOS field: fi la
  Login shell: /bin/sh
  Kerberos principal: user_22474_0
  Email address: user_22474_0
  UID: 1487600003
  GID: 1487600003
  Password: False
  Kerberos keys available: False
-------------------------
Added user "user_22474_1"
-------------------------
  User login: user_22474_1
  First name: fi
  Last name: la
  Full name: fi la
  Display name: fi la
  Initials: fl
  Home directory: /home/user_22474_1
  GECOS field: fi la
  Login shell: /bin/sh
  Kerberos principal: user_22474_1
  Email address: user_22474_1
  UID: 1487600004
  GID: 1487600004
  Password: False
  Kerberos keys available: False
-------------------------
Added user "user_22474_2"
-------------------------
  User login: user_22474_2
  First name: fi
  Last name: la
  Full name: fi la
  Display name: fi la
  Initials: fl
  Home directory: /home/user_22474_2
  GECOS field: fi la
  Login shell: /bin/sh
  Kerberos principal: user_22474_2
  Email address: user_22474_2
  UID: 1487600005
  GID: 1487600005
  Password: False
  Kerberos keys available: False
-------------------------
.
.
.
.
.
:
.
.
-------------------------
  User login: user_22474_9
  First name: fi
  Last name: la
  Full name: fi la
  Display name: fi la
  Initials: fl
  Home directory: /home/user_22474_9
  GECOS field: fi la
  Login shell: /bin/sh
  Kerberos principal: user_22474_9
  Email address: user_22474_9
  UID: 1487600012
  GID: 1487600012
  Password: False
  Kerberos keys available: False

4. [root@ipaqa64vml slapd-PKI-IPA]# pwd
/var/log/dirsrv/slapd-PKI-IPA
[root@ipaqa64vml slapd-PKI-IPA]# grep DB_LOCK_DEADLOCK errors
[root@ipaqa64vml slapd-PKI-IPA]#echo $?
1


Hence VERIFIED.
Comment 9 errata-xmlrpc 2016-03-22 14:47:27 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-0468.html
Comment 10 Noriko Hosoi 2016-04-05 18:21:45 UTC 
*** Bug 1196464 has been marked as a duplicate of this bug. ***
Note You need to log in before you can comment on or make changes to this bug.