#3827 SSSD should log to syslog if a domain is not started due to a misconfiguration
Closed: Fixed 2 years ago Opened 2 years ago by jhrozek.

Ticket was cloned from Red Hat Bugzilla: Bug 1626001

Please note that this Bug is private and may not be accessible as it contains confidential Red Hat customer information.

With recent releases, we also auto-start the files domain. This makes it somewhat harder to spot issues in any explicit domain configuration, because previously, if a system used only a single domain, this single domain wouldn't start and then, because there were no domains started at all, the service would have aborted startup. The additional implicit files domain hides the explicit domain error in the sense that now sssd at least starts.

Therefore it would be nice to at least call sss_log in case a domain is misconfigured so much that it can't be started. We can also take this opportunity to review all the fatal misconfigurations - perhaps some of them could be relaxed.


Metadata Update from @jhrozek:
- Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1626001

2 years ago

Metadata Update from @jhrozek:
- Issue tagged with: easyfix

2 years ago

I think it would be enough to add the sss_log call to where confdb_get_domain_internal is called.

I think it would be enough to add the sss_log call to where confdb_get_domain_internal is called.

I think it would be enough to add the sss_log call to where confdb_get_domain_internal is called.

Metadata Update from @jhrozek:
- Issue set to the milestone: SSSD 2.1

2 years ago

Metadata Update from @thalman:
- Issue assigned to thalman

2 years ago

Metadata Update from @jhrozek:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

2 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/4821

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.

Login to comment on this ticket.

Metadata