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:

With RHEL8, "systemd --user" instance spawns when a user slice is created. Upon user slice destruction, a "systemctl --user --force exit" command is executed.
Due to race condition, systemd (PID 1) kills the "systemctl" command above and print a message at NOTICE level, which pollutes the logs.


Version-Release number of selected component (if applicable):

systemd-239-31.el8_2.2


How reproducible:

Almost Always


Steps to Reproduce:
1. Login using ssh as a non-logged in user

  # ssh <user>@vm-rhel8 true

2. Check the journal

  # journalctl -p notice -u user@<userid>.service --follow

Actual results:

Jul 27 13:34:20 vm-rhel8 systemd[1]: user@<userid>.service: Killing process 2891 (systemctl) with signal SIGKILL.


Expected results:

No message, or at least at INFO level max


Additional info:

This seems due to a race condition when closing the last session: systemd(1) still sees the "systemctl --user --force exit" command which makes "systemd --user" exit and wait for it to exit.
A solution may be to use "systemctl --user --force --no-block exit" instead.

fix merged to github master branch -> https://github.com/redhat-plumbers/systemd-rhel8/pull/136

fix merged to github master branch ->

fix merged to github master branch -> https://github.com/redhat-plumbers/systemd-rhel8/pull/236

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 (systemd bug fix and enhancement 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/RHBA-2022:2069