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.
I've also seen
systemd: user-runtime-dir: Failed with result 'start-limit-hit'.
systemd: Failed to start /run/user/5678 mount wrapper.
systemd: Dependency failed for User Manager for UID 5678.
systemd: user: Job user/start failed with result 'dependency'.
sshd: pam_systemd(sshd:session): Failed to create session: Start job for unit user failed with 'dependency'
on a minimal install of RHEL-8.4.0 @ s390x, which seems to be related to this BZ.
(5678 is an unprivileged UID)
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-2021:4469
Description of problem: We need to backport commit d06e8fbce35c2b52ee1d09af4888876d5f2d7ae4 related to user-runtime-dir@.service. This commit makes sure the user-runtime-dir@.service is really done before starting "systemd --user", which is really required or else race conditions happen leading the "systemd --user" failure. Version-Release number of selected component (if applicable): systemd-239-41.el8_3.1.x86_64 How reproducible: Always using a systemtap script Steps to Reproduce: 1. Create delay_mount_runtimepath.stp that will delay the mount of /run/user/<UID> operation (here below UID 101166) -------- 8< ---------------- 8< ---------------- 8< ---------------- 8< -------- probe syscall.mount.call { if (argstr =~ "\"/run/user/101166\"") { delay = 1500 + randint(150) printf("PID %lu (%s) entered '%s(%s)', delaying call by %ld\n", pid(), execname(), name, argstr, delay) mdelay(delay) } } -------- 8< ---------------- 8< ---------------- 8< ---------------- 8< -------- 2. Execute the stap script (requires Guru mode) -------- 8< ---------------- 8< ---------------- 8< ---------------- 8< -------- # yum -y install systemtap # stap-prep # stap -g -v ./delay_mount_runtimepath.stp [...] Pass 5: starting run. -------- 8< ---------------- 8< ---------------- 8< ---------------- 8< -------- 3. Log in through ssh as the target user -------- 8< ---------------- 8< ---------------- 8< ---------------- 8< -------- # ssh rmetrich@localhost true -------- 8< ---------------- 8< ---------------- 8< ---------------- 8< -------- Actual results: - Stap output: -------- 8< ---------------- 8< ---------------- 8< ---------------- 8< -------- PID 4281 (systemd-user-ru) entered 'mount("tmpfs", "/run/user/101166", "tmpfs", MS_NOSUID|MS_NODEV, "mode=0700,uid=101166,gid=101166,size=190722048")', delaying call by 1575 -------- 8< ---------------- 8< ---------------- 8< ---------------- 8< -------- - Journal: -------- 8< ---------------- 8< ---------------- 8< ---------------- 8< -------- Apr 06 08:57:17.748899 vm-sssd8 systemd[3994]: pam_unix(systemd-user:session): session opened for user rmetrich by (uid=0) Apr 06 08:57:19.284443 vm-sssd8 systemd[3994]: Failed to fully start up daemon: Permission denied Apr 06 08:57:19.285148 vm-sssd8 systemd[3995]: pam_unix(systemd-user:session): session closed for user rmetrich Apr 06 08:57:19.285853 vm-sssd8 systemd[1]: user: Failed with result 'protocol'. Apr 06 08:57:19.286015 vm-sssd8 systemd[1]: Failed to start User Manager for UID 101166. Apr 06 08:57:19.286443 vm-sssd8 systemd[1]: Stopping /run/user/101166 mount wrapper... Apr 06 08:57:19.287687 vm-sssd8 sshd[3991]: pam_systemd(sshd:session): Failed to create session: Start job for unit user failed with 'failed' -------- 8< ---------------- 8< ---------------- 8< ---------------- 8< -------- Expected results: No error spawning "systemd --user" Additional info: See also BZ #1945569 for hardening this.