[SSSD] sssd pam backend crashing once in a while.

Jakub Hrozek jhrozek at redhat.com
Tue May 21 10:24:34 UTC 2013


On Tue, May 21, 2013 at 09:58:06AM +0000, Steve Traylen wrote:
> 
> Hi,
> 
>   We are experienced trouble in our interactive login service where sssd in crashing every few hours in most of the nodes.
>  We run on Scientific Linux CERN SLC release 6.4 (Carbon) (which is RH 6.4 based), more precisely:
> 

Hi,
I'm sorry for the trouble.

>  sssd-1.9.2-82.7.el6_4.x86_64
>   sssd-client-1.9.2-82.7.el6_4.x86_64
> 

That's pretty much the latest stable release.

>   We have some logs
> 
>   (Mon May 20 14:31:27 2013) [sssd[pam]] [sss_dp_init] (0x0010): Failed to connect to monitor services.
>   (Mon May 20 14:31:27 2013) [sssd[pam]] [sss_process_init] (0x0010): fatal error setting up backend connector
> 
>   which is the restart of the backed failing?
>   
>   

It's actually the PAM process not succeeding in reconnecting to the UNIX
pipe connecting it with the monitor process that watches over all the
SSSD worker processes.

> 
> Here is our sssd.conf
> 
[snip]

The config file looks good to me.

> 
> and a backtrace below.  I can provide a core file.
> 

Providing the core file would be great if you don't mind. However, keep
in mind that the core file might contain confidential information, in
some cases even the passwords.

>   Cheers; Steve
> 
> # ls -ltd  /core.18894
> -rw-------. 1 root root 1253376 May 14 20:10 /core.18894
> # file /core.18894
> /core.18894: ELF 64-bit LSB core file x86-64, version 1 (SYSV), SVR4-style, from '/usr/libexec/sssd/sssd_pam --debug-to-files'
> #
> 
> .....does this ring a bell?

No, sorry. This looks like some kind of a new bug to me. Can you install
sssd-debuginfo (debuginfo-install sssd should be all you need) and
generate the backtrace again?

When does the crash happen, can you see any pattern in SSSD usage? I'd
like to reproduce the crash in-house if possible.

> 
> # gdb /usr/libexec/sssd/sssd_pam /core.18894
> GNU gdb (GDB) Red Hat Enterprise Linux (7.2-60.el6)
> Copyright (C) 2010 Free Software Foundation, Inc.
> ....
> (gdb) where
> #0  0x00007f297c2778a5 in raise () from /lib64/libc.so.6
> #1  0x00007f297c279085 in abort () from /lib64/libc.so.6
> #2  0x00007f297f41cc3c in ?? () from /usr/lib64/libtalloc.so.2
> #3  0x00007f297f41cdf1 in talloc_get_name () from /usr/lib64/libtalloc.so.2
> #4  0x00007f297f41ce1e in talloc_check_name () from /usr/lib64/libtalloc.so.2
> #5  0x0000000000410e0a in ?? ()
> #6  0x00007f297edb161a in ?? () from /lib64/libdbus-1.so.3
> #7  0x00007f297edb386f in dbus_connection_dispatch () from /lib64/libdbus-1.so.3
> #8  0x000000000045425e in ?? ()
> #9  0x00007f297f62bbd9 in tevent_common_loop_timer_delay () from /usr/lib64/libtevent.so.0
> #10 0x00007f297f62b2ab in ?? () from /usr/lib64/libtevent.so.0
> #11 0x00007f297f6278f0 in _tevent_loop_once () from /usr/lib64/libtevent.so.0
> #12 0x00007f297f62795b in tevent_common_loop_wait () from /usr/lib64/libtevent.so.0
> #13 0x0000000000455bb3 in ?? ()
> #14 0x0000000000409b32 in ?? ()
> #15 0x00007f297c263cdd in __libc_start_main () from /lib64/libc.so.6
> #16 0x0000000000406859 in ?? ()
> #17 0x00007fffadb98f88 in ?? ()
> #18 0x000000000000001c in ?? ()
> #19 0x0000000000000002 in ?? ()
> #20 0x00007fffadb99f02 in ?? ()
> #21 0x00007fffadb99f1d in ?? ()
> #22 0x0000000000000000 in ?? ()
> (gdb)
> <core.18894>



More information about the sssd-devel mailing list