1.2.10 on EL5 (db 4.3) will print errors like this during shutdown:
libdb: DB handle previously used in transaction, missing transaction handle
1.2.10 switched all of the databases to use DB_AUTO_COMMIT upon open. With 4.2 and 4.3, this means all operations which update the database (put, del) must either specify a valid transaction handle or specify DB_AUTO_COMMIT in the flags.
not working - back to the drawing board :P
0001-fix-transaction-errors-with-db-4.3-and-db-4.2.patch 0001-fix-transaction-errors-with-db-4.3-and-db-4.2.patch
To ssh://git.fedorahosted.org/git/389/ds.git ac6a81f..9c7e9d5 master -> master commit changeset:9c7e9d5/389-ds-base Author: Rich Megginson rmeggins@redhat.com Date: Wed Mar 28 16:11:20 2012 -0600
originally targeted for 1.2.11.rc1, but actually in the 1.2.11.a1 release
Added initial screened field value.
Why don't you want to backport this patch to 1.2.10.x (the most "stable" branch if i understand correctly)? I need to do it manually each time the "x" in 1.2.10.x changes :) I'm using EL5, so unfortunately i can't migrate easily to 1.2.11 & 1.3.0.
Replying to [comment:10 pj101]:
Done.
Metadata Update from @rmeggins: - Issue assigned to nhosoi - Issue set to the milestone: 1.2.11.a1
389-ds-base is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in 389-ds-base's github repository.
This issue has been cloned to Github and is available here: - https://github.com/389ds/389-ds-base/issues/331
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Metadata Update from @spichugi: - Issue close_status updated to: wontfix (was: Fixed)
Login to comment on this ticket.