Description of problem: Migrated from FC28 to FC30 and no longer able to run "systemd-run --scope --user ...". Logging into system with NIS accounts (on NIS slave) fails to start "systemd --user" due to "Failed to determine user credentials: No such process". Unable to run "systemd-run --scope --user .." due to this problem. Does not affect local users on system. --- NIS account, uid=500 ● user - User Manager for UID 500 Loaded: loaded (/usr/lib/systemd/system/user@.service; static; vendor preset: disabled) Active: failed (Result: protocol) since Tue 2020-04-14 18:58:31 BST; 37min ago Docs: man:user@.service(5) Process: 10042 ExecStart=/usr/lib/systemd/systemd --user (code=exited, status=217/USER) Main PID: 10042 (code=exited, status=217/USER) CPU: 38ms Apr 14 18:58:31 beats systemd[1]: Starting User Manager for UID 500... Apr 14 18:58:31 beats systemd[10042]: user: Failed to determine user credentials: No such process Apr 14 18:58:31 beats systemd[10042]: user: Failed at step USER spawning /usr/lib/systemd/systemd: No such process Apr 14 18:58:31 beats systemd[1]: user: Failed with result 'protocol'. Apr 14 18:58:31 beats systemd[1]: Failed to start User Manager for UID 500. Apr 14 18:58:31 beats systemd[1]: user: Consumed 38ms CPU time. --- Local account, uid=1003 $ id uid=1003(local_guest) gid=1004(local_guest) groups=1004(local_guest) -bash-5.0$ systemctl status user ● user - User Manager for UID 1003 Loaded: loaded (/usr/lib/systemd/system/user@.service; static; vendor preset: disabled) Active: active (running) since Tue 2020-04-14 19:25:15 BST; 33s ago Docs: man:user@.service(5) Main PID: 11150 (systemd) Status: "Startup finished in 1.826s." Tasks: 2 Memory: 6.4M CPU: 369ms CGroup: /user.slice/user-1003.slice/user └─init.scope ├─11150 /usr/lib/systemd/systemd --user └─11153 (sd-pam) Apr 14 19:25:15 beats systemd[11150]: Listening on Multimedia System. Apr 14 19:25:15 beats systemd[11150]: Reached target Paths. Apr 14 19:25:15 beats systemd[11150]: Starting D-Bus User Message Bus Socket. Apr 14 19:25:15 beats systemd[11150]: Started Mark boot as successful after the user session has run 2 minutes. Apr 14 19:25:15 beats systemd[11150]: Reached target Timers. Apr 14 19:25:15 beats systemd[11150]: Listening on D-Bus User Message Bus Socket. Apr 14 19:25:15 beats systemd[11150]: Reached target Sockets. Apr 14 19:25:15 beats systemd[11150]: Reached target Basic System. Apr 14 19:25:15 beats systemd[11150]: Reached target Main User Target. Apr 14 19:25:15 beats systemd[11150]: Startup finished in 1.826s. --- Version-Release number of selected component (if applicable): FC30, systemd 241, kernel booted with cgroup2 How reproducible: Every time Steps to Reproduce: 1. Create NIS account on nisserver, create NIS slave FC30, sync accounts with FC30 slave 2. Login to NIS slave host Actual results: systemd --user not run for NIS account (user fails) Expected results: systemd --user run for NIS account (user success) and able to run systemctl --user status Additional info: kernel booted with cgroup2 selinux disabled in config authselect current Profile ID: nis Enabled features: - with-pamaccess
installing and running "nscd" appears to resolve the problem and logging in with NIS account results in "user" starting
This message is a reminder that Fedora 30 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 30 on 2020-05-26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '30'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 30 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Investigated on F32 - bug report here: https://bugzilla.redhat.com/show_bug.cgi?id=1831141 Same issue, NIS user does not start "systemd --user" wihtout nscd running
*** Bug 1831141 has been marked as a duplicate of this bug. ***
This message is a reminder that Fedora 32 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 32 on 2021-05-25. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '32'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 32 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 32 changed to end-of-life (EOL) status on 2021-05-25. Fedora 32 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.