#3812 sssd 2.0.0 segfaults on startup
Closed: Fixed a year ago Opened 2 years ago by tgurr.

While the previous version (1.16.1) I had worked and still works fine the new version 2.0.0 segfaults right on startup.

# journalctl -xe

-- 
-- Üblicherweise ist dies ein Hinweis auf einen Programmfehler und sollte
-- als Fehler dem jeweiligen Hersteller gemeldet werden.
Aug 23 15:20:56 localhost sssd[pam][31561]: Starting up
Aug 23 15:20:56 localhost sssd[nss][31560]: Starting up
Aug 23 15:20:56 localhost sssd[pam][31563]: Starting up
Aug 23 15:20:56 localhost sssd[nss][31562]: Starting up
Aug 23 15:20:57 localhost sssd[be[shadowutils]][31564]: Starting up
Aug 23 15:20:57 localhost audit[31564]: ANOM_ABEND auid=4294967295 uid=0 gid=0 ses=4294967295 pid=31564 comm="sssd_be" exe="/usr/x86_64-pc-linux-gnu/libexec/sssd/sssd_be" sig=11 res=1
Aug 23 15:20:57 localhost kernel: sssd_be[31564]: segfault at 58 ip 00007f1ca2f3bcf0 sp 00007fffd6fe6de8 error 4 in libsss_sbus.so[7f1ca2f35000+1b000]
Aug 23 15:20:57 localhost kernel: Code: 01 00 be a3 00 00 00 48 8d 3d 0c 69 01 00 31 c0 e8 45 a4 ff ff e9 72 fe ff ff 48 8b 7f 58 e9 37 99 ff ff 0f 1f 80 00 00 00 00 <48> 8b 7f 58 e9 17 a3 ff ff 0f 1f 80 00 00 00 00 48 85 ff 74 23 48 
Aug 23 15:20:57 localhost kernel: audit: type=1701 audit(1535030457.926:8): auid=4294967295 uid=0 gid=0 ses=4294967295 pid=31564 comm="sssd_be" exe="/usr/x86_64-pc-linux-gnu/libexec/sssd/sssd_be" sig=11 res=1
Aug 23 15:20:57 localhost systemd[1]: Attaching egress BPF program to cgroup /sys/fs/cgroup/unified/system.slice/system-systemd\x2dcoredump.slice/systemd-coredump@3-31565-0.service failed: Invalid argument
Aug 23 15:20:57 localhost systemd[1]: Started Process Core Dump (PID 31565/UID 0).
-- Subject: Unit systemd-coredump@3-31565-0.service has finished start-up
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit systemd-coredump@3-31565-0.service has finished starting up.
-- 
-- The start-up result is RESULT.
Aug 23 15:20:58 localhost sssd[31538]: Exiting the SSSD. Could not restart critical service [shadowutils].
Aug 23 15:20:58 localhost sssd[be[DOMAIN]][31540]: Shutting down
Aug 23 15:20:58 localhost systemd[1]: sssd.service: Main process exited, code=exited, status=1/FAILURE
Aug 23 15:20:58 localhost systemd[1]: sssd.service: Failed with result 'exit-code'.
Aug 23 15:20:58 localhost systemd[1]: Failed to start System Security Services Daemon.
-- Subject: Unit sssd.service has failed
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit sssd.service has failed.
-- 
-- The result is RESULT.
Aug 23 15:20:58 localhost systemd-coredump[31566]: Process 31564 (sssd_be) of user 0 dumped core.

                                                   Stack trace of thread 31564:
                                                   #0  0x00007f1ca2f3bcf0 sbus_connection_add_path_map (/usr/x86_64-pc-linux-gnu/lib/sssd/libsss_sbus.so)
                                                   #1  0x00007f1c9b52a815 proxy_client_init (libsss_proxy.so)
                                                   #2  0x00007f1c9b529d09 sssm_proxy_init (libsss_proxy.so)
                                                   #3  0x0000564cdc0e2db1 dp_load_module (sssd_be)
                                                   #4  0x0000564cdc0e3792 dp_init_targets (sssd_be)
                                                   #5  0x0000564cdc0e2734 n/a (sssd_be)
                                                   #6  0x00007f1ca2f3c4ef n/a (/usr/x86_64-pc-linux-gnu/lib/sssd/libsss_sbus.so)
                                                   #7  0x00007f1ca2f3f45c n/a (/usr/x86_64-pc-linux-gnu/lib/sssd/libsss_sbus.so)
                                                   #8  0x00007f1ca2f48a27 n/a (/usr/x86_64-pc-linux-gnu/lib/sssd/libsss_sbus.so)
                                                   #9  0x00007f1ca2f3de73 n/a (/usr/x86_64-pc-linux-gnu/lib/sssd/libsss_sbus.so)
                                                   #10 0x00007f1ca2ee780a n/a (/usr/x86_64-pc-linux-gnu/lib/libdbus-1.so.3.19.8)
                                                   #11 0x00007f1ca2eeb026 dbus_connection_dispatch (/usr/x86_64-pc-linux-gnu/lib/libdbus-1.so.3.19.8)
                                                   #12 0x00007f1ca2f3d646 n/a (/usr/x86_64-pc-linux-gnu/lib/sssd/libsss_sbus.so)
                                                   #13 0x00007f1c9fc29635 tevent_common_invoke_timer_handler (libtevent.so.0)
                                                   #14 0x00007f1c9fc297c6 tevent_common_loop_timer_delay (libtevent.so.0)
                                                   #15 0x00007f1c9fc2a767 n/a (libtevent.so.0)
                                                   #16 0x00007f1c9fc28cb7 n/a (libtevent.so.0)
                                                   #17 0x00007f1c9fc241dd _tevent_loop_once (libtevent.so.0)
                                                   #18 0x00007f1c9fc243eb tevent_common_loop_wait (libtevent.so.0)
                                                   #19 0x00007f1c9fc28c57 n/a (libtevent.so.0)
                                                   #20 0x00007f1ca3079f33 server_loop (/usr/x86_64-pc-linux-gnu/lib/sssd/libsss_util.so)
                                                   #21 0x0000564cdc0d90c4 main (sssd_be)
                                                   #22 0x00007f1c9f322493 __libc_start_main (libc.so.6)
                                                   #23 0x0000564cdc0d925e _start (sssd_be)
