<div dir="ltr">Lukas,<div><br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><span style="font-size:13px;font-family:arial,sans-serif">Could you try to disable dynamic dns updates in domain section.<br>
</span><span style="font-size:13px;font-family:arial,sans-serif"> dyndns_update = false</span></blockquote><div><br></div><div>I can do that. Would you like valgrind logs? Another coredump? And just to review, the crash happens only when 'dyndns_update_ptr' is true; the crash doesn't seem to be affected by the 'dyndns_update' option.</div>
</div></div><div class="gmail_extra"><br clear="all"><div><div><br></div>-Chris</div>
<br><br><div class="gmail_quote">On Wed, Aug 13, 2014 at 1:08 PM, Lukas Slebodnik <span dir="ltr"><<a href="mailto:lslebodn@redhat.com" target="_blank">lslebodn@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="HOEnZb"><div class="h5">On (13/08/14 11:12), Chris Hartman wrote:<br>
>Greetings,<br>
><br>
>Could you send me more coredumps privately with fuly updated ubuntu 14.04?<br>
>> Because it really strange that sssd crashed in syscal fdatasync.<br>
><br>
>Lukas, not a problem. Stand by for an email with a 7zip archive of a core<br>
>dump and back trace. The debugging symbols for lib{tdb,ldb}1 were installed<br>
>for this.<br>
><br>
>I have another idea which could help us to to find a problem.<br>
>> We can try to run sssd_be with valgrind.<br>
>> 1) we need to find out arguments for process sssd_be<br>
>> sh-4.2$ pgrep -af sssd_be<br>
>> 1191 /usr/libexec/sssd/sssd_be --domain <a href="http://idm.example.com" target="_blank">idm.example.com</a> --debug-to-files<br>
>> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^<br>
>> this output will be used in sssd.conf<br>
>> 2) add new option to domain section in sssd.conf<br>
>> command = valgrind -v --show-reachable=yes --log-file=/var/log/sssd/valgrind_idm.example.com.log<br>
>> /usr/libexec/sssd/sssd_be --domain <a href="http://idm.example.com" target="_blank">idm.example.com</a> --debug-to-files<br>
>> # do not forget to replace output from previous step.<br>
>><br>
>> 3) It would be good to install debug symbols for libraries libtdb1 and<br>
>> libldb1<br>
>> 4) reproduce problem<br>
>> some interesting output can be in log file from valgrind.<br>
><br>
> I did this with interesting(?) results. The sssd_be process never actually<br>
>crashed but there is some erroneous output in the valgrind log. Removing<br>
>the special command option results in a crash as expected. I've sanitized<br>
>and attached the log to this email. Let me know if that reveals anything.<br>
><br>
</div></div>Thank you very much for log files from valgrind.<br>
There is use after free problem in dynamic dns updates code.<br>
<br>
Could you try to disable dynamic dns updates in domain section.<br>
dyndns_update = false<br>
<div class="HOEnZb"><div class="h5"><br>
LS<br>
_______________________________________________<br>
sssd-users mailing list<br>
<a href="mailto:sssd-users@lists.fedorahosted.org">sssd-users@lists.fedorahosted.org</a><br>
<a href="https://lists.fedorahosted.org/mailman/listinfo/sssd-users" target="_blank">https://lists.fedorahosted.org/mailman/listinfo/sssd-users</a><br>
</div></div></blockquote></div><br></div>