Contents
Why does dbus say systemd start systemd-logind?
Because the service is still running, “systemd start systemd-logind” is a no-op, and since the busname won’t reappear, dbus considers it an activation failure. Other services are prone to the issue as well; networkd however seems to continue living ever since applying said two patches on top of 228. Don’t lose the dbus connection.
What happens when I change dBus to dbus-1.10.24?
Products & Services Knowledgebase RHEL7: after updating dbus from dbus-1.6.12 to dbus-1.10.24, the system is broken, messages such as Note: in some situations, you may see a No such file or directory error message instead of Connection refused.
What to do if dbus failed to activate service?
Eventually after some time you would start seeing some weird behavior like hostnamectl not reporting a thing, or timedatectl reports Failed to query server: Connection timed out and other odd things. As well the symptoms reported originally. One workaround is to delete all ‘session-*.scope’ files and to restart systemd.
When does logind randomly lose its dbus connection?
Mar 31 11:00:01 dagent systemd-logind [128]: Failed to abandon session scope: Transport endpoint is not connected Mar 31 11:05:08 dagent systemd [1]: Started Login Service. Mar 31 11:05:33 dagent systemd-logind [128]: Failed to abandon session scope: Transport endpoint is not connected Mar 31 11:12:58 dagent systemd [1]: Started Login Service.
When did systemd-logind.service entered failed state?
Jan 09 21:21:40 Katana systemd [1]: start request repeated too quickly for systemd-logind.service Jan 09 21:21:40 Katana systemd [1]: Failed to start Login Service. Jan 09 21:21:40 Katana systemd [1]: Unit systemd-logind.service entered failed state.
When did katana systemd failed to start login service?
Jan 10 19:15:33 Katana systemd [1]: start request repeated too quickly for systemd-logind.service Jan 10 19:15:33 Katana systemd [1]: Failed to start Login Service. Jan 10 19:15:33 Katana systemd [1]: Unit systemd-logind.service entered failed state.
Why is my systemd user service not starting?
If -session optional pam_systemd.so is present in your PAM configuration, the user service cannot start, and the error message $XDG_RUNTIME_DIR not found is showing in /var/log/messages , do not attempt to set the environmental variable. In this scenario, the error is not accurate.
Is the systemd user service used in RHEL 7?
The systemd user service is not used as commonly as the normal systemd process manager. Red Hat disabled the systemd user service in RHEL 7 (and thereby all distros that come from RHEL, like CentOS, Oracle Linux 7, Amazon Linux 2).