This bug is created as a clone of upstream ticket:
The code that resets the original entries/mods/etc. when retrying deadlocked transactions in ldbm_back_delete et. al. need to be cache aware when deleting entries that are cached - for example, ldbm_delete.c:485
The problem is that e is cached, so cannot be freed like this. Freeing cached entries seems to cause problems in the server, assertion failures, other crashes.
Please add steps to verify this bug
The attached test scripts and steps in this comment can be shared for verifying this bug.
After running the test, run search all.
ldapsearch -x ... -b "dc=example,dc=com" >> OUTPUT0
Restart the server and run search all, again.
ldapsearch -x ... -b "dc=example,dc=com" >> OUTPUT1
The 2 outputs OUTPUT0 and OUTPUT1 are supposed to be identical (to ensure the cache reflects the entries in DB).
Also covered by the new test multi_plugin - the stress test
r6706 | rmeggins@REDHAT.COM | 2012-07-07 08:24:23 -0600 (Sat, 07 Jul 2012) | 16 lines
Add multi_plugin test suite
This test enables and configures multiple plugins in the style
of ipa. The stress version of this test will enable the
TXN_TESTING in the server which will exercise the txn deadlock
and retry code paths in the server.
Tickets covered by this test:
Ticket #345 - db deadlock return should not log error
Ticket #387 - managed entry sometimes doesn't delete the managed entry
Ticket #360 - ldapmodify returns Operations error
Ticket #335 - transaction retries need to be cache aware
Bugs covered by this test:
830336 db deadlock return should not log error
830343 managed entry sometimes doesn't delete the managed entry
833218 ldapmodify returns Operations error
833202 transaction retries need to be cache aware
On RHEL 6.4 Snapshot 5 with 389-ds-base-220.127.116.11-11.el6.x86_64:
multi_plugin startup 100% (1/1)
multi_plugin run 100% (6/6)
multi_plugin cleanup 100% (1/1)
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.