Bug 1110369
| Summary: | sssd is started before messagebus, making sssd-ifp fail | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Jan Pazdziora (Red Hat) <jpazdziora> |
| Component: | sssd | Assignee: | Jakub Hrozek <jhrozek> |
| Status: | CLOSED ERRATA | QA Contact: | Kaushik Banerjee <kbanerje> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 6.6 | CC: | dpal, grajaiya, jgalipea, jhutar, jpazdziora, lslebodn, mkosek, pbrezina, preichl, stefw |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | sssd-1.11.6-3.el6 | Doc Type: | Bug Fix |
| Doc Text: |
No Documentation Needed
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2014-10-14 04:48:45 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: | |||
|
Description
Jan Pazdziora (Red Hat)
2014-06-17 13:53:15 UTC
The issue can likely be also observed by rebooting the machine. We're debating the right solution with the DBus developers. So far, one option that came up was making SSSD poll for the system bus: https://fedorahosted.org/sssd/ticket/2360 The problem with polling is, if you have fast machine, httpd could be started before the next poll and attempt to serve request and dbus call will fail. Polling is good to recover from some errors but for consistent boot sequence, it might be good to also have an explicit chkconfig entry after messagebus but before things like httpd to poke sssd to retry right away. HUP or USR1, maybe? Stef, do you know of any DBus service that is in the same area as SSSD, that is, both an identity provider and a DBus service? I wish we could simply put a watch on the DBus system bus socket and only start the IFP service then, but inotify can't watch for nonexistent files (obvisously). Upstream ticket: https://fedorahosted.org/sssd/ticket/2360 I talked to Marius a bit today on IRC and he had an interesting suggestion a bit along the lines of what Jan suggested in comment #5. The proposal was to let DBus (not an initscript entry) start a simple binary that would SIGHUP the sssd and let it know it's time to spawn the dbus service. I'll try to experiment with this and start a thread on sssd-devel. btw the reason I don't like simply starting messagebus before sssd is that sssd users might be included in places like the interface policy XML. Clearly dbus consumes identities at that point, so the identities should be resolvable. (In reply to Jakub Hrozek from comment #8) > I talked to Marius a bit today on IRC and he had an interesting suggestion a > bit along the lines of what Jan suggested in comment #5. > > The proposal was to let DBus (not an initscript entry) start a simple binary > that would SIGHUP the sssd and let it know it's time to spawn the dbus > service. I'll try to experiment with this and start a thread on sssd-devel. Yes, not a bad idea. Although you could use any other means of communication, such as the usual sssd unix sockets as well. Hi Jan, given that sssd-dbus is mostly used by Satellite in RHEL6, would the Sat QE be available to help with testing? Patches are available for review on the upstream sssd-devel list. Just for reference, here are the commits that fixed the bug:
* master:
1a59af8245f183f22d87d067a90197d8e2ea958d
1746e8b8399da2a7a8da4aace186f66055ccfec1
149f40dc2d4ead57811c70b5028648ac83f6a1a7
b76419cf8830440b46c20a15585562343c7b1924
0c1d65998907930678da2d091789446f2c344d5d
1f2507e1fd089f2bf3458cfb4faeaa9669d72f98
4df1a6a977df74420867d9b1daddcca0eea4b2e1
* sssd-1-11:
80af7e9daed52b283af037864bcdd86d96695618
42b0c3442815c0374735377c7f5ced4fe1a00e97
87d3c7d23885b0b6dca3d7cf0494c7b93225429c
fbc3f000ca0672bb18797201768bd13e5611eaad
3e57c78c8163f6ee395bdf34b1e2c550cd8467f1
727f4bf4829f2405c978a4c9b960bef3ad86b002
906177a2666bf360a3d85fec55fc942cf9b33163
Verified with version 1.11.6-29.el6 # chkconfig --list | grep -E 'messagebus|sssd' messagebus 0:off 1:off 2:on 3:on 4:on 5:on 6:off sssd 0:off 1:off 2:off 3:on 4:on 5:on 6:off service messagebus stop ; service sssd stop ; init 3 # ps axuw | grep ifp root 13135 0.0 0.3 199972 3368 ? S 05:29 0:00 /usr/libexec/sssd/sssd_ifp --debug-to-files 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/RHBA-2014-1375.html |