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 1340176 - The AD keytab renewal task leaks a file descriptor
Summary: The AD keytab renewal task leaks a file descriptor
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: sssd
Version: 6.0
Hardware: All
OS: All
urgent
urgent
Target Milestone: rc
: ---
Assignee: SSSD Maintainers
QA Contact: Steeve Goveas
Aneta Šteflová Petrová
URL:
Whiteboard:
Depends On:
Blocks: 1344657
TreeView+ depends on / blocked
 
Reported: 2016-05-26 15:46 UTC by Jakub Hrozek
Modified: 2020-05-02 18:22 UTC (History)
12 users (show)

Fixed In Version: sssd-1.13.3-25.el6
Doc Type: Bug Fix
Doc Text:
Attempts to renew the system password in a keytab no longer cause SSSD to stop working When attempting to renew the system password stored in a keytab, System Security Services Daemon (SSSD) leaked a file descriptor. The leaked file descriptors gradually accumulated, which caused SSSD to stop working. With this update, SSSD no longer leaks file descriptors in this situation. As a result, SSSD is able to keep updating the system password without the described negative impact on the system.
Clone Of:
: 1344657 (view as bug list)
Environment:
Last Closed: 2017-03-21 09:56:53 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github SSSD sssd issues 4047 0 None None None 2020-05-02 18:22:12 UTC
Github SSSD sssd issues 4058 0 None None None 2020-05-02 18:22:49 UTC
Red Hat Product Errata RHBA-2017:0632 0 normal SHIPPED_LIVE sssd bug fix and enhancement update 2017-03-21 12:30:13 UTC

Description Jakub Hrozek 2016-05-26 15:46:58 UTC 
This bug is created as a clone of upstream ticket:
https://fedorahosted.org/sssd/ticket/3017

The renewal task opens a write_to_child_fd but never closes it, leading to a leak of fd.
Comment 1 Jakub Hrozek 2016-05-26 15:49:54 UTC 
To reproduce, configure sssd to renew the machine credentials frequently and watch /proc/$(pidof sssd_be)/fds. With the unpatched version, sssd will leak a file descriptor after each iteration and you should see a new fd as a new number in the /proc output. With the patched version, the number of fds should be stable (after the initial connections are established).
Comment 2 Jakub Hrozek 2016-05-26 15:50:24 UTC 
Steeve, can you please qa_ack this bug given the reproducer above?
Comment 3 Jakub Hrozek 2016-05-26 15:51:18 UTC 
Upstream ticket:
https://fedorahosted.org/sssd/ticket/3006
Comment 4 Jakub Hrozek 2016-05-31 11:22:51 UTC 
Fixed in:
    master: 518f5b83fd546e3188da01e4743ddb27a574e08f
    sssd-1-13: 312d211e03b9f3769a0362f1767cc59792e32746 
and:
    master: 45e11be651dbd3855a35de4abd2922e5b9d4b963
    sssd-1-13: 2fb750062a665dbf318b5ffb2e53f1060e43b8dc
Comment 11 Dan Lavu 2016-07-01 17:29:52 UTC 
Verified.

Failing in sssd-1.13.3-22.el6.

::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
:: [   LOG    ] :: bug_automation_013: bz1340176 - The AD keytab renewal task leaks a file descriptor
::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::

:: [ 12:33:36 ] :: File descriptors on initial start: 22
:: [ 12:35:36 ] :: File descriptors open after running for 2 minutes: 33
:: [ 12:37:36 ] :: File descriptors open after running for 4 minutes: 45


Working in sssd-client-1.13.3-25.el6

::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
:: [   LOG    ] :: bug_automation_013: bz1340176 - The AD keytab renewal task leaks a file descriptor
::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::

:: [ 13:25:31 ] :: File descriptors open on initial start: 22
:: [ 13:27:31 ] :: File descriptors open after running for 2 minutes: 22
:: [ 13:29:31 ] :: File descriptors open after running for 4 minutes: 22
Comment 16 Dan Lavu 2016-12-21 15:41:56 UTC 
Now verifying the right bug, against version 1.13.3-54.el6.


::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
:: [   LOG    ] :: The AD keytab renewal task leaks a file descriptor bz1340176
::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::

:: [   LOG    ] :: File descriptors open on initial start: 4
:: [   LOG    ] :: File descriptors open after running for 2 minutes: 4
:: [   LOG    ] :: File descriptors open after running for 4 minutes: 4
:: [   PASS   ] :: File descriptors are not increasing 
:: [   LOG    ] :: Duration: 4m 16s
:: [   LOG    ] :: Assertions: 1 good, 0 bad
:: [   PASS   ] :: RESULT: The AD keytab renewal task leaks a file descriptor bz1340176
Comment 18 errata-xmlrpc 2017-03-21 09:56:53 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, 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://rhn.redhat.com/errata/RHBA-2017-0632.html
Note You need to log in before you can comment on or make changes to this bug.