#842 pam and nss clients are hanging if backend is dead
Closed: wontfix 3 years ago by pbrezina. Opened 12 years ago by sbose.

If a backend is really dead and cannot be restarted by the monitor due to too ferquent restarts clients connecting to the pam or nss responder hang until the socket timeout (5min) is over.

If the backend cannot be contacted the connection to the client should be terminated earlier. The pam reponder can return with an appropriate error code and error message while the nss responder can check the cache or return nothing.


Fields changed

milestone: NEEDS_TRIAGE => SSSD Deferred
patch: => 0

Fields changed

rhbz: => 0

Metadata Update from @sbose:
- Issue set to the milestone: SSSD Patches welcome

7 years ago

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)

3 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/1884

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