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.
Description of problem:
A customer running Openshift 3.11 is suffering an issue on multiple systems running latest systemd (systemd-219-67.el7_7.1) where he sees systemd consuming 48GB of memory and spending his time sending PropertiesChanged notifications for all devices in loop.
Early investigation shows over a 30s period, systemd
- executed epoll_wait() only 95 times, returning immediately
- read udev 71462 times
- sent 34888 PropertiesChanged notifications (637 devices per "epoll" round)
Extracting coredump informations using "strings" shows the memory is allocated for DBus messages: (strings coredump | sort | uniq -c | sort -nr)
35328408 sa{sv}as
17936804 PropertiesChanged
17902069 org.freedesktop.DBus.Properties
...
Version-Release number of selected component (if applicable):
systemd-219-67.el7_7.1
How reproducible:
Don't know. Often on customer prod boxes
Comparing the RHEL8 and RHEL7 code, I was wondering why I couldn't reproduce.
It appears that the following commit must be backported to RHEL7:
-------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------
commit 5ae37ad833583e6c1c7765767b7f8360afca3b07
Author: Lennart Poettering <lennart>
Date: Fri Dec 15 22:24:16 2017 +0100
sd-bus: when attached to an sd-event loop, disconnect on processing errors
If we can't process the bus for some reason we shouldn't just disable
the event source, but log something and give up on the connection. Hence
do that, and disconnect.
-------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------
In a nutshell, upon receiving -ETIMEDOUT, no special handling should be done in bus_process_internal() but in io_callback() instead.
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 (Low: systemd security and bug fix update), 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://access.redhat.com/errata/RHSA-2020:4007
Description of problem: A customer running Openshift 3.11 is suffering an issue on multiple systems running latest systemd (systemd-219-67.el7_7.1) where he sees systemd consuming 48GB of memory and spending his time sending PropertiesChanged notifications for all devices in loop. Early investigation shows over a 30s period, systemd - executed epoll_wait() only 95 times, returning immediately - read udev 71462 times - sent 34888 PropertiesChanged notifications (637 devices per "epoll" round) Extracting coredump informations using "strings" shows the memory is allocated for DBus messages: (strings coredump | sort | uniq -c | sort -nr) 35328408 sa{sv}as 17936804 PropertiesChanged 17902069 org.freedesktop.DBus.Properties ... Version-Release number of selected component (if applicable): systemd-219-67.el7_7.1 How reproducible: Don't know. Often on customer prod boxes