With the line not commented, upon each and every startup in all cases
one sees this:
May 19 11:37:25 email1 systemd[1]: Starting SSSD NSS Service responder socket.
May 19 11:37:25 email1 sssd_check_socket_activated_responders[72216]: (Tue May
19 11:37:12:251510 2020) [sssd] [main] (0x0010): Misconfiguration found for the
nss responder.
May 19 11:37:25 email1 sssd_check_socket_activated_responders[72216]: The nss
responder has been configured to be socket-activated but it's still mentioned
in the services' line in /etc/sssd/sssd.conf.
May 19 11:37:25 email1 sssd_check_socket_activated_responders[72216]: Please,
consider either adjusting your services' line in /etc/sssd/sssd.conf or
disabling the nss's socket by calling:
May 19 11:37:25 email1 sssd[pac]: Starting up
May 19 11:37:25 email1 systemd[1]: Starting SSSD PAM Service responder private
socket.
May 19 11:37:25 email1 sssd_check_socket_activated_responders[72216]:
"systemctl disable sssd-nss.socket"
May 19 11:37:25 email1 sssd_check_socket_activated_responders[72218]: (Tue May
19 11:37:12:022884 2020) [sssd] [main] (0x0010): Misconfiguration found for the
pam responder.
May 19 11:37:25 email1 sssd_check_socket_activated_responders[72218]: The pam
responder has been configured to be socket-activated but it's still mentioned
in the services' line in /etc/sssd/sssd.conf.
May 19 11:37:25 email1 sssd_check_socket_activated_responders[72218]: Please,
consider either adjusting your services' line in /etc/sssd/sssd.conf or
disabling the pam's socket by calling:
May 19 11:37:25 email1 sssd[ssh]: Starting up
May 19 11:37:25 email1 systemd[1]: sssd-pam-priv.socket: Control process
exited, code=exited, status=17/n/a
May 19 11:37:25 email1 sssd_check_socket_activated_responders[72218]:
"systemctl disable sssd-pam.socket"
May 19 11:37:25 email1 sssd[pam]: Starting up
May 19 11:37:25 email1 systemd[1]: sssd-pam-priv.socket: Failed with result
'exit-code'.
May 19 11:37:25 email1 sssd[sudo]: Starting up
May 19 11:37:25 email1 systemd[1]: Failed to listen on SSSD PAM Service
responder private socket.
May 19 11:37:25 email1 sssd_check_socket_activated_responders[72224]: (Tue May
19 11:37:13:424695 2020) [sssd] [main] (0x0010): Misconfiguration found for the
sudo responder.
May 19 11:37:25 email1 sssd_check_socket_activated_responders[72224]: The sudo
responder has been configured to be socket-activated but it's still mentioned
in the services' line in /etc/sssd/sssd.conf.
May 19 11:37:25 email1 sssd_check_socket_activated_responders[72224]: Please,
consider either adjusting your services' line in /etc/sssd/sssd.conf or
disabling the sudo's socket by calling:
May 19 11:37:25 email1 systemd[1]: Dependency failed for SSSD PAM Service
responder socket.
May 19 11:37:25 email1 sssd_check_socket_activated_responders[72224]:
"systemctl disable sssd-sudo.socket"
May 19 11:37:25 email1 systemd[1]: sssd-pam.socket: Job sssd-pam.socket/start
failed with result 'dependency'.
May 19 11:37:25 email1 sssd_check_socket_activated_responders[72221]: (Tue May
19 11:37:13:671260 2020) [sssd] [main] (0x0010): Misconfiguration found for the
ssh responder.
May 19 11:37:25 email1 sssd_check_socket_activated_responders[72221]: The ssh
responder has been configured to be socket-activated but it's still mentioned
in the services' line in /etc/sssd/sssd.conf.
May 19 11:37:25 email1 sssd_check_socket_activated_responders[72221]: Please,
consider either adjusting your services' line in /etc/sssd/sssd.conf or
disabling the ssh's socket by calling:
May 19 11:37:25 email1 systemd[1]: sssd-nss.socket: Control process exited,
code=exited, status=17/n/a
May 19 11:37:25 email1 sssd_check_socket_activated_responders[72221]:
"systemctl disable sssd-ssh.socket"
May 19 11:37:25 email1 systemd[1]: sssd-nss.socket: Failed with result
'exit-code'.
May 19 11:37:25 email1 sssd[nss]: Starting up
With the line commented, one sees:
May 19 11:41:05 email1 systemd[1]: Starting System Security Services Daemon...
May 19 11:41:07 email1 sssd: Starting up
May 19 11:41:07 email1 kernel: [270731.176590] kauditd_printk_skb: 23 callbacks
suppressed
May 19 11:41:07 email1 kernel: [270731.176594] audit: type=1400
audit(1589906467.911:65972): apparmor="ALLOWED" operation="exec"
profile="/usr/sbin/sssd" name="/usr/libexec/sssd/sssd_be" pid=72354 comm="sssd"
requested_mask="x" denied_mask="x" fsuid=0 ouid=0
target="/usr/sbin/sssd//null-/usr/libexec/sssd/sssd_be"
May 19 11:41:07 email1 kernel: [270731.178959] audit: type=1400
audit(1589906467.911:65973): apparmor="ALLOWED" operation="file_mmap"
profile="/usr/sbin/sssd//null-/usr/libexec/sssd/sssd_be"
name="/usr/libexec/sssd/sssd_be" pid=72354 comm="sssd_be" requested_mask="r"
denied_mask="r" fsuid=0 ouid=0
May 19 11:41:07 email1 kernel: [270731.179565] audit: type=1400
audit(1589906467.911:65974): apparmor="ALLOWED" operation="file_mmap"
profile="/usr/sbin/sssd//null-/usr/libexec/sssd/sssd_be"
name="/usr/lib/x86_64-linux-gnu/ld-2.31.
