Learn more about these different git repos.
Other Git URLs
Ticket was cloned from Red Hat Bugzilla (product Red Hat Enterprise Linux 8): Bug 1660461
Description of problem: sssd_be take too long time to reconnect (almost more than 80 seconds) after killing the pid of sssd_be. Version-Release number of selected component (if applicable): sssd-2.0.0-27.el8.x86_64 How reproducible: Always Steps to Reproduce: 1. Configure sssd client 2. Clear the sss cache 3. Find pid of sssd_be and do a kill -STOP `pidof sssd_be` 4. Do a new getent passwd username in another terminal or run getent passwd as back groud process. 5. Now kill -9 `pidof sssd_be` 6. And check user lookup again. Actual results: sssd_be take too long time to reconnect (almost more than 80 seconds). Expected results: Should not take that much long time to reconnect. Additional info: # cat sssd.conf [sssd] config_file_version = 2 services = nss, pam domains = LDAP [nss] filter_groups = root filter_users = root [pam] [domain/LDAP] debug_level=0xFFF0 id_provider = ldap ldap_uri = ldap://server.example.com ldap_search_base = dc=example,dc=com ldap_tls_cacert = /etc/openldap/certs/cacert.asc
Metadata Update from @jhrozek: - Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1660461
Metadata Update from @jhrozek: - Issue set to the milestone: SSSD 2.1
Metadata Update from @pbrezina: - Issue assigned to pbrezina
PR: https://github.com/SSSD/sssd/pull/752
Metadata Update from @jhrozek: - Issue tagged with: PR, bug, regression
Metadata Update from @jhrozek: - Issue set to the milestone: SSSD 2.2 (was: SSSD 2.1)
Metadata Update from @jhrozek: - Issue close_status updated to: Fixed - 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/4892
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.
Log in to comment on this ticket.