Source: sssd Version: 2.8.2-4 Severity: normal Tags: upstream Hi there,
thanks for your work with the sssd packages, really appreciated. Today I found this assert that is preventing the sssd.service from starting: Apr 19 14:02:17 debian sssd[586]: Starting up Apr 19 14:02:17 debian sssd[586]: dbus[586]: arguments to dbus_server_get_address() were incorrect, assertion "server != NULL" failed in file ../../../dbus/dbus-server.c line 840. Apr 19 14:02:17 debian sssd[586]: This is normally a bug in some application using the D-Bus library. Apr 19 14:02:17 debian sssd[586]: D-Bus not built with -rdynamic so unable to print a backtrace Apr 19 14:02:17 debian systemd[1]: sssd.service: Main process exited, code=killed, status=6/ABRT Apr 19 14:02:17 debian systemd[1]: sssd.service: Failed with result 'signal'. Apr 19 14:02:17 debian systemd[1]: Failed to start sssd.service - System Security Services Daemon. My configuration: $ sudo cat /etc/sssd/sssd.conf [sssd] domains = files config_file_version = 2 [domain/files] id_provider = files access_provider = permit Packages in my system: $ dpkg -l *sss* Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-=================-============-============-============================================================ ii libnss-sss:amd64 2.8.2-4 amd64 Nss library for the System Security Services Daemon ii libpam-sss:amd64 2.8.2-4 amd64 Pam module for the System Security Services Daemon ii libsss-certmap0 2.8.2-4 amd64 Certificate mapping library for SSSD ii libsss-idmap0 2.8.2-4 amd64 ID mapping library for SSSD ii libsss-nss-idmap0 2.8.2-4 amd64 SID based lookups library for SSSD un libsss-sudo <none> <none> (no description available) ii python3-sss 2.8.2-4 amd64 Python3 module for the System Security Services Daemon ii sssd 2.8.2-4 amd64 System Security Services Daemon -- metapackage ii sssd-ad 2.8.2-4 amd64 System Security Services Daemon -- Active Directory back end ii sssd-ad-common 2.8.2-4 amd64 System Security Services Daemon -- PAC responder ii sssd-common 2.8.2-4 amd64 System Security Services Daemon -- common files un sssd-dbus <none> <none> (no description available) ii sssd-ipa 2.8.2-4 amd64 System Security Services Daemon -- IPA back end ii sssd-krb5 2.8.2-4 amd64 System Security Services Daemon -- Kerberos back end ii sssd-krb5-common 2.8.2-4 amd64 System Security Services Daemon -- Kerberos helpers ii sssd-ldap 2.8.2-4 amd64 System Security Services Daemon -- LDAP back end ii sssd-proxy 2.8.2-4 amd64 System Security Services Daemon -- proxy back end ii sssd-tools 2.8.2-4 amd64 System Security Services Daemon -- tools I'm not sure who is to blame, if Dbus or sssd. In any case, in my opinion, some actionable error message should be produced, rather than a weird assert.
