Learn more about these different git repos.
Other Git URLs
sssd-pac.socket uses the usual mechanism for preventing it from starting while services = pac is present in sssd.conf:
sssd-pac.socket
services = pac
sssd.conf
ExecStartPre=/usr/libexec/sssd/sssd_check_socket_activated_responders -r pac
However, in the case that sssd is configured to use a backend using the IPA provider and services is not set, or is set but does not contain pac, then the add_implicit_services function will add the pac to the service list at run time. This is not detected by sssd_check_socket_activated_reponders and you end up with two instances of sssd_pac running, one spawned by sssd and the other by systemd.
sssd
services
pac
add_implicit_services
sssd_check_socket_activated_reponders
sssd_pac
systemd
Quick and dirty fix: modify sssd_check_socket_activated_responders to use the same logic as sssd, that is, fail if any domain section in sssd.conf has id_provider = ipa.
sssd_check_socket_activated_responders
domain
id_provider = ipa
Metadata Update from @pbrezina: - Issue tagged with: Future milestone
SSSD is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in SSSD's github repository.
This issue has been cloned to Github and is available here: - https://github.com/SSSD/sssd/issues/5013
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Metadata Update from @pbrezina: - Issue close_status updated to: cloned-to-github - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.