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:
Memory increase of the systemd process.
The systemd(pid=1) process continues increasing the memory.
Similar problem is reported in the community of systemd, but a new version of systemd seems to be necessary for the solution to problem.
- https://github.com/systemd/systemd/issues/2614
Version-Release number of selected component (if applicable):
[root@rh72-01 ~]# uname -a
Linux rh72-01 3.10.0-327.36.2.el7.x86_64 #1 SMP Tue Sep 27 16:01:21 EDT 2016 x86_64 x86_64 x86_64 GNU/Linux
[root@rh72-01 ~]# rpm -qa |grep systemd
systemd-python-219-19.el7_2.13.x86_64
systemd-219-19.el7_2.13.x86_64
systemd-libs-219-19.el7_2.13.x86_64
systemd-sysv-219-19.el7_2.13.x86_64
How reproducible:
The phenomenon reappears by carrying out the following test scripts which I prepared for beforehand.
This is a script connecting with local host (rh72-02) in ssh.
------test.sh----
#!/bin/sh
while [ 1 ]; do
ssh rh72-01 ls
sleep 1
echo "test"
done
------
Steps to Reproduce:
1. Watch systemd process by top command.
2. Carry out test script.
Actual results:
The RSS of the systemd process that I watched by top command continues increasing.
Expected results:
It cannot be necessary to continue increasing the RSS of the systemd process that I watched by top command.
Best Regards,
Hideo Yamauchi.
Hi Michal,
I was not able to find rpm of systemd-219-19.el7_2.14.
Where should I download rpm of systemd-219-19.el7_2.14 from?
Or should I use rpm of Fedora as Mr. Jan says?
Best Regards,
Hideo Yamauchi.
Hi Jan,
I started confirmation with the package which you told.
I confirm it in consecutive movement until the weekend and report a result.
-----
[root@rh72-01 ~]# rpm -qa |grep systemd
systemd-219-30.el7.centos.3.x86_64
systemd-python-219-30.el7.centos.3.x86_64
systemd-libs-219-30.el7.centos.3.x86_64
systemd-sysv-219-30.el7.centos.3.x86_64
-----
Best Regards,
Hideo Yamauchi.
(In reply to HIDEO YAMAUCHI from comment #6)
>
> Where should I download rpm of systemd-219-19.el7_2.14 from?
> Or should I use rpm of Fedora as Mr. Jan says?
You can't get it from anywhere because this version of systemd was not released yet.
Feel free to test packages from COPR as they also contain a fix.
(In reply to Michal Sekletar from comment #8)
> (In reply to HIDEO YAMAUCHI from comment #6)
>
> >
> > Where should I download rpm of systemd-219-19.el7_2.14 from?
> > Or should I use rpm of Fedora as Mr. Jan says?
>
> You can't get it from anywhere because this version of systemd was not
> released yet.
>
> Feel free to test packages from COPR as they also contain a fix.
Hi Michal,
Okay!
Many thanks!
Hideo Yamauch.
Hi Jan,
Hi Michal,
We confirmed a problem in Errata of released new systemd.
We finally confirmed it in next systemd for one week.
---
systemd-sysv-219-30.el7_3.3.x86_64
systemd-libs-219-30.el7_3.3.x86_64
systemd-python-219-30.el7_3.3.x86_64
systemd-219-30.el7_3.3.x86_64
---
The problem was improved somehow or other in rpm of new systemd.
Please close this Bugzilla.
Many thanks!
Hideo Yamauchi.