Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionThorsten Scherf
2016-08-02 11:12:53 UTC
Description of problem:
sssctl requires ifp to be added manually to sssd.conf. Even if we add a note to the documentation, customers will file bugs about this.
Here are some proposals how to fix it:
a) enable ifp by default
b) make ifp socket-activated by systemd
c) print a warning on the console saying what needs to be done to make sssctl work
For the GA release I strongly recommend to implement at least c).
Version-Release number of selected component (if applicable):
sssd-tools-1.14.0-14.el7.x86_64
How reproducible:
# grep services /etc/sssd/sssd.conf
services = nss, sudo, pam, ssh
# sssctl list-domains
Unable to get domains list [3]: Communication error
org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Check that SSSD is running and the InfoPipe responder is enabled.
# sed -i 's/services = nss, sudo, pam, ssh/services = nss, sudo, pam, ssh, ifp/' /etc/sssd/sssd.conf
# systemctl restart sssd
# grep services /etc/sssd/sssd.conf
services = nss, sudo, pam, ssh, ifp
# sssctl list-domains
testrelm.test
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
The error message already says that the InfoPipe needs to be enabled. What would you like to see more?
"Check that SSSD is running and the InfoPipe responder is enabled."
I linked this bugzilla to two upstream tickets, one tracks the socket-activation of IFP and targets 7.4. The other tracks the better info message and tracks 7.3.
(In reply to Lukas Slebodnik from comment #6)
> master:
> * 9b86f8f3c07af6fd3d2b08ff66cf9dcce61e7abf
>
> only #3130 is fixed.
Right, that commit is in RHEL as well, but I would prefer to use this bugzilla for the socket-activation.
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.
https://access.redhat.com/errata/RHEA-2017:2294