Learn more about these different git repos.
Other Git URLs
OpenLMI sssd provider does not work when sssd service is not running - various sss_sifp_* functions return SSS_SIFP_IO_ERROR error. This is perfectly OK, we just want to know why it fails and that starting sssd service might be a good idea. sss_sifp_get_last_io_error_message() returns cryptic "Launch helper exited with unknown return code 1", which is probably returned by DBus.
sss_sifp_*
SSS_SIFP_IO_ERROR
sss_sifp_get_last_io_error_message()
DBus starts sssd helper /usr/libexec/sssd/sss_signal, which just spits "Could not signal SSSD. Is SSSD running?" to stderr and exits. But DBus does not care about stderr... IMO the helper should stay alive and return something more useful to all API calls.
/usr/libexec/sssd/sss_signal
And either sss_sifp_ functions should then return something like SSS_SIFP_SSSD_STOPPED_ERROR or sss_sifp_get_last_io_error_message could return meaningful error message.
sss_sifp_
sss_sifp_get_last_io_error_message
This request is really a low prio one, I'm going to work around it on OpenLMI using more verbose error message:
printf("Error talking to sssd: %s. Is 'sssd' service running?", sss_sifp_get_last_io_error_message(ctx))
And that is IMO more than enough for now.
Fields changed
milestone: NEEDS_TRIAGE => SSSD Deferred
rhbz: => 0
Metadata Update from @jsafrane: - Issue set to the milestone: SSSD Patches welcome
Thank you for taking time to submit this request for SSSD. Unfortunately this issue was not given priority and the team lacks the capacity to work on it at this time.
Given that we are unable to fulfill this request I am closing the issue as wontfix.
If the issue still persist on recent SSSD you can request re-consideration of this decision by reopening this issue. Please provide additional technical details about its importance to you.
Thank you for understanding.
Metadata Update from @pbrezina: - Issue close_status updated to: wontfix - Issue status updated to: Closed (was: Open)
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/3530
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Login to comment on this ticket.