New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Double free while adding entries (1.2.11 only) #1618
Comments
Comment from tbordaz (@tbordaz) at 2015-09-23 20:10:08 attachment |
Comment from tbordaz (@tbordaz) at 2015-09-23 20:37:53 DS aborts with this stack
|
Comment from nhosoi (@nhosoi) at 2015-09-24 04:47:09 Ticket has been cloned to Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1265851 |
Comment from nhosoi (@nhosoi) at 2015-10-13 04:58:03 git patch file (1.2.11 only) |
Comment from tbordaz (@tbordaz) at 2015-10-13 13:53:13 Hello Noriko, Great finding and fix !! Did you manage to reproduce with valgrind ? |
Comment from nhosoi (@nhosoi) at 2015-10-13 21:07:56 Replying to [comment:6 tbordaz]:
Thanks, Thierry! Actually, I could not reproduce the bug with valgrind. The issue is IPA start's timeout (I guess). DS itself has no problem to run with valgrind. But using "ipaclt start", I could not make the following KDC start successfully. I guess there's some trick to let it wait, but I gave it up there and did more research in the DS itself. I came to this conclusion in the 1.2.11 code, was to apply the change to the master, then found the same fix was there!! :) |
Comment from nhosoi (@nhosoi) at 2017-02-11 22:51:58 Metadata Update from @nhosoi:
|
Cloned from Pagure issue: https://pagure.io/389-ds-base/issue/48287
This problem was found while investigating https://fedorahosted.org/freeipa/ticket/5235
It was reproduced on RHEL 6.7 (389-ds-base-1.2.11.15-60.el6.x86_64)
The test case to reproduce is:
- install IPA master
- install IPA replica
- (enable core dump: yum install abrt, sysctl -w fs.suid_dumpable=1, 'ulimit -c unlimited' in /etc/sysconfig/dirsrv)
- iterate the provided script 'steps.sh'
- the master replica will crash
The crash is not systematic. On my VMs it happens once in ~[20,100] 'steps.sh'
Sometime the test case ends in breaking IPA topology (ipa user-add fails, or total init fails) without crash. It requires to reinstall the topology.
Each time (crash or IPA topology break) the following messages are logged:
The text was updated successfully, but these errors were encountered: