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.
This bug was initially created as a copy of Bug #1961746
I am copying this bug because:
It applies to RHEL-9 too.
Description of problem:
When a user enabled "lingering" and the user's password expired, the "systemd --user" instance for the user fails to start and enters failed state.
To recover, it's necessary for some admin to reset the state, which is problematic.
Version-Release number of selected component (if applicable):
systemd-239 (tested on latest from 8.3.0)
How reproducible:
Always
Steps to Reproduce:
1. Create a user, set a password and set lingering
# useradd user
# echo "redhat" | passwd --stdin user
# loginctl enable-linger user
2. Expire the password
# passwd -e user
3. Reboot the system and check user@<id> state
# systemctl status user@$(id -u user).service
Actual results:
May 18 16:23:28 vm-rhel8 systemd[1]: Starting User Manager for UID 1009...
May 18 16:23:28 vm-rhel8 systemd[1247]: pam_unix(systemd-user:account): expired password for user user (root enforced)
May 18 16:23:28 vm-rhel8 systemd[1247]: PAM failed: Authentication token is no longer valid; new one required
May 18 16:23:28 vm-rhel8 systemd[1247]: user: Failed to set up PAM session: Operation not permitted
May 18 16:23:28 vm-rhel8 systemd[1247]: user: Failed at step PAM spawning /usr/lib/systemd/systemd: Oper>
May 18 16:23:28 vm-rhel8 systemd[1]: user: Failed with result 'protocol'.
May 18 16:23:28 vm-rhel8 systemd[1]: Failed to start User Manager for UID 1009.
Expected results:
instance starts anyway? of maybe not but no failed state then.
Additional info:
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:8327