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.
Bug 1884205 - KCM: Increase client idle timeout to 5 minutes
Summary: KCM: Increase client idle timeout to 5 minutes
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: sssd
Version: 8.3
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: rc
: ---
Assignee: jstephen
QA Contact: Anuj Borah
URL:
Whiteboard: sync-to-jira
Depends On: 1881992
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-10-01 10:55 UTC by Alexey Tikhonov
Modified: 2021-05-18 15:05 UTC (History)
8 users (show)

Fixed In Version: sssd-2.4.0-1.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-05-18 15:03:57 UTC
Type: Enhancement
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github SSSD sssd issues 4829 0 None closed KCM: Increase the default client idle timeout, consider decreasing the timeout on busy servers 2021-02-16 12:18:20 UTC
Github SSSD sssd pull 5413 0 None closed TESTS: KCM: Increase client idle timeout to 5 minutes 2021-02-16 12:18:21 UTC

Description Alexey Tikhonov 2020-10-01 10:55:30 UTC 
By default, KCM has a 60-second idle client timeout. This might not be enough, because the client is often kinit, so there is some user interaction involved.
Comment 1 Alexey Tikhonov 2020-10-01 11:02:00 UTC 
Pushed PR: https://github.com/SSSD/sssd/pull/5288

* `master`
    * 00ae18dc9fd05a0dd12043d50a7fc0f1123bbc85 - KCM: Increase client idle timeout to 5 minutes
Comment 4 Anuj Borah 2020-11-05 07:51:43 UTC 
With fixed and unfixed both have infinite time waiting :

[root@ci-vm-10-0-137-97 sssd]# systemctl stop sssd ; rm -rf /var/log/sssd/* ; rm -rf /var/lib/sss/db/* ; systemctl start sssd
[root@ci-vm-10-0-137-97 sssd]# systemctl restart sssd-kcm 
[root@ci-vm-10-0-137-97 sssd]# id foo1@example1
uid=14583101(foo1@example1) gid=14564100(ldapusers@example1) groups=14564100(ldapusers@example1)
[root@ci-vm-10-0-137-97 sssd]# date
Thu Nov  5 02:20:51 EST 2020
[root@ci-vm-10-0-137-97 sssd]# kinit foo1
Password for foo1: 
kinit: Password read interrupted while getting initial credentials
[root@ci-vm-10-0-137-97 sssd]# date
Thu Nov  5 02:46:00 EST 2020
[root@ci-vm-10-0-137-97 sssd]# rpm -qa | grep sssd
sssd-nfs-idmap-2.3.0-9.el8.x86_64
sssd-krb5-common-2.4.0-1.el8.x86_64
sssd-ipa-2.4.0-1.el8.x86_64
sssd-common-2.4.0-1.el8.x86_64
sssd-krb5-2.4.0-1.el8.x86_64
sssd-common-pac-2.4.0-1.el8.x86_64
sssd-ad-2.4.0-1.el8.x86_64
sssd-2.4.0-1.el8.x86_64
sssd-client-2.4.0-1.el8.x86_64
sssd-ldap-2.4.0-1.el8.x86_64
python3-sssdconfig-2.4.0-1.el8.noarch
sssd-kcm-2.4.0-1.el8.x86_64
[root@ci-vm-10-0-137-97 sssd]# 

KCM log:  

[root@ci-vm-10-0-137-97 sssd]# cat sssd_kcm.log
(2020-11-05  2:28:07): [kcm] [orderly_shutdown] (0x0010): SIGTERM: killing children
[root@ci-vm-10-0-137-97 sssd]# 


sssd.conf:

[root@ci-vm-10-0-137-97 sssd]# cat sssd.conf
[sssd]
config_file_version = 2
services = nss, pam
domains = example1

[domain/example1]
ldap_search_base = dc=example,dc=test
id_provider = ldap
auth_provider = ldap
ldap_user_home_directory = /home/%u
ldap_uri = ldaps://ci-vm-10-0-138-55.hosted.upshift.rdu2.redhat.com
ldap_tls_cacert = /etc/openldap/cacerts/cacert.pem
use_fully_qualified_names = True
debug_level = 9
[root@ci-vm-10-0-137-97 sssd]# 


It was waiting infinitely after:  kinit foo1

Any other config change i have to do ?
Comment 6 Anuj Borah 2020-11-06 03:49:49 UTC 
With Unfixed version:

