#4054 socket activated services incompatible with default implicit sssd.conf
Closed: cloned-to-github 5 years ago by pbrezina. Opened 5 years ago by ahasenack.

Thread: https://lists.fedorahosted.org/archives/list/sssd-users@lists.fedorahosted.org/thread/OQZ525APQFZLH75LGV6QV5X2PUH23PET/

I noticed that when there is no /etc/sssd/sssd.conf file, some sort of default is assumed so that the main sssd service starts. This doesn't work with the socket activated services, however. They log this error:

Aug 01 12:49:07 eoan-sssd2 sssd_check_socket_activated_responders[3012]: The nss responder has been configured to be socket-activated but it's still mentioned in the services' line in /etc/sssd/sssd.conf.

There is no /etc/sssd/sssd.conf file, however.


Seems like we have a related PR for some time: https://github.com/SSSD/sssd/pull/132
but I don't remember the contents of the PR, honestly, needs another look

Metadata Update from @pbrezina:
- Issue tagged with: Future milestone

5 years ago

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/5022

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

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)

5 years ago

Log in to comment on this ticket.

Metadata