Jeff, if you&#39;re seeing sssd_dp segfaults, can you get us a core dump? We&#39;re planning to remove the sssd_dp in the 0.7.0 release in a few weeks, but we&#39;re also going to be doing a 0.6.1 maintenance release (that we planned to release on Monday)<br>
If you can get us a core dump (or at least a backtrace), I&#39;ll see what I can do about fixing it for the 0.6.1 release.<br><br><div class="gmail_quote">On Fri, Oct 9, 2009 at 6:50 PM, Jeff Schroeder <span dir="ltr">&lt;<a href="mailto:jeffschroed@gmail.com">jeffschroed@gmail.com</a>&gt;</span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">I&#39;ve seen an occasional and (as of yet) impossible to reproduce dp<br>
segfault with sssd 0.6-1. Would it be worth trying to track down? It<br>
looked like there were patches merged to remove the dp process<br>
entirely. When sssd_dp segfaults, the watchdog doesn&#39;t restart it and<br>
bad things happen. That leads to nasty messages in syslog like:<br>
<br>
Oct  9 18:20:01.122 nameobscured crond[6931]: pam_sss(crond:account):<br>
Request to sssd failed.<br>
<br>
Restarting sssd fixes the problem but this is a bit disconcerting. Is<br>
master in shape to snapshot and build rpms from or should I wait for<br>
the 0.7 release without sssd_dp? This is the second time we&#39;ve seen<br>
this since 0.6 was released but it is still a legit problem.<br>
<br>
--<br>
Jeff Schroeder<br>
<br>
Don&#39;t drink and derive, alcohol and analysis don&#39;t mix.<br>
<a href="http://www.digitalprognosis.com" target="_blank">http://www.digitalprognosis.com</a><br>
_______________________________________________<br>
sssd-devel mailing list<br>
<a href="mailto:sssd-devel@lists.fedorahosted.org">sssd-devel@lists.fedorahosted.org</a><br>
<a href="https://fedorahosted.org/mailman/listinfo/sssd-devel" target="_blank">https://fedorahosted.org/mailman/listinfo/sssd-devel</a><br>
</blockquote></div><br>