On Wed, Apr 24, 2013 at 2:53 AM, Jakub Hrozek <jhro...@redhat.com> wrote: > On Tue, Apr 23, 2013 at 03:20:45PM -0400, Stephen Gallagher wrote: >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> On 04/23/2013 01:44 PM, Brandon Foster wrote: >> > hey thanks for the quick reply. >> > >> > that is the end of the log after the user search has finish. the >> > next line after that is: >> > >> > >> > ------------------- (Tue Apr 23 12:52:29 2013) [sssd[be[default]]] >> > [server_setup] (0x0400): CONFDB: /var/lib/sss/db/config.ldb (Tue >> > Apr 23 12:52:29 2013) [sssd[be[default]]] [recreate_ares_channel] >> > (0x0100): Initializing new c-ares channel (Tue Apr 23 12:52:29 >> > 2013) [sssd[be[default]]] [resolv_get_family_order] (0x1000): >> > Lookup order: ipv4_first (Tue Apr 23 12:52:29 2013) >> > [sssd[be[default]]] [fo_context_init] (0x0400): Created new fail >> > over context, retry timeout is 30 (Tue Apr 23 12:52:29 2013) >> > [sssd[be[default]]] [confdb_get_domain_internal] (0x1000): >> > pwd_expiration_warning is -1 (Tue Apr 23 12:52:29 2013) >> > [sssd[be[default]]] [sysdb_domain_init_internal] (0x0200): DB File >> > for default: /var/lib/sss/db/cache_default.ldb (Tue Apr 23 12:52:29 >> > 2013) [sssd[be[default]]] [ldb] (0x4000): Added timed event >> > "ltdb_callback": 0x10e98c0 >> > >> > (Tue Apr 23 12:52:29 2013) [sssd[be[default]]] [ldb] (0x4000): >> > Added timed event "ltdb_timeout": 0x10ff4d0 .... --------------- >> > which is the same as the very beginning of the log. >> > >> > the start of the user search is in there near the end, but that is >> > where the log ends when taken after the id search has failed. >> >> >> >> Well, that tells us something. It tells us that apparently you >> experienced a crash and the SSSD was forced to restart the provider >> daemon. >> > > Yes, I agree. The crash occurs while retrieving the rootDSE and I > remember we had a number of issues with that in 6.3, especially if the > server on the other end was Novell eDirectory. > > There are currently no known SSSD crasher bugs related to rootDSE, so I > believe the issue would be fixed when you upgrade. > >> Would you mind trying out the SSSD from CentOS 6.4 to see if this >> particular crash has already been fixed there? If not, please try to >> get a backtrace (of the 6.4 version of SSSD) with GDB. You will need >> to take the following steps: >> >> yum install gdb >> debuginfo-install sssd >> gdb -p $(pidof sssd_be) >> >> At the gdb prompt, type "continue". >> >> When it eventually crashes and returns you to the prompt, type 'bt >> full' and copy all of the backtrace data into a text file (and attach >> it to an email). > _______________________________________________ > sssd-users mailing list > sssd-users@lists.fedorahosted.org > https://lists.fedorahosted.org/mailman/listinfo/sssd-users
sorry for the delay got pulled away for a bit. I can confirm that I have updated to 6.4 and all of my packages are up to date. i'll do the debuginfo shortly _______________________________________________ sssd-users mailing list sssd-users@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/sssd-users
