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:
"systemd --user" instance is useful for tty sessions only, not for sftp or ftp sessions.
Currently, since the spawning is performed by pam_systemd, every single PAM aware service sourcing pam_systemd (usually because it includes password-auth) will see a "systemd --user" instance being spawned.
This makes the system perform poorly when it's designed to serve many requests from outside world, e.g. it hosts a ftp service implemented by vsftpd.
The available workarounds are not convenient at all:
Workaround 1: Disable user@.service globally. Impact: GUI sessions are not possible anymore
Workaround 2: De-duplicate the PAM stack and remove "pam_systemd" for the service not needing "systemd --user", but then cgroup creation is not performed anymore
Version-Release number of selected component (if applicable):
systemd-239-41.el8_3.1.x86_64
How reproducible:
N/A
Whether pam_systemd.so is included in the setup of the PAM session depends entirely on the PAM configuration. In order to prevent launching systemd --user instances when it is not desirable we should fix the appropriate PAM configuration files. Also this RHEL-8 change should be coordinated with corresponding authselect changes so that we have the same behaviour in recent Fedoras and in RHEL-9.
I'm sorry for the ping pong, but lets switch the component back to systemd.
We could fix this in pam/authselect and omit pam_systemd for some services, but the same can be done in pam_systemd itself - be a noop for services where it does not make sense to run it. This would be much better choice since from pam point of view, we can not decide (and guarantee) which services are valid for pam_systemd and which are not. It would be also safer for the future as only pam_systemd would need to be changed if the list of irrelevant services changes.
Comment 5RHEL Program Management
2023-09-21 11:07:59 UTC
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.
Comment 6RHEL Program Management
2023-09-21 11:11:35 UTC
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.
Due to differences in account names between systems, some fields were not replicated. Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.
To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer. You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:
"Bugzilla Bug" = 1234567
In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.