One more question, any reason for these error messages in the logs after restarting systemd-logind?
May 20 11:12:50 secondary systemd-logind[382684]: New seat seat0.
May 20 11:12:50 secondary systemd-logind[382684]: User or group name "0" starts with a digit, accepting for compatibility.
May 20 11:12:50 secondary systemd-logind[382684]: Failed to add user by file name 0, ignoring: Invalid argument
May 20 11:12:50 secondary systemd-logind[382684]: User enumeration failed: Invalid argument
May 20 11:13:41 primary systemd[1]: Starting Login Service...
May 20 11:13:41 primary systemd-logind[110604]: New seat seat0.
May 20 11:13:41 primary systemd-logind[110604]: User or group name "199" starts with a digit, accepting for compatibility.
May 20 11:13:41 primary systemd-logind[110604]: Failed to add user by file name 199, ignoring: Invalid argument
May 20 11:13:41 primary systemd-logind[110604]: User or group name "6105" starts with a digit, accepting for compatibility.
May 20 11:13:41 primary systemd-logind[110604]: Failed to add user by file name 6105, ignoring
May 20 11:12:50 secondary systemd-logind[382684]: New seat seat0.
May 20 11:12:50 secondary systemd-logind[382684]: User or group name "0" starts with a digit, accepting for compatibility.
May 20 11:12:50 secondary systemd-logind[382684]: Failed to add user by file name 0, ignoring: Invalid argument
May 20 11:12:50 secondary systemd-logind[382684]: User enumeration failed: Invalid argument
May 20 11:13:41 primary systemd[1]: Starting Login Service...
May 20 11:13:41 primary systemd-logind[110604]: New seat seat0.
May 20 11:13:41 primary systemd-logind[110604]: User or group name "199" starts with a digit, accepting for compatibility.
May 20 11:13:41 primary systemd-logind[110604]: Failed to add user by file name 199, ignoring: Invalid argument
May 20 11:13:41 primary systemd-logind[110604]: User or group name "6105" starts with a digit, accepting for compatibility.
May 20 11:13:41 primary systemd-logind[110604]: Failed to add user by file name 6105, ignoring
On Wed, May 20, 2020 at 11:07 AM Robert Kudyba <rkudyba@xxxxxxxxxxx> wrote:
On Di, 19.05.20 23:36, Robert Kudyba (rkudyba@xxxxxxxxxxx) wrote:
> Just upgraded for Fedora 32, still running NUS/ypserv, now getting
> very slow logins and systemd-logind is not starting. I enabled debug
> logs and am seeing the below logs. I don't think
> https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_systemd_systemd_issues_7074&d=DwIBAg&c=aqMfXOEvEJQh2iQMCb7Wy8l0sPnURkcqADc2guUW8IM&r=X0jL9y0sL4r4iU_qVtR3lLNo4tOL1ry_m7-psV3GejY&m=g-sQXgHR3VJuVTBfUvADrmjl8NIsPaBKboi8ZUH0gOA&s=X94m6OxWpvg9NhGqgPLaACIrMX1q1gleuH8E5qtUR3U&e= is back with the
> nss-nis bug but I made sure that IPAddress= is set (to nothing).
Make sure to turn the sandboxing off for systemd-userdb.service too if
you want to use NIS.OK this wasn't obvious to me but I believe I found it. How does one know how to turn off sandboxing for this service? Is there a document that mentions IPAddress = achieves this?In /usr/lib/systemd/system/systemd-userdbd.service I set IPAddress= (again blank it did have "Any" set). I restarted that service (after running systemctl daemon-reload). That also took about a minute. Then restarting systemd-logind.service worked and logins are now quick. I created a Bugzilla for this https://bugzilla.redhat.com/show_bug.cgi?id=1837808
_______________________________________________ systemd-devel mailing list systemd-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/systemd-devel
