Hi Jakub, Is it possible to generate a core file? That would help debugging quite a > lot.
Thanks for your response. I'd be happy to generate a core file for you but I'm afraid I'm going to need some guidance. My google-fu has gotten me a little familiar with what commands are involved, but I'm not exactly sure how I'd go about generating or retrieving a core dump, especially because the sssd_be process is the one that's crashing, not the main sssd process. Would you be able provide assistance? I think that the following option (in the domain section) should help you > work around the problem: > dyndns_update = False This actually didn't work for me, but this did: dyndns_update_ptr = False So, apparently, the bug is related the ptr update procedure? Thanks again! -Chris On Wed, Jul 9, 2014 at 5:18 PM, Jakub Hrozek <[email protected]> wrote: > > On 09 Jul 2014, at 17:09, Chris Hartman <[email protected]> wrote: > > > Hi guys, > > > > Ubuntu 14.04 x86_64 > > SSSD 1.11.5 > > Active Directory backend > > > > Hi Chris, > > thanks for reporting this issue. I think we have a bug in the dynamic DNS > update code. Here are the last couple of lines before SSSD crashed: > (Wed Jul 9 10:10:39 2014) [sssd[be[sanedomain]]] > [sdap_id_op_connect_step] (0x4000): reusing cached connection > (Wed Jul 9 10:10:39 2014) [sssd[be[sanedomain]]] [be_nsupdate_done] > (0x0200): nsupdate child status: 0 > (Wed Jul 9 10:10:39 2014) [sssd[be[sanedomain]]] > [nsupdate_msg_create_common] (0x0200): Creating update message for realm > [SANEDOMAIN.LOCAL]. > (Wed Jul 9 10:10:42 2014) [sssd[be[sanedomain]]] [server_setup] (0x0400): > CONFDB: /var/lib/sss/db/config.ldb > > “server_setup” is the first function that gets executed after SSSD > restarts, so the lines right before that indicate where SSSD was before the > crash. > > Is it possible to generate a core file? That would help debugging quite a > lot. I realise the core file can contain private information, so feel free > to send it to me directly. If that not acceptable either, generate a > backtrace with “bt full” in a gdb session, then you can send a sanitised > backtrace. > > I think that the following option (in the domain section) should help you > work around the problem: > dyndns_update = False > > Please let us know if disabling the DNS update helped and if you can > generate the core file. > > Thanks again for the problem report! > > > I've been experiencing this problem for a few weeks with no luck in > troubleshooting it. During boot, the sssd_be process will continually spawn > and crash due to a segfault. When it gets stuck in this loop, domain > account login is almost impossible (local accounts still work). > > > > I've attached sanitized logs and my sssd.conf file. Please have a look > and let me know what you think. Thanks! > > > > -Chris > > <logs.tar.gz>_______________________________________________ > > sssd-users mailing list > > [email protected] > > https://lists.fedorahosted.org/mailman/listinfo/sssd-users > >
_______________________________________________ sssd-users mailing list [email protected] https://lists.fedorahosted.org/mailman/listinfo/sssd-users