(Thu Nov  5 22:33:04 2020) [sssd[kcm]] [client_close_fn] (0x2000): Terminated client [0x555fb5bbb330][15]
(Thu Nov  5 22:33:34 2020) [sssd[kcm]] [setup_client_idle_timer] (0x4000): Idle timer re-set for client [0x555fb5bbb080][14]
(Thu Nov  5 22:34:04 2020) [sssd[kcm]] [setup_client_idle_timer] (0x4000): Idle timer re-set for client [0x555fb5bbb080][14]
(Thu Nov  5 22:34:34 2020) [sssd[kcm]] [client_idle_handler] (0x2000): Terminating idle client [0x555fb5bbb080][14]
(Thu Nov  5 22:34:34 2020) [sssd[kcm]] [client_close_fn] (0x2000): Terminated client [0x555fb5bbb080][14]


[root@ci-vm-10-0-139-39 sssd]# rpm -qa | grep sssd
sssd-ldap-2.2.0-19.el8.x86_64
sssd-ipa-2.2.0-19.el8.x86_64
sssd-common-2.2.0-19.el8.x86_64
sssd-client-2.2.0-19.el8.x86_64
sssd-nfs-idmap-2.2.0-19.el8.x86_64
sssd-kcm-2.2.0-19.el8.x86_64
sssd-krb5-common-2.2.0-19.el8.x86_64
sssd-krb5-2.2.0-19.el8.x86_64
sssd-proxy-2.2.0-19.el8.x86_64
sssd-2.2.0-19.el8.x86_64
sssd-common-pac-2.2.0-19.el8.x86_64
python3-sssdconfig-2.2.0-19.el8.noarch
sssd-ad-2.2.0-19.el8.x86_64


With Fixed version:


(2020-11-05 22:39:39): [kcm] [client_close_fn] (0x2000): Terminated client [0x5581403586d0][15]
(2020-11-05 22:42:06): [kcm] [responder_idle_handler] (0x2000): Re-scheduling the idle timeout for the responder [0x558140353340]
(2020-11-05 22:42:06): [kcm] [schedule_responder_idle_timer] (0x2000): Re-scheduling the idle timeout for the responder [0x558140353340]
(2020-11-05 22:42:09): [kcm] [setup_client_idle_timer] (0x4000): Idle timer re-set for client [0x558140358420][14]
(2020-11-05 22:44:36): [kcm] [responder_idle_handler] (0x2000): Re-scheduling the idle timeout for the responder [0x558140353340]
(2020-11-05 22:44:36): [kcm] [schedule_responder_idle_timer] (0x2000): Re-scheduling the idle timeout for the responder [0x558140353340]
(2020-11-05 22:44:39): [kcm] [setup_client_idle_timer] (0x4000): Idle timer re-set for client [0x558140358420][14]
(2020-11-05 22:47:06): [kcm] [responder_idle_handler] (0x2000): Terminating idle responder [0x558140353340]
(2020-11-05 22:47:06): [kcm] [kcm_responder_ctx_destructor] (0x0400): Responder is being shut down
(2020-11-05 22:47:06): [kcm] [client_close_fn] (0x2000): Terminated client [0x558140358420][14]
(2020-11-05 22:47:06): [kcm] [orderly_shutdown] (0x0010): SIGTERM: killing children
(2020-11-05 22:47:06): [kcm] [orderly_shutdown] (0x0040): Shutting down (status = 0)


[root@ci-vm-10-0-137-54 sssd]# rpm -qa | grep sssd
sssd-krb5-common-2.4.0-1.el8.x86_64
sssd-ipa-2.4.0-1.el8.x86_64
sssd-common-2.4.0-1.el8.x86_64
sssd-krb5-2.4.0-1.el8.x86_64
sssd-common-pac-2.4.0-1.el8.x86_64
sssd-ad-2.4.0-1.el8.x86_64
sssd-2.4.0-1.el8.x86_64
sssd-client-2.4.0-1.el8.x86_64
sssd-ldap-2.4.0-1.el8.x86_64
python3-sssdconfig-2.4.0-1.el8.noarch
sssd-kcm-2.4.0-1.el8.x86_64
Comment 11 errata-xmlrpc 2021-05-18 15:03:57 UTC 
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 (sssd bug fix and enhancement update), 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/RHBA-2021:1666
Note You need to log in before you can comment on or make changes to this bug.