#1059 SSSD backend gets killed on slow systems
Closed: Fixed None Opened 12 years ago by jhrozek.

https://bugzilla.redhat.com/show_bug.cgi?id=746654

On system with slow network connections or on system under heavy load, the SSSD
backend fails to response to monitor pings through SBUS in time and it gets
killed repeatedly.

This results in logins taking several minutes. Sometimes the login process gets
frozen altogether.

Filing for book-keeping purposes. This was already fixed in:

- master: 1d197aa10d020a377c4cd4993a6a2a24743544e3
- sssd-1.6: c0ae9495a82a484941faa64ca86f43860b890dcb
- sssd-1.5: 5b4cd5c1aeade6092aaa561eb35e1381905f072f

coverity: =>
description: https://bugzilla.redhat.com/show_bug.cgi?id=746654

{{{
On system with slow network connections or on system under heavy load, the SSSD
backend fails to response to monitor pings through SBUS in time and it gets
killed repeatedly.

This results in logins taking several minutes. Sometimes the login process gets
frozen altogether.
}}}
=> https://bugzilla.redhat.com/show_bug.cgi?id=746654

{{{
On system with slow network connections or on system under heavy load, the SSSD
backend fails to response to monitor pings through SBUS in time and it gets
killed repeatedly.

This results in logins taking several minutes. Sometimes the login process gets
frozen altogether.
}}}

patch: => 0
resolution: => fixed
rhbz: => 746654
status: new => closed
tests: => 0
testsupdated: => 0
upgrade: => 0

Metadata Update from @jhrozek:
- Issue set to the milestone: SSSD 1.5.14

7 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/2101

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