[ Mike Gabriel, 2020-12-15 ] > 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).
ok, confirmed. > 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). yes, they do. I guess your proposed solution 2 could be the right one - at least that's my coclusion from the output (see below) Wolfgang ░░ Subject: A start job for unit sssd-nss.socket has begun execution ░░ A start job for unit sssd-nss.socket has begun execution. ░░ Subject: A start job for unit sssd-pam-priv.socket has begun execution ░░ A start job for unit sssd-pam-priv.socket has begun execution. Dez 15 23:41:09 am-080027a69b7b.intern sssd_check_socket_activated_responders[572]: (2020-12-15 23:41:09:157321): [sssd] [main] (0x0010): Misconfiguration found for the nss responder. Dez 15 23:41:09 am-080027a69b7b.intern sssd_check_socket_activated_responders[572]: The nss responder has been configured to be socket-activated but it's still mentioned in the services' line in /etc/sssd/sssd.conf. Dez 15 23:41:09 am-080027a69b7b.intern sssd_check_socket_activated_responders[572]: Please, consider either adjusting your services' line in /etc/sssd/sssd.conf or disabling the nss's socket by calling: Dez 15 23:41:09 am-080027a69b7b.intern sssd_check_socket_activated_responders[572]: "systemctl disable sssd-nss.socket" Dez 15 23:41:09 am-080027a69b7b.intern sssd_check_socket_activated_responders[573]: (2020-12-15 23:41:09:162260): [sssd] [main] (0x0010): Misconfiguration found for the pam responder. Dez 15 23:41:09 am-080027a69b7b.intern sssd_check_socket_activated_responders[573]: The pam responder has been configured to be socket-activated but it's still mentioned in the services' line in /etc/sssd/sssd.conf. Dez 15 23:41:09 am-080027a69b7b.intern sssd_check_socket_activated_responders[573]: Please, consider either adjusting your services' line in /etc/sssd/sssd.conf or disabling the pam's socket by calling: Dez 15 23:41:09 am-080027a69b7b.intern sssd_check_socket_activated_responders[573]: "systemctl disable sssd-pam.socket" Dez 15 23:41:09 am-080027a69b7b.intern systemd[1]: sssd-nss.socket: Control process exited, code=exited, status=17/n/a
signature.asc
Description: PGP signature
