Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
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 1360159

Summary: 100% CPU utilization when SSH connections reach ~10 per second
Product: Red Hat Enterprise Linux 7 Reporter: Jan Kurik <jkurik>
Component: systemdAssignee: systemd-maint
Status: CLOSED ERRATA QA Contact: Frantisek Sumsal <fsumsal>
Severity: high Docs Contact:
Priority: urgent    
Version: 7.2CC: bblaskov, btotty, chorn, fkrska, fsumsal, jgenus, lmanasko, lnykryn, mmatsuya, myamazak, ovasik, ssahani, sshaurya, systemd-maint-list, systemd-maint, yoguma
Target Milestone: rcKeywords: Regression, ZStream
Target Release: ---   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: systemd-219-19.el7_2.13 Doc Type: Bug Fix
Doc Text:
Previously, the cgroups-agent program used D-Bus for its messaging. Because the dbus-daemon used a backlog of 30 connections on its D-bus system bus socket, reaching the limit of 30 queued connections could consequently result in losing cgroup empty messages from further connections. This update adds a separate cgroup agent socket of the AF_UNIX/SOCK_DGRAM type, which needs no connection set up and for no listen() backlog applies. Now, if the cgroups-agent binary file cannot queue datagram messages, it does not attempt for re-connection but instead blocks the datagram messages. As a result, cgroup empty messages are no longer lost, the session scopes for an SSH connection no longer trigger a memory leak, and the load increases.
Story Points: ---
Clone Of: 1305608 Environment:
Last Closed: 2016-09-15 08:00:05 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1305608    
Bug Blocks:    

Description Jan Kurik 2016-07-26 06:51:20 UTC
This bug has been copied from bug #1305608 and has been proposed
to be backported to 7.2 z-stream (EUS).

Comment 22 errata-xmlrpc 2016-09-15 08:00:05 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-2016-1835.html