SSSD / sssd

#1622 Setting 'force_timeout = -1' never kills sssd_be/sssd_nss process
Closed: Duplicate Opened by jhrozek.

Closed: Duplicate
Reopen Issue

https://bugzilla.redhat.com/show_bug.cgi?id=874474 (Red Hat Enterprise Linux 6)

Description of problem:
When force_timeout parameter is set to -1 in the DOMAIN/NSS section of
sssd.conf, the backend process never gets killed. Upon verifying the sssd log
files, we can see "Killing service [LDAP]" notification however "Sending
SIGKILL" never notification never appears. Either we should run SIGCONT to get
sssd_be/sssd_nss process restarted or kill all processes explicitly and start
from scratch.
Version-Release number of selected component (if applicable):
sssd-1.9.2-7.el6.x86_64
How reproducible:
Always
Steps to Reproduce:
1. Configure sssd.conf as given below:
[sssd]
reconnection_retries = 3
config_file_version = 2
sbus_timeout = 30
services = nss, pam
domains = LDAP
debug_level = 0x0270
[nss]
filter_groups = root
filter_users = root
reconnection_retries = 3
[pam]
reconnection_retries = 3
[domain/LDAP]
id_provider = ldap
auth_provider = ldap
enumerate = FALSE
cache_credentials = TRUE
debug_level = 9
ldap_uri = ldap://SERVER
ldap_search_base = dc=example,dc=com
ldap_tls_cacert = /etc/openldap/certs/cacert.asc
force_timeout = -1
2. Start sssd service and send SIGSTOP to process sssd_be
   # kill -s SIGSTOP <PID>
3. Monitor sssd.log file for the messages.
   # tail -f /var/log/sssd.log
Actual results:
The sssd service restarts successfully and "Killing service [LDAP]"
notification was seen however, sssd_be never gets killed. We should run SIGCONT
to get sssd_be process restarted.
Expected results:
Either a warning message while restarting the service OR service should never
start.
Additional info:

Fields changed

blockedby: =>
blocking: =>
coverity: =>
design: =>
design_review: => 0
feature_milestone: =>
fedora_test_page: =>
milestone: NEEDS_TRIAGE => SSSD Deferred
testsupdated: => 0

Fields changed

blocking: => [https://fedorahosted.org/sssd/ticket/416 416]

Fields changed

blocking: [https://fedorahosted.org/sssd/ticket/416 416] => [https://fedorahosted.org/sssd/ticket/416 416]

Closing as duplicate of #2269

changelog: =>
mark: => 0
resolution: => duplicate
review: => 0
selected: =>
status: new => closed

Metadata Update from @jhrozek:
- Issue marked as blocked by: #416
- Issue set to the milestone: SSSD Patches welcome

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

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.
Metadata
None
None
None
None
Normal
defect
SSSD
None
0
0
https://bugzilla.redhat.com/show_bug.cgi?id=874474
0
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.