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:
When upgrading systemd without restarting the system afterwards, we can see that /run/systemd/sessions directory contains "stale" files, causing a leak and /run filesystem to grow:
# ll /run/systemd/sessions/
total 20
-rw-r--r--. 1 root root 282 Jan 3 13:00 1
prw-------. 1 root root 0 Jan 3 13:00 1.ref
-rw-r--r--. 1 root root 238 Jan 3 13:01 2
-rw-r--r--. 1 root root 251 Jan 3 13:02 3
-rw-r--r--. 1 root root 251 Jan 3 13:02 4
-rw-r--r--. 1 root root 251 Jan 3 13:02 5
# cat /run/systemd/sessions/4
# This is private data. Do not parse.
UID=0
USER=root
ACTIVE=1
STATE=closing
REMOTE=1
STOPPING=1
...
Each time a new session is created (e.g. when user connects through ssh), a new state file will remain in that directory, even upon session closure.
Version-Release number of selected component (if applicable):
systemd-219-42.el7_4.4.x86_64
How reproducible:
ALWAYS
Steps to Reproduce:
1. Install a RHEL < 7.4 system (e.g. RHEL 7.3)
2. Upgrade systemd to latest version
# yum -y update systemd
3. Connect to the system using ssh
# ssh root@reproducer true
Actual results:
Every connection (3.) leads to a new state file that doesn't get deleted.
Additional info:
Workaround (root cause?) is to restart systemd-logind service upon upgrade.