gentoo console login times out for 25 seconds after password entered.

whansard · 03-26-2021, 09:47 AM

Quote:

Mar 26 09:36:39 Wil login[3660]: pam_unix(login:session): session opened for user root(uid=0) by LOGIN(uid=0)
Mar 26 09:36:39 Wil dbus-daemon[3486]: [system] Activating service name='org.freedesktop.login1' requested by ':1.0' (uid=0 pid=3660 comm="/bin/login -- ") (using servicehelper)
Mar 26 09:36:39 Wil elogind-daemon[3670]: Cannot determine cgroup we are running in: No medium found
Mar 26 09:36:39 Wil elogind-daemon[3670]: Failed to allocate manager object: No medium found
Mar 26 09:37:04 Wil dbus-daemon[3486]: [system] Failed to activate service 'org.freedesktop.login1': timed out (service_start_timeout=25000ms)
Mar 26 09:37:04 Wil login[3660]: pam_elogind(login:session): Failed to create session: Failed to activate service 'org.freedesktop.login1': timed out (service_start_timeout=25000ms)
Mar 26 09:37:04 Wil login[3675]: ROOT LOGIN on '/dev/tty1'

this is var/log/messages where it happend

Brains · 03-29-2021, 12:43 AM

Quote:

Failed to activate service 'org.freedesktop.login1'

The service name is "systemd.logind.service"
Boot back to the install CD, chroot into it and check status and enable if disabled as such:

Code:

systemctl status systemd.logind
systemctl enable systemd.logind

I'm assuming you set a root password during installation. Are you still in the installation phase or was everything cool and this just happened out of the blue?

EDIT: If you installed a DE like Gnome or Plasma, enabling gdm.service or sddm.service will enable systemd.logind

whansard · 04-01-2021, 04:15 PM

this is a gentoo install over 20 years old, and upgraded hundreds of times, moved to each new computer i've gotten over the years. i don't think there is any systemd on here. it lets me login, but it waits 25 seconds after the password, before letting me do anything. no graphical login. i've got over 30 operating systems on this computer, so it's not important. if i get too frustrated with it after a while, I'll restore a backup from before the problems.

Emerson · 04-01-2021, 04:42 PM

Gentoo works great if you keep it consistent. And you keep it up to date. In Gentoo forums I have seen problems created by too old GCC, for instance. User upgraded gcc, but forgot to enable it and was still running old incompatible gcc version, creating weird problems all across the board. This is why any Gentoo support request should start with posting 'emerge --info'. Such timeouts are often caused by some DNS issue, but of course it is only a guess.

Edit: it may be your kernel is missing a feature which is required by upgraded system. These are easy to miss if you do not pay attention to portage messages.

whansard · 10-18-2022, 01:53 PM

Code:

/usr/share/dbus-1/system-services # mv org.freedesktop.login1.service .org.freedesktop.login1.service

ended the timeout. i had never searched for org.freedesktop.login1.service anywhere except in /etc.

now i get the folling in /var/log/messages, but no timeout, and a successful login.

Oct 18 13:43:23 Wil dbus-daemon[3732]: [system] Activating service name='org.freedesktop.login1' requested by ':1.22' (uid=0 pid=6824 comm="/bin/login -- ") (using servicehelper)
Oct 18 13:43:23 Wil dbus-daemon[3732]: [system] Activated service 'org.freedesktop.login1' failed: Bus name not found in system service directory
Oct 18 13:43:23 Wil login[6824]: pam_elogind(login:session): Failed to create session: Bus name not found in system service directory

computersavvy · 10-18-2022, 06:12 PM

Maybe the system needs both org.freedesktop.login1.service and .org.freedesktop.login1.service. If that is the case then having one as the actual file and one as a link should suffice.