-- Subject: Speicherabbild für Prozess 31564 (@COREDUMP_COMM) generiert
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Documentation: man:core(5)
-- 
-- Prozess 31564 (sssd_be) ist abgebrochen worden und
-- ein Speicherabbild wurde generiert.
-- 
-- Üblicherweise ist dies ein Hinweis auf einen Programmfehler und sollte
-- als Fehler dem jeweiligen Hersteller gemeldet werden.

Additional notes, I've a rather basic/simple setup:

/etc/sssd/sssd.conf

[sssd]
services = nss, pam
domains = shadowutils,DOMAIN

[nss]
filter_users = postgres
filter_groups = domänen-benutzer

[pam]

[domain/shadowutils]
id_provider = files

auth_provider = proxy
proxy_pam_target = sssd-shadowutils

proxy_fast_alias = True

/etc/sssd/conf.d/domain-ldap.conf

[domain/DOMAIN]
id_provider = ldap
auth_provider = ldap
access_provider = ldap
chpass_provider = ldap

ldap_uri = ldap://addc.domain.de/
ldap_search_base = dc=domain,dc=de
ldap_default_bind_dn = xxx
ldap_default_authtok = xxx

ldap_user_object_class = user
ldap_group_object_class = group
ldap_user_name = sAMAccountName
ldap_tls_reqcert = demand
ldap_tls_cacert = /etc/ssl/domain/DOMAIN_Root_CA.pem

# defines user/group schema type
ldap_schema = ad

# for SID-UID mapping
ldap_id_mapping = true

# disable case sensitive user names
case_sensitive = false

# caching credentials
cache_credentials = true
enumerate = true

# access controls
ldap_access_order = expire
ldap_account_expire_policy = ad

override_homedir = /home/%d/%u
fallback_homedir = /home/%d/%u
default_shell = /bin/bash

cc @pbrezina maybe we broke the proxy provider with 2.0?

Metadata Update from @jhrozek:
- Issue priority set to: blocker (was: minor)
- Issue tagged with: PR, bug, regression

a year ago

Metadata Update from @jhrozek:
- Issue set to the milestone: SSSD 2.1

a year ago

Metadata Update from @jhrozek:
- Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1628126

a year ago

Metadata Update from @jhrozek:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

a year ago

@tgurr thank you very much for reporting the bug

Login to comment on this ticket.

Metadata