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://github.com/systemd/systemd/issues/7074 is back with the nss-nis bug but I made sure that IPAddress= is set (to nothing). May 19 23:18:48 ourserver systemd-logind[26154]: /run/systemd/userdb/io.systemd.Multiplexer: varlink: changing state awaiting-reply → pending-timeout May 19 23:18:48 ourserver systemd-logind[26154]: /run/systemd/userdb/io.systemd.Multiplexer: varlink: changing state pending-timeout → processing-timeout May 19 23:18:48 ourserver systemd-logind[26154]: Got lookup error: io.systemd.TimedOut May 19 23:18:48 ourserver systemd-logind[26154]: /run/systemd/userdb/io.systemd.Multiplexer: varlink: changing state processing-timeout → disconnected May 19 23:18:48 ourserver systemd-logind[26154]: Couldn't add lingering user myuser, ignoring: Connection timed out May 19 23:18:48 ourserver systemd-logind[26154]: n/a: varlink: setting state idle-client May 19 23:18:48 ourserver systemd-logind[26154]: /run/systemd/userdb/io.systemd.Multiplexer: Sending message: {"method":"io.systemd.UserDatabase.GetUserRecord","parameters":{"userName":"localuser","service":"io.systemd.Multiplexer"}} May 19 23:18:48 ourserver systemd-logind[26154]: /run/systemd/userdb/io.systemd.Multiplexer: varlink: changing state idle-client → awaiting-reply May 19 23:19:33 ourserver systemd[1]: systemd-logind.service: start operation timed out. Terminating. May 19 23:19:34 ourserver systemd-logind[26154]: /run/systemd/userdb/io.systemd.Multiplexer: varlink: changing state awaiting-reply → pending-timeout May 19 23:19:34 ourserver systemd-logind[26154]: /run/systemd/userdb/io.systemd.Multiplexer: varlink: changing state pending-timeout → processing-timeout May 19 23:19:34 ourserver systemd-logind[26154]: Got lookup error: io.systemd.TimedOut May 19 23:19:34 ourserver systemd-logind[26154]: /run/systemd/userdb/io.systemd.Multiplexer: varlink: changing state processing-timeout → disconnected May 19 23:19:34 ourserver systemd-logind[26154]: Couldn't add lingering user localguy, ignoring: Connection timed out May 19 23:19:34 ourserver systemd-logind[26154]: User enumeration failed: Connection timed out May 19 23:19:34 ourserver systemd-logind[26154]: Watching system buttons on /dev/input/event0 (Power Button) May 19 23:19:34 ourserver systemd-logind[26154]: Watching system buttons on /dev/input/event1 (Barcode Reader ) May 19 23:19:34 ourserver systemd-logind[26154]: Watching system buttons on /dev/input/event3 (Barcode Reader System Control) May 19 23:19:34 ourserver systemd-logind[26154]: Watching system buttons on /dev/input/event4 (Barcode Reader Consumer Control) May 19 23:19:34 ourserver systemd-logind[26154]: systemd-logind running as pid 26154 May 19 23:19:34 ourserver systemd-logind[26154]: Bus n/a: changing state AUTHENTICATING → CLOSED May 19 23:19:34 ourserver systemd-logind[26154]: systemd-logind stopped as pid 26154 May 19 23:19:34 ourserver systemd[1]: systemd-logind.service: Failed with result 'timeout'. -- Subject: Unit failed -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- The unit systemd-logind.service has entered the 'failed' state with result 'timeout'. May 19 23:19:34 ourserver systemd[1]: Failed to start Login Service. -- Subject: A start job for unit systemd-logind.service has failed -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A start job for unit systemd-logind.service has finished with a failure. -- -- The job identifier is 14622 and the job result is failed. May 19 23:19:34 ourserver systemd[1]: systemd-logind.service: Scheduled restart job, restart counter is at 2. -- Subject: Automatic restarting of a unit has been scheduled -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Automatic restarting of the unit systemd-logind.service has been scheduled, as the result for -- the configured Restart= setting for the unit. May 19 23:19:34 ourserver systemd[1]: Stopped Login Service. -- Subject: A stop job for unit systemd-logind.service has finished -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A stop job for unit systemd-logind.service has finished. -- -- The job identifier is 14731 and the job result is done. May 19 23:19:34 ourserver systemd[1]: Condition check resulted in Load Kernel Module drm being skipped. -- Subject: A start job for unit modprobe@drm.service has finished successfully -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A start job for unit modprobe@drm.service has finished successfully. -- -- The job identifier is 14838. May 19 23:19:34 ourserver systemd[1]: Starting Login Service... -- Subject: A start job for unit systemd-logind.service has begun execution -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A start job for unit systemd-logind.service has begun execution. -- -- The job identifier is 14731. May 19 23:19:34 ourserver systemd-logind[26377]: Found cgroup2 on /sys/fs/cgroup/, full unified hierarchy May 19 23:19:34 ourserver systemd-logind[26377]: Failed to read memory.max cgroup attribute, ignoring cgroup memory limit: No such file or directory May 19 23:19:34 ourserver systemd-logind[26377]: Bus n/a: changing state UNSET → OPENING May 19 23:19:34 ourserver systemd-logind[26377]: Bus n/a: changing state OPENING → AUTHENTICATING May 19 23:19:34 ourserver systemd-logind[26377]: New seat seat0. -- Subject: A new seat seat0 is now available -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- Documentation: https://www.freedesktop.org/wiki/Software/systemd/multiseat -- -- A new seat seat0 has been configured and is now available. May 19 23:19:34 ourserver systemd-logind[26377]: Preallocating VTs... May 19 23:19:34 ourserver systemd-logind[26377]: VT changed to 1 May 19 23:19:34 ourserver systemd-logind[26377]: n/a: varlink: setting state idle-client May 19 23:19:34 ourserver systemd-logind[26377]: /run/systemd/userdb/io.systemd.Multiplexer: Sending message: {"method":"io.systemd.UserDatabase.GetUserRecord","parameters":{"userName":"myuser","service":"io.systemd.Multiplexer"}} May 19 23:19:34 ourserver systemd-logind[26377]: /run/systemd/userdb/io.systemd.Multiplexer: varlink: changing state idle-client → awaiting-reply
_______________________________________________ systemd-devel mailing list systemd-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/systemd-devel
