强制重新启动 systemd-logind.service

Question

我在一台服务器上使用 ssh 登录时遇到问题，连接时间太长。我之前在不同的服务器上遇到过同样的情况，并且重新启动 systemd-logind.service 有效。

\n\n

我尝试在这台服务器上执行相同的操作，但在无法重新启动后却显示此消息。

\n\n

#  service  systemd-logind status\nRedirecting to /bin/systemctl status  systemd-logind.service\n\xe2\x97\x8f systemd-logind.service - Login Service\nLoaded: loaded (/usr/lib/systemd/system/systemd-logind.service; static; \n vendor preset: disabled)\n   Active: failed (Result: timeout) since Thu 2018-10-25 16:48:50 CST; 1min 16s ago\n     Docs: man:systemd-logind.service(8)\n           man:logind.conf(5)\n           http://www.freedesktop.org/wiki/Software/systemd/logind\n           http://www.freedesktop.org/wiki/Software/systemd/multiseat\n  Process: 90429 ExecStart=/usr/lib/systemd/systemd-logind (code=exited, status=1/FAILURE)\n Main PID: 90429 (code=exited, status=1/FAILURE)\n   Status: "Shutting down..."\n   CGroup: /system.slice/systemd-logind.service\n           \xe2\x94\x94\xe2\x94\x801037 /usr/lib/systemd/systemd-logind\n\nOct 25 16:42:49 HOST systemd[1]: Starting Login Service...\nOct 25 16:42:49 HOST systemd-logind[90429]: Failed to register name: File exists\nOct 25 16:42:49 HOST systemd[1]: systemd-logind.service: main process exited, code=exited, status=1/FAILURE\nOct 25 16:44:19 HOST systemd[1]: systemd-logind.service stop-sigterm timed out. Killing.\nOct 25 16:45:50 HOST systemd[1]: systemd-logind.service still around after SIGKILL. Ignoring.\nOct 25 16:47:20 HOST systemd[1]: systemd-logind.service stop-final-sigterm timed out. Killing.\nOct 25 16:48:50 HOST systemd[1]: systemd-logind.service still around after final SIGKILL. Entering failed mode.\nOct 25 16:48:50 HOST systemd[1]: Stopped Login Service.\nOct 25 16:48:50 HOST systemd[1]: Unit systemd-logind.service entered failed state.\nOct 25 16:48:50 HOST systemd[1]: systemd-logind.service failed.\n

\n\n

乌纳梅

\n\n

# uname -a\nLinux HOST 3.10.0-514.el7.x86_64 #1 SMP Wed Oct 19 11:24:13 EDT 2016 x86_64 x86_64 x86_64 GNU/Linux\n

\n\n

我什至无法杀死 -9 进程。

\n\n

如果我尝试重新启动

\n\n

SYSTEMD_LOG_LEVEL=debug /usr/lib/systemd/systemd-logind\nFailed to determine peer security context: Protocol not available\nSent message type=method_call sender=n/a destination=org.freedesktop.DBus object=/org/freedesktop/DBus interface=org.freedesktop.DBus member=Hello cookie=1 reply_cookie=0 error=n/a\nGot message type=method_return sender=org.freedesktop.DBus estination=:1.32483949 object=n/a interface=n/a member=n/a cookie=1 reply_cookie=1 error=n/a\nSent message type=method_call sender=n/a destination=org.freedesktop.DBus object=/org/freedesktop/DBus interface=org.freedesktop.DBus member=AddMatch cookie=2 reply_cookie=0 error=n/a\nSent message type=method_call sender=n/a destination=org.freedesktop.DBus object=/org/freedesktop/DBus interface=org.freedesktop.DBus member=AddMatch cookie=3 reply_cookie=0 error=n/a\nSent message type=method_call sender=n/a destination=org.freedesktop.DBus object=/org/freedesktop/DBus interface=org.freedesktop.DBus member=AddMatch cookie=4 reply_cookie=0 error=n/a\nSent message type=method_call sender=n/a destination=org.freedesktop.DBus object=/org/freedesktop/DBus interface=org.freedesktop.DBus member=AddMatch cookie=5 reply_cookie=0 error=n/a\nSent message type=method_call sender=n/a destination=org.freedesktop.DBus object=/org/freedesktop/DBus interface=org.freedesktop.DBus member=AddMatch cookie=6 reply_cookie=0 error=n/a\nSent message type=method_call sender=n/a destination=org.freedesktop.systemd1 object=/org/freedesktop/systemd1 interface=org.freedesktop.systemd1.Manager member=Subscribe cookie=7 reply_cookie=0 error=n/a\nSent message type=method_call sender=n/a destination=org.freedesktop.DBus object=/org/freedesktop/DBus interface=org.freedesktop.DBus member=RequestName cookie=8 reply_cookie=0 error=n/a\nFailed to register name: File exists\nFailed to fully start up daemon: File exists\n

\n