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.

Description of problem:
dbus-daemon fails to close correct file descriptors.

Version-Release number of selected component (if applicable):
dbus-1.6.12-11.el7.x86_64

How reproducible:
Always

Actual results:
'dbus-daemon: Failed to close file descriptor: Could not close fd' messages appear in journal logs


Expected results:
Correct file descriptors should be closed.

Additional info:

This is a known bug which was fixed through https://cgit.freedesktop.org/dbus/dbus/commit/?id=07f4c12efe3b9bd45d109bc5fbaf6d9dbf69d78e

We're hitting this bug often enough that dbus-daemon hits the open fd limit (2144 by default). Once this happens, dbus-daemon starts chewing through 100% CPU time of a core until dbus-daemon is restarted.

In a cluster of 8 machines with the same workload and same uptime we've observed a wide variance in the number of "leaked" fds per hour, ranging from ~0.42 fds/hour to 1.38 fds/hour. However, all machines are leaking fds over time, just at different rates.

Observed with dbus-1.6.12-13.el7.x86_64.

It would be ideal if this could be fixed in time for RHEL 7.3.

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-2016-2453.html