Bug#977462: Debian Edu sssd.conf conflicts with sssd service sockets

[Mike Gabriel]

Hi Wolfgang,

On  Di 15 Dez 2020 23:13:07 CET, Wolfgang Schweer wrote:

A more complete output:

● sssd.service - System Security Services Daemon

     Active: active (running) since Tue 2020-12-15 23:09:26 CET; 15s ago
   Main PID: 443 (sssd)
      Tasks: 5 (limit: 1125)
     Memory: 45.1M
     CGroup: /system.slice/sssd.service
             ├─443 /usr/sbin/sssd -i --logger=files

             ├─537 /usr/libexec/sssd/sssd_nss --uid 0 --gid 0 --logger=files
             ├─538 /usr/libexec/sssd/sssd_pam --uid 0 --gid 0 --logger=files



Dez 15 23:09:25 am-080027a69b7b.intern sssd[443]: Starting up
Dez 15 23:09:25 am-080027a69b7b.intern be[intern][512]: Starting up
Dez 15 23:09:25 am-080027a69b7b.intern be[intern][512]: Your
configuration uses the autofs provider with schema set to rfc2307 and
default attribute mappings. The default map has changed in this release,
please make sure the configuration matches the server attributes.
Dez 15 23:09:25 am-080027a69b7b.intern autofs[539]: Starting up
Dez 15 23:09:25 am-080027a69b7b.intern nss[537]: Starting up
Dez 15 23:09:25 am-080027a69b7b.intern pam[538]: Starting up



Wolfgang

Loaded: loaded (/lib/systemd/system/sssd.service; enabled; vendor preset: enabled) ├─512 /usr/libexec/sssd/sssd_be --domain intern --uid 0 --gid 0 --logger=files └─539 /usr/libexec/sssd/sssd_autofs --uid 0 --gid 0 --logger=files Dez 15 23:09:24 am-080027a69b7b.intern systemd[1]: Starting System Security Services Daemon... Dez 15 23:09:26 am-080027a69b7b.intern systemd[1]: Started System Security Services Daemon. Dez 15 23:09:26 am-080027a69b7b.intern nss[537]: Enumeration requested but not enabled

Mike
--

DAS-NETZWERKTEAM
c\o Technik- und Ökologiezentrum Eckernförde
Mike Gabriel, Marienthaler Str. 17, 24340 Eckernförde
mobile: +49 (1520) 1976 148
landline: +49 (4351) 850 8940

GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22  0782 9AF4 6B30 2577 1B31
mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de

sssd.service is starting up fine, here, too. You have to scan for errors that occur during the startups of the pam, nss and autofs socket listeners. You should see those bugs, when hitting ESC during the boot splash. If you don't have them, it would be interesting to analyze the difference between a fresh install and my systems (fresh installs in August 2020, upgraded today). Btw., I run the test machines off-site (that is: without TJENER being around). (But that should not trigger the socket listeners' startup errors, they should also occur on-site).

pgpSKpfxEM9yZ.pgp
Description: Digitale PGP-Signatur