Aram Akhavan via FreeIPA-users wrote: > Working on getting hosts joined with ansible. I set up a fresh debian 13 VM > and used the ansible role to run client install. No issues joining and I can > log in just fine. Everything seems to work. > > On reboot, though, I notice some systemd issues: > > sssd_check_socket_activated_responders[675]: Misconfiguration found for the > 'nss' responder. > > It has been configured to be socket-activated but it's still mentioned in > the services' line of the config file. > > Please consider either adjusting services' line or disabling the socket by > calling: > > "systemctl disable sssd-nss.socket" > > The same shows for the other services. And indeed, the sssd.conf file set up > by the client install has: > [sssd] > services = nss, pam, ssh, sudo > > Quick search shows that this is in ipaclient/install/client.py, though its > used by the ansible module too. > > I guess the solution is to update my own role to disable the socket > responders? >
That would be one way. It's hard to know without more details on what you Ansible script looks like and the versions of sssd and freeipa. Or it could be a bug in freeipa. If you run ipa-client-install directly are things setup properly? rob -- _______________________________________________ FreeIPA-users mailing list -- [email protected] To unsubscribe send an email to [email protected] Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedorahosted.org/archives/list/[email protected] Do not reply to spam, report it: https://forge.fedoraproject.org/infra/tickets/issues/new
