Bug 824244
| Summary: | sssd does not warn into sssd.log for broken configurations | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Kaushik Banerjee <kbanerje> |
| Component: | sssd | Assignee: | Jakub Hrozek <jhrozek> |
| Status: | CLOSED ERRATA | QA Contact: | Kaushik Banerjee <kbanerje> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | medium | ||
| Version: | 6.3 | CC: | grajaiya, jgalipea, prc |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | sssd-1.9.2-27.el6 | Doc Type: | Bug Fix |
| Doc Text: |
No documentation needed.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2013-02-21 09:23:51 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 881827 | ||
|
Description
Kaushik Banerjee
2012-05-23 04:39:06 UTC
Upstream ticket: https://fedorahosted.org/sssd/ticket/1345 Re-opening. The issue is not fixed in version 1.9.2-7 Kaushik, can you re-test? I think we fixed this issue again while fixing the startup bugs. At least it works for me, when I break the domains configuration with bogus min_id/max_id and attempt to start the sssd, I see a DEBUG message in the logs: (Wed Nov 14 21:41:52:786778 2012) [sssd] [main] (0x0020): Error loading configuration database: [2]: No such file or directory Not exactly verbose, but at least gives a hint that something is up with configuration.. Tested with sssd-1.9.2-13. With debug level set to 0xFFF0 in the [sssd] section, I do see only the "Error loading configu... ". But, shouldn't we get the same errors/output in sssd.log as what we get by running "sssd -i -d 0xFFF0"? We used to get the similar output in sssd.log before it broke in 1.8 Re-opening bug to get this fixed. Verified in version 1.9.2-37.el6. All mis-configurations are now logged to sssd.log. Report from beaker automation run. [ PASS ] SSSD_mis-configuration_001 max_id less than min_id [ PASS ] SSSD_mis-configuration_002 Invalid provider value [ PASS ] SSSD_mis-configuration_003 Negative min_id [ PASS ] SSSD_mis-configuration_004 Negative max_id [ PASS ] SSSD_mis-configuration_005 duplicate defined parameters, last read wins [ PASS ] SSSD_mis-configuration_006 Segmentation Fault [ PASS ] SSSD_mis-configuration_007 Required Key provider Not Defined [ PASS ] SSSD_mis-configuration_008 Enumeration defined with Integer [ PASS ] SSSD_mis-configuration_009 Enumeration defined with non boolean [ PASS ] SSSD_mis-configuration_010 Use Fully Qualified Names defined with a string [ PASS ] SSSD_mis-configuration_011 Use Fully Qualified Names defined with an integer [ PASS ] SSSD_mis-configuration_012 Invalid Authentication provider with LOCAL Identity provider [ PASS ] SSSD_mis-configuration_013 Invalid sssd.conf file permissions - 0644 [ PASS ] SSSD_mis-configuration_014 Invalid sssd.conf file permissions - 0200 [ PASS ] SSSD_mis-configuration_015 Invalid sssd.conf file permissions - 0066 [ PASS ] SSSD_mis-configuration_016 Invalid sssd.conf file ownership [ PASS ] SSSD_mis-configuration_017 Invalid dp Service [ PASS ] SSSD_mis-configuration_018 Duplicate defined parameters for offline authentication- last one read win Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHSA-2013-0508.html |