http://bugzilla.opensuse.org/show_bug.cgi?id=1023631 Bug ID: 1023631 Summary: sssd runtime crash with ldap backend Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.2 Hardware: Other OS: openSUSE 42.2 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening@forge.provo.novell.com Reporter: ralf.koelmel@kit.edu QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:51.0) Gecko/20100101 Firefox/51.0 Build Identifier: sssd ver. 1.13.4 shows runtime problem with configured ldap backend. I've seen crashes of the main sssd process during timeout procedure of a not reachable ldap server. The following log is present : Feb 03 16:27:20 sssd[1399]: Killing service [default], not responding to pings! Feb 03 16:27:20 sssd[be[11378]: Starting up Feb 03 16:29:00 sssd[1399]: Killing service [default], not responding to pings! Feb 03 16:29:00 systemd[1]: sssd.service: Main process exited, code=dumped, status Feb 03 16:29:00 sssd[be[1402]: Shutting down Feb 03 16:29:00 systemd[1]: sssd.service: Unit entered failed state. Feb 03 16:29:00 systemd[1]: sssd.service: Failed with result 'core-dump'. Feb 03 16:29:00 systemd-coredump[11390]: Process 1399 (sssd) of user 0 dumped core The backtrace of the core is : (gdb) bt #0 0x00007fbbbe5358d7 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:55 #1 0x00007fbbbe536caa in __GI_abort () at abort.c:78 #2 0x00007fbbbe8a846c in ?? () from /usr/lib64/libtalloc.so.2 #3 0x00007fbbbe8a876d in talloc_check_name () from /usr/lib64/libtalloc.so.2 #4 0x0000000000405c0a in ping_check (pending=0x1927770, data=<optimized out>) at src/monitor/monitor.c:2565 #5 0x00007fbbbf0dbf92 in ?? () from /lib64/libdbus-1.so.3 #6 0x00007fbbbf0df361 in dbus_connection_dispatch () from /lib64/libdbus-1.so.3 #7 0x00007fbbbf7898a2 in sbus_dispatch (ev=0x18f6fe0, te=<optimized out>, tv=..., data=<optimized out>) at src/sbus/sssd_dbus_connection.c:96 #8 0x00007fbbbeabdf6f in tevent_common_loop_timer_delay () from /usr/lib64/libtevent.so.0 #9 0x00007fbbbeabef7a in ?? () from /usr/lib64/libtevent.so.0 #10 0x00007fbbbeabd677 in ?? () from /usr/lib64/libtevent.so.0 #11 0x00007fbbbeab981d in _tevent_loop_once () from /usr/lib64/libtevent.so.0 #12 0x00007fbbbeab99bb in tevent_common_loop_wait () from /usr/lib64/libtevent.so.0 #13 0x00007fbbbeabd617 in ?? () from /usr/lib64/libtevent.so.0 #14 0x00007fbbbf793523 in server_loop (main_ctx=0x18f3340) at src/util/server.c:673 #15 0x00000000004054e5 in main (argc=<optimized out>, argv=<optimized out>) at src/monitor/monitor.c:3066 The configuration is a default ldap backend with the following settings : [sssd] config_file_version = 2 services = nss,pam domains = default [nss] [pam] [domain/default] ldap_uri = <hidden> ldap_chpass_uri = <hidden> ldap_search_base = <hidden> ldap_schema = rfc2307 id_provider = ldap ldap_id_use_start_tls = True enumerate = True cache_credentials = False ldap_tls_cacertdir = /etc/ssl/certs chpass_provider = ldap auth_provider = ldap reconnection_retries = 6 timeout = 20 force_timeout = 120 ldap_service_object_class = ldap_service_name = ldap_service_port = ldap_service_proto = ldap_service_search_base = Some leap 42.2 systems weren't affected during ldap outage and have shown normal timeout procedure until the ldap server was present again. Also leap 42.1 systems with a version 1.11.5.1 have had crashes, but no coredump was generated. I've seen problems (not reconnecting after ldap outage) with the timeout procedure also in opensuse 13.2 systems the last years. Here i've changed the official version 1.12 to 1.13.3 from network:ldap repo and changed the timeout parameters as you see in the given config. This version has stabilized the problem in such situations, when ldap server or network were down. Reproducible: Didn't try -- You are receiving this mail because: You are on the CC list for the bug.