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 1086907 - Performing deletes during tombstone purging results in operation errors
Summary: Performing deletes during tombstone purging results in operation errors
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: 389-ds-base
Version: 6.6
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Noriko Hosoi
QA Contact: Sankar Ramalingam
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-04-11 19:32 UTC by Noriko Hosoi
Modified: 2020-09-13 21:02 UTC (History)
5 users (show)

Fixed In Version: 389-ds-base-1.2.11.15-34.el6
Doc Type: Bug Fix
Doc Text:
Cause: Deleting entries while tombstone purging is occurring Consequence: Some delete operations will fail with an error 1. Fix: The error 1 was triggered because the parent entry was replaced in the entry cache. The fix retries to obtain the parent entry until it succeeds or times out. Result: Delete operations succeed as expected
Clone Of:
: 1086908 (view as bug list)
Environment:
Last Closed: 2014-10-14 07:54:53 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github 389ds 389-ds-base issues 1103 0 None None None 2020-09-13 21:02:48 UTC
Red Hat Product Errata RHBA-2014:1385 0 normal SHIPPED_LIVE 389-ds-base bug fix and enhancement update 2014-10-14 01:27:42 UTC

Description Noriko Hosoi 2014-04-11 19:32:34 UTC 
Description of problem:
There is a race condition when looking up the parent of a deleted entry, where the cached entry is replaced by tombstone purging(updating the parents tombstonenumsubordinate attribute). The cached entry gets removed just after retrieving the entry from the cache, but before it can be locked (cache_lock_entry). This results in an operations error when trying to lock the entry that was just retrieved from the cache.
Comment 1 mreynolds 2014-04-21 15:30:00 UTC 
Upstream ticket

https://fedorahosted.org/389/ticket/47771
Comment 2 mreynolds 2014-04-21 17:30:17 UTC 
Verification steps:

[1]  Create one instance, but enable/setup replication(no agreement needed)
[2]  Set the tombstone purging interval to 20 seconds

  example: 

dn: cn=replica,cn=dc\3Dexample\2Cdc\3Dcom,cn=mapping tree,cn=config
changetype: modify
replace: nsDS5ReplicaTombstonePurgeInterval
nsDS5ReplicaTombstonePurgeInterval: 20

[3]  Import or add 500 entries
[4]  Delete those 500 entries
[5]  All the delete operations should pass, and not report an error 1(operations error), or any error for that fact.
Comment 4 Viktor Ashirov 2014-08-06 13:25:26 UTC 
1. Create one instance, but enable/setup replication (no agreement needed)
2. Set the tombstone purging interval to 20 seconds

$ ldapmodify -D "cn=Directory Manager" -w Secret123  -H ldap://localhost:1389 << EOF
> dn: cn=changelog5,cn=config
> changetype: add
> objectclass: top
> objectclass: extensibleObject
> cn: changelog5
> nsslapd-changelogdir: /var/lib/dirsrv/slapd-rhel6ds/changelogdb
> nsslapd-changelogmaxage: 10d
> EOF
adding new entry "cn=changelog5,cn=config"

$ ldapmodify -D "cn=Directory Manager" -w Secret123  -H ldap://localhost:1389 << EOF
> dn: cn=replica,cn=dc\=example\,dc\=com,cn=mapping tree,cn=config
> changetype: add
> objectclass: top
> objectclass: nsds5replica
> objectclass: extensibleObject
> cn: replica
> nsds5replicaroot: dc=example,dc=com
> nsds5replicaid: 7
> nsds5replicatype: 3
> nsds5flags: 1
> nsds5ReplicaPurgeDelay: 604800
> nsds5ReplicaBindDN: cn=replication manager,cn=config
> nsDS5ReplicaTombstonePurgeInterval: 20
> EOF
adding new entry "cn=replica,cn=dc\=example\,dc\=com,cn=mapping tree,cn=config"

3. Import or add 500 entries
$ ldclt -h localhost -p 1389 -D "cn=Directory Manager" -w Secret123 -f cn=MrXXXXX -b "ou=people,dc=example,dc=com" -e add,person,incr,noloop,commoncounter -r0 -R499 -n 1 -v
ldclt version 4.23
/usr/bin/ldclt-bin -h localhost -p 1389 -D "cn=Directory Manager" -w Secret123 -f cn=MrXXXXX -b ou=people,dc=example,dc=com -e add,person,incr,noloop,commoncounter -r0 -R499 -n 1 -v
Process ID         = 24242
Host to connect    = localhost
Port number        = 1389
Bind DN            = cn=Directory Manager
Passwd             = Secret123
Referral           = on
Base DN            = ou=people,dc=example,dc=com
Filter             = "cn=MrXXXXX"
Max times inactive = 3
Max allowed errors = 1000
Number of samples  = -1
Number of threads  = 1
Total op. req.     = -1
Running mode       = 0x0e040201
Running mode       = verbose incremental commoncounter noloop add class=person
LDAP oper. timeout = 30 sec
Sampling interval  = 10 sec
Values range       = [0 , 499]
Filter's head      = "cn=Mr"
Filter's tail      = ""
ldclt[24242]: Starting at Wed Aug  6 15:18:09 2014

ldclt[24242]: T000: Hit top incrementeal value
ldclt[24242]: T000: thread is dead.
ldclt[24242]: Average rate:  500.00/thr  (  50.00/sec), total:    500
ldclt[24242]: Average rate:    0.00/thr  (   0.00/sec), total:      0
ldclt[24242]: All threads are dead - exit.
ldclt[24242]: Global average rate:  500.00/thr  ( 25.00/sec), total:    500
ldclt[24242]: Global number times "no activity" reports: never
ldclt[24242]: Global number of dead threads: 1
ldclt[24242]: Global no error occurs during this session.
ldclt[24242]: Ending at Wed Aug  6 15:18:29 2014
ldclt[24242]: Exit status 0 - No problem during execution.


4. Delete those 500 entries
$ ldclt -h localhost -p 1389 -D "cn=Directory Manager" -w Secret123 -f cn=MrXXXXX -b "ou=people,dc=example,dc=com" -e delete,person,incr,noloop,commoncounter -r0 -R499 -n 1 -v
ldclt version 4.23
/usr/bin/ldclt-bin -h localhost -p 1389 -D "cn=Directory Manager" -w Secret123 -f cn=MrXXXXX -b ou=people,dc=example,dc=com -e delete,person,incr,noloop,commoncounter -r0 -R499 -n 1 -v
Process ID         = 24250
Host to connect    = localhost
Port number        = 1389
Bind DN            = cn=Directory Manager
Passwd             = Secret123
Referral           = on
Base DN            = ou=people,dc=example,dc=com
Filter             = "cn=MrXXXXX"
Max times inactive = 3
Max allowed errors = 1000
Number of samples  = -1
Number of threads  = 1
Total op. req.     = -1
Running mode       = 0x0b040201
Running mode       = verbose incremental commoncounter noloop delete class=person
LDAP oper. timeout = 30 sec
Sampling interval  = 10 sec
Values range       = [0 , 499]
Filter's head      = "cn=Mr"
Filter's tail      = ""
ldclt[24250]: Starting at Wed Aug  6 15:18:47 2014

ldclt[24250]: T000: Hit top incrementeal value
ldclt[24250]: T000: thread is dead.
ldclt[24250]: Average rate:  500.00/thr  (  50.00/sec), total:    500
ldclt[24250]: Average rate:    0.00/thr  (   0.00/sec), total:      0
ldclt[24250]: All threads are dead - exit.
ldclt[24250]: Global average rate:  500.00/thr  ( 25.00/sec), total:    500
ldclt[24250]: Global number times "no activity" reports: never
ldclt[24250]: Global number of dead threads: 1
ldclt[24250]: Global no error occurs during this session.
ldclt[24250]: Ending at Wed Aug  6 15:19:07 2014
ldclt[24250]: Exit status 0 - No problem during execution.

No errors were returned, hence marking as VERIFIED.
Comment 5 errata-xmlrpc 2014-10-14 07:54:53 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.

http://rhn.redhat.com/errata/RHBA-2014-1385.html
Note You need to log in before you can comment on or make changes to this bug.