| Summary: | sys-apps/systemd-216 - systemd[1]: Failed to start Login Service. | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Juergen Rose <rose> |
| Component: | [OLD] Core system | Assignee: | Gentoo systemd Team <systemd> |
| Status: | RESOLVED TEST-REQUEST | ||
| Severity: | normal | ||
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Juergen Rose
2014-09-19 20:05:52 UTC
BTW., the systemd-logind.service have the state "activating (start)" while on other systems the state is "active (running)":
root@gepard:/root(48)# systemctl status systemd-logind
● systemd-logind.service - Login Service
Loaded: loaded (/usr/lib64/systemd/system/systemd-logind.service; static)
Active: activating (start) since Fri 2014-09-19 22:19:09 CEST; 6s ago
Docs: man:systemd-logind.service(8)
man:logind.conf(5)
http://www.freedesktop.org/wiki/Software/systemd/logind
http://www.freedesktop.org/wiki/Software/systemd/multiseat
Main PID: 6084 (systemd-logind)
Status: "Processing requests..."
CGroup: /system.slice/systemd-logind.service
└─6084 /usr/lib/systemd/systemd-logind
Sep 19 22:19:09 gepard systemd-logind[6084]: New seat seat0.
Sep 19 22:19:09 gepard systemd-logind[6084]: Watching system buttons on /dev/input/event2 (Power Button)
Sep 19 22:19:09 gepard systemd-logind[6084]: Watching system buttons on /dev/input/event3 (Video Bus)
Sep 19 22:19:09 gepard systemd-logind[6084]: Watching system buttons on /dev/input/event0 (Lid Switch)
Sep 19 22:19:09 gepard systemd-logind[6084]: Watching system buttons on /dev/input/event1 (Sleep Button)
Sep 19 22:19:09 gepard systemd-logind[6084]: Watching system buttons on /dev/input/event8 (ThinkPad Extra Buttons)
Sep 19 22:19:09 gepard systemd-logind[6084]: New session c1 of user root.
Sep 19 22:19:09 gepard systemd-logind[6084]: New session 1 of user rose.
> Sep 19 20:34:17 gepard dbus[1830]: [system] Failed to activate service 'org.freedesktop.ConsoleKit': timed out
You should probably disable/remove consolekit. You seem to be throwing a lot of logind and dbus related errors, so maybe that's it.
(In reply to Mike Gilbert from comment #2) > > Sep 19 20:34:17 gepard dbus[1830]: [system] Failed to activate service 'org.freedesktop.ConsoleKit': timed out > > You should probably disable/remove consolekit. You seem to be throwing a lot > of logind and dbus related errors, so maybe that's it. It seems that some of my installed packages depend on consolekit: root@gepard:/usr/src/linux(18)# emerge -pv --depclean consolekit Calculating dependencies... done! sys-auth/consolekit-0.4.6 pulled in by: lxde-base/lxdm-0.4.1-r9 requires sys-auth/consolekit net-misc/networkmanager-0.9.8.10-r1 requires sys-auth/consolekit sys-auth/pambase-20140313 requires >=sys-auth/consolekit-0.4.6[pam] x11-apps/xdm-1.1.11-r3 requires sys-auth/consolekit >>> No packages selected for removal by depclean Packages installed: 3641 Packages in world: 805 Packages in system: 44 Required packages: 3641 Number to remove: 0 root@gepard:/usr/src/linux(19)# equery d consolekit * These packages depend on consolekit: gnome-base/gdm-3.12.2 (!systemd ? >=sys-auth/consolekit-0.4.5_p20120320-r2) gnome-base/gnome-control-center-3.12.1-r1 (sys-auth/consolekit) gnome-base/gnome-session-3.12.1 (!systemd ? sys-auth/consolekit) kde-base/kdm-4.11.12 (consolekit ? sys-auth/consolekit) lxde-base/lxdm-0.4.1-r9 (consolekit ? sys-auth/consolekit) net-misc/networkmanager-0.9.8.10-r1 (consolekit ? sys-auth/consolekit) sys-apps/accountsservice-0.6.37 (!systemd ? sys-auth/consolekit) sys-auth/pambase-20140313 (consolekit ? >=sys-auth/consolekit-0.4.6[pam]) sys-auth/polkit-0.112-r2 (!systemd ? sys-auth/consolekit[policykit]) x11-apps/xdm-1.1.11-r3 (consolekit ? sys-auth/consolekit) At http://www.gossamer-threads.com/lists/gentoo/user/288842 I found a discussion about slow ssh rekeying. It was suggested to comment the "-session optional pam_systemd.so" line in /etc/pam.d/system-auth. What do you think is the better solution, to try to reemerge lxdm, networkmanager, pambase, xdm, gdm, gnome-control-center, gnome-session, accountsservice and polkit with "USE=-consolekit" and then delete consolekit ot to comment out the line in /etc/pam.d/system-auth? (In reply to Juergen Rose from comment #3) > (In reply to Mike Gilbert from comment #2) > > > Sep 19 20:34:17 gepard dbus[1830]: [system] Failed to activate service 'org.freedesktop.ConsoleKit': timed out > > > > You should probably disable/remove consolekit. You seem to be throwing a lot > > of logind and dbus related errors, so maybe that's it. > > It seems that some of my installed packages depend on consolekit: > > root@gepard:/usr/src/linux(18)# emerge -pv --depclean consolekit > > Calculating dependencies... done! > sys-auth/consolekit-0.4.6 pulled in by: > lxde-base/lxdm-0.4.1-r9 requires sys-auth/consolekit > net-misc/networkmanager-0.9.8.10-r1 requires sys-auth/consolekit > sys-auth/pambase-20140313 requires >=sys-auth/consolekit-0.4.6[pam] > x11-apps/xdm-1.1.11-r3 requires sys-auth/consolekit ... > At http://www.gossamer-threads.com/lists/gentoo/user/288842 I found a > discussion about slow ssh rekeying. It was suggested to comment the > "-session optional pam_systemd.so" line in /etc/pam.d/system-auth. What do > you think is the better solution, to try to reemerge lxdm, networkmanager, > pambase, xdm, gdm, gnome-control-center, gnome-session, accountsservice and > polkit with "USE=-consolekit" and then delete consolekit ot to comment out > the line in /etc/pam.d/system-auth? After adding "-consolekit" to kdm, lxdm, networkmanager, pambase and xdm in /etc/portage/package.use I could delete consolekit with 'emerge -v --depclean consolekit'. After rebooting the graphical.target and the multi-user.target is still dead. There are still "Failed to start Login Service" messages in the journal: root@gepard:/root(2)# journalctl -xb | grep -i fail Sep 20 14:00:31 gepard kernel: acpi PNP0A03:00: _OSC failed (AE_NOT_FOUND); disabling ASPM Sep 20 14:00:31 gepard kernel: acpi PNP0A08:00: _OSC failed (AE_SUPPORT); disabling ASPM Sep 20 14:00:31 gepard kernel: intel ips 0000:00:1f.6: failed to get i915 symbols, graphics turbo disabled until i915 loads Sep 20 14:00:31 gepard systemd[1]: Cannot add dependency job for unit display-manager.service, ignoring: Unit display-manager.service failed to load: No such file or directory. Sep 20 14:02:53 gepard kernel: iwlwifi 0000:03:00.0: Direct firmware load failed with error -2 Sep 20 14:02:53 gepard kernel: iwlwifi 0000:03:00.0: Direct firmware load failed with error -2 Sep 20 14:02:53 gepard systemd[1]: Failed to subscribe to NameOwnerChanged signal: Connection timed out Sep 20 14:02:53 gepard systemd[1]: Failed to subscribe to activation signal: Connection timed out Sep 20 14:02:53 gepard systemd[1]: Failed to register name: Connection timed out Sep 20 14:02:53 gepard systemd[1]: Failed to set up API bus: Connection timed out Sep 20 14:02:53 gepard systemd[1]: Unit nfs-config.service entered failed state. Sep 20 14:02:53 gepard systemd[1]: Unit systemd-logind.service entered failed state. Sep 20 14:02:53 gepard systemd[1]: Unit sendmail.service entered failed state. Sep 20 14:02:54 gepard dbus[1814]: [system] Failed to activate service 'org.freedesktop.ColorManager': timed out Sep 20 14:02:54 gepard systemd[2000]: Failed at step EXEC spawning /usr/sbin/rpc.statd: No such file or directory -- The process /usr/sbin/rpc.statd could not be executed and failed. Sep 20 14:02:54 gepard systemd[1]: Unit rpc-statd.service entered failed state. Sep 20 14:03:19 gepard dbus[1814]: [system] Failed to activate service 'org.freedesktop.ColorManager': timed out Sep 20 14:03:51 gepard sshd[2067]: pam_systemd(sshd:session): Failed to create session: Connection timed out Sep 20 14:04:24 gepard systemd[1]: Failed to start Login Service. -- Subject: Unit systemd-logind.service has failed -- Unit systemd-logind.service has failed. -- The result is failed. Sep 20 14:04:24 gepard systemd[1]: Unit systemd-logind.service entered failed state. Sep 20 14:05:54 gepard systemd[1]: Failed to start Login Service. -- Subject: Unit systemd-logind.service has failed -- Unit systemd-logind.service has failed. -- The result is failed. Sep 20 14:05:54 gepard systemd[1]: Unit systemd-logind.service entered failed state. Sep 20 14:06:50 gepard sshd[2400]: pam_systemd(sshd:session): Failed to create session: Connection timed out Sep 20 14:07:24 gepard systemd[1]: Failed to start Login Service. -- Subject: Unit systemd-logind.service has failed -- Unit systemd-logind.service has failed. -- The result is failed. Sep 20 14:07:24 gepard systemd[1]: Unit systemd-logind.service entered failed state. Sep 20 14:08:55 gepard systemd[1]: Failed to start Login Service. -- Subject: Unit systemd-logind.service has failed -- Unit systemd-logind.service has failed. -- The result is failed. ... Sep 20 14:14:56 gepard systemd[1]: Unit systemd-logind.service entered failed state. Sep 20 14:16:26 gepard su[2877]: pam_systemd(su:session): Failed to create session: Message did not receive a reply (timeout by message bus) Sep 20 14:16:26 gepard systemd[1]: Failed to start Login Service. -- Subject: Unit systemd-logind.service has failed -- Unit systemd-logind.service has failed. -- The result is failed. Sep 20 14:16:26 gepard systemd[1]: Unit systemd-logind.service entered failed state. Now I coomented out the -session optional pam_systemd.so line in /etc/pam.d/system-auth and rebooted the system. The subsequent login is much faster. It does not hang a long time at "rekeying". But graphical.target and the multi-user.target is still dead and there are still messages about "Failed to start Login Service". Could you try -217, please? Otherwise, we certainly should move this upstream. (In reply to Michał Górny from comment #7) > Could you try -217, please? Otherwise, we certainly should move this > upstream. Can't check now due to Bug 527406. (In reply to Juergen Rose from comment #8) > Can't check now due to Bug 527406. Which has been fixed. Sync your portage tree. Please retry with 225 |
