Your message dated Fri, 19 Jul 2019 15:51:20 +0000 with message-id <e1hovag-0006iy...@fasolo.debian.org> and subject line Bug#932080: fixed in sssd 2.2.0-4 has caused the Debian Bug report #932080, regarding sssd fails to start: #886483 raises from the dead to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 932080: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932080 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: sssd Version: 2.2.0-3 Severity: grave Justification: renders package unusable After upgrading to 2.2.0-3, sssd will not start (automatically). There are two failure modes, both likely related to #886483 I reported over a year ago. First failure mode happens if any services are listed in sssd.conf like (any service here will cause failure) service = pam, nss Startig sssd with systemctl will now (correctly) start the listed services, BUT it will also insist on trying to start the corresponding socket listener, which times out trying to get the socket, eventually causing systemd to kill the whole stack of processes, leaving no sssd processes running. It is, however, possible to start sssd manually from command line: "sssd -i" works as expected. Second failure mode is triggered by trying the obvious: commenting out the whole "service" line from sssd.conf. However, now sssd fails both from command line and from systemd because "sssd: SSSD couldn't load the configuration database [22]: Invalid argument." There does not seem to be any way of disabling all non-socket services but if at least one non-socket service is active, systemd will time out trying to load the corresponding socket. I even removed every .socket file related to sssd from my systemd but it didn't help (yes, I did a daemon-reexec and daemon-reload). Only fix I managed to find is a downgrade to 1.16.3-3.1. Cheers, Juha -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---Source: sssd Source-Version: 2.2.0-4 We believe that the bug you reported is fixed in the latest version of sssd, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 932...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Timo Aaltonen <tjaal...@debian.org> (supplier of updated sssd package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Format: 1.8 Date: Fri, 19 Jul 2019 18:15:41 +0300 Source: sssd Architecture: source Version: 2.2.0-4 Distribution: unstable Urgency: medium Maintainer: Debian SSSD Team <pkg-sssd-de...@alioth-lists.debian.net> Changed-By: Timo Aaltonen <tjaal...@debian.org> Closes: 932080 Changes: sssd (2.2.0-4) unstable; urgency=medium . [ Sam Morris ] * fix-have-systemd.patch: correct detection of systemd.pc (Closes: #932080) * default-to-socket-activated-services.diff: rely on socket activation to spawn nss and pam responders Checksums-Sha1: 2a2925398e1dbc49270ef2789d17b765229bec46 5154 sssd_2.2.0-4.dsc ceda844f5d0d1d43e6cdb1195eb2179322169299 107452 sssd_2.2.0-4.diff.gz 2b57a9d8c47eceb901a46ba4070897cd48834a32 10062 sssd_2.2.0-4_source.buildinfo Checksums-Sha256: 3e9b54c26d144485636d22a849a8e5f9f30c3fc44adb8e1d01c296356c0669dc 5154 sssd_2.2.0-4.dsc 366c97605a1c768ed91379f72d4ebf2f3e94947c3dd4d3df2ead663eda334de7 107452 sssd_2.2.0-4.diff.gz dc5eec465b0e0444a37b073088afaa5b57716f08bcedb44c8da2763e696382e6 10062 sssd_2.2.0-4_source.buildinfo Files: 70572d70f6864ce91740a98c50059599 5154 utils optional sssd_2.2.0-4.dsc 8264e436058cfad06bb8ebdcc42d9ea6 107452 utils optional sssd_2.2.0-4.diff.gz 5f69c2dce74229bf3ff62ce04c1d3106 10062 utils optional sssd_2.2.0-4_source.buildinfo -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEdS3ifE3rFwGbS2Yjy3AxZaiJhNwFAl0x384ACgkQy3AxZaiJ hNwMyg//Q3iNAanGzCH8oFNzIfPNol04IHt6bOMo5ZgsH342l7Sa+7Tj5FtR9TpP 1DUnobmYXONFW4tg7GlLA1JnDNuNcfRWBL64qioHVn5fANfbtOhbqg+2dwYqlGft MIHX/zSv3Z1woslye+OnJzxTK1tvtnKYzPRvmUbu+GS9q3HnEnGCY1H/y4DrNl7W WIDCoi6yZ6zyAHub7aM3FLH2VKl+E8CiiIM7n+LHWjn1ZetIO2CQN1pKBXWTzv55 IEsH6xj0bZqgRQV5O1WWp7lyObLlvBn02HJvbftapEfWjMTYEKKvsIV2aQ0ZwlzR aO4RAsw6HZLg4ooDKYxatv4bCaQS40rom3+XfO1sRvbcU7k8GFUExGKii0p3ja3n ibwopJrWERMQxAAYME/+TfEyGmqPXLfE9hFGir5lq8WKUEJuNkOWeEPtvQlXuhVX V3NYgYPYuvfiuF3eeFbCXRQoLTXzVueGugiQsyfAYPImtx88nVUH0na0kKiVUfSV M0+jOXMN2LgSEKwMO/nYU7oAZ9Yf+tcgXXiUuiAKwLBebZKiZs4apgo4FdeLA0gW qV2idW8JGdlIK4sojIUjBx5jcGaNgVC7KhV4F3L0B+3Tdazi7aFkKdHOinKkubCF qYdyXsbff4ghaqL00BAdYFUJ8hjdX72SvUSvX5Xn4Bm6MEkM7mU= =LX1R -----END PGP SIGNATURE-----
--- End Message ---
