Bug 1360159
| Summary: | 100% CPU utilization when SSH connections reach ~10 per second | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Jan Kurik <jkurik> |
| Component: | systemd | Assignee: | systemd-maint |
| Status: | CLOSED ERRATA | QA Contact: | Frantisek Sumsal <fsumsal> |
| Severity: | high | Docs Contact: | |
| Priority: | urgent | ||
| Version: | 7.2 | CC: | bblaskov, btotty, chorn, fkrska, fsumsal, jgenus, lmanasko, lnykryn, mmatsuya, myamazak, ovasik, ssahani, sshaurya, systemd-maint-list, systemd-maint, yoguma |
| Target Milestone: | rc | Keywords: | 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
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 |