Bootup stalls sometimes

English Install/Boot/Login
#1

Sometimes bootup to KDE desktop takes much longer than usual, some apps stucks (e. g. skype hangs on login stage), logging in to VT as root takes about 30 sec. So whole desktop almost unusable. This happens with about 50% of booutps.

Interesting parts of logs:


2014-08-16T11:39:39.908482+03:00 mk dbus[613]: [system] Activating systemd to hand-off: service name='org.freedesktop.PolicyKit1' unit='polkit.service'

2014-08-16T11:39:47.737830+03:00 mk dbus[613]: [system] Activating systemd to hand-off: service name='org.freedesktop.login1' unit='dbus-org.freedesktop.login1.service'
2014-08-16T11:40:04.925111+03:00 mk dbus[613]: [system] Failed to activate service 'org.freedesktop.PolicyKit1': timed out
2014-08-16T11:40:04.925547+03:00 mk dbus[613]: [system] Failed to activate service 'org.freedesktop.systemd1': timed out

2014-08-16T11:40:04.926339+03:00 mk systemd-logind[619]: Failed to enable subscription: Activation of org.freedesktop.systemd1 timed out
2014-08-16T11:40:04.927414+03:00 mk dbus[613]: [system] Successfully activated service 'org.freedesktop.login1'
2014-08-16T11:40:04.927935+03:00 mk systemd-logind[619]: New seat seat0.

2014-08-16T11:40:24.563448+03:00 mk dbus[613]: [system] Activating systemd to hand-off: service name='org.freedesktop.UPower' unit='upower.service'
2014-08-16T11:40:29.930690+03:00 mk dbus[613]: [system] Failed to activate service 'org.freedesktop.systemd1': timed out
2014-08-16T11:40:29.931175+03:00 mk systemd-logind[619]: Failed to start unit user-1000.slice: Activation of org.freedesktop.systemd1 timed out
2014-08-16T11:40:29.931516+03:00 mk systemd-logind[619]: Failed to start user slice: Activation of org.freedesktop.systemd1 timed out

2014-08-16T11:40:38.655518+03:00 mk systemd[1]: Failed to start Login Service.
2014-08-16T11:40:38.655839+03:00 mk systemd[1]: Unit systemd-logind.service entered failed state.

2014-08-16T11:40:38.658338+03:00 mk systemd[1]: systemd-logind.service holdoff time over, scheduling restart.
2014-08-16T11:40:38.658613+03:00 mk systemd[1]: Stopping Login Service...
2014-08-16T11:40:38.658907+03:00 mk systemd[1]: Starting Login Service...
2014-08-16T11:40:38.659162+03:00 mk systemd[1]: Started Update UTMP about System Runlevel Changes.

2014-08-16T11:40:49.568250+03:00 mk dbus[613]: [system] Failed to activate service 'org.freedesktop.UPower': timed out
2014-08-16T11:40:49.569621+03:00 mk dbus[613]: [system] Activating systemd to hand-off: service name='org.freedesktop.UPower' unit='upower.service'
2014-08-16T11:40:54.935665+03:00 mk dbus[613]: [system] Failed to activate service 'org.freedesktop.systemd1': timed out
2014-08-16T11:40:54.937080+03:00 mk systemd-logind[2092]: Failed to enable subscription: Activation of org.freedesktop.systemd1 timed out
2014-08-16T11:40:54.937493+03:00 mk systemd-logind[2092]: New seat seat0.

… and then these messages about UPower, systemd1, UDisks2, logind are repeated.

Seems related to https://bugzilla.redhat.com/show_bug.cgi?id=1043212 (same log messages in some of its dups), but for me there’s no /var/run/nologin

I’m at openSUSE 11.3 with all latest updates.
I can’t provide steps to reproduce this bug because of it randomness. So I’m looking for tips how to debug org.freedesktop.PolicyKit1, org.freedesktop.login1 or org.freedesktop.systemd1; or for someone who experienced same bug on openSUSE.

#2

This seems to be a problem related to dbus. AFAIK its timeout is exactly 30 seconds, which would explain a 30 seconds hang when logging in to a VT.
And those messages you posted are about timeouts when trying to reach services via dbus.

Seems related to https://bugzilla.redhat.com/show_bug.cgi?id=1043212 (same log messages in some of its dups), but for me there’s no /var/run/nologin

I doubt that. That bug report is about something creating /var/run/nologin, which would prevent you from logging in at all IIUIC.

I’m at openSUSE 11.3 with all latest updates.

Really? Did you install systemd manually then?
Or is this a typo?

11.3 is out of support for 2.5 years already. And it didn’t even have systemd or logind, so debugging org.freedesktop.login1 or org.freedesktop.systemd1 wouldn’t make sense at all.
In that case it might be better to upgrade to or freshly install a newer openSUSE version. That would probably “fix” your issue as well.

#3

Oh sorry, openSUSE 13.1 of course.

So how can I debug dbus at boot time?

Also what does it mean “Activating systemd to hand-off”? With successful boot I see


2014-08-16T11:56:26.005284+03:00 mk dbus[616]: [system] **Activating via systemd**: service name='org.freedesktop.PolicyKit1unit='polkit.service'


2014-08-16T11:56:28.585859+03:00 mk dbus[616]: [system] Successfully activated service 'org.freedesktop.PolicyKit1

instead.

#4

I have no idea.

Also what does it mean “Activating systemd to hand-off”?

I don’t know really.
Probably it means, that dbus tells systemd to start the corresponding service.
A dbus service can either specify a daemon to be started or a systemd unit.

Your problem seems to be that the communication between dbus and systemd does not reliably work sometimes, or systemd has problems starting the corresponding service/unit.

I do remember a similar sounding problem somebody in the german forum had after a fresh installation of 13.1 32bit. Starting certain applications took a very long time e.g. (minutes)
For him, updating to a newer systemd fixed it.
So maybe try this as well, systemd 210 is available for 13.1 from here:
http://download.opensuse.org/repositories/Base:/System/openSUSE_13.1/

Add the repo, and switch all systemd packages to the versions from that repo (use the “Versions” tab in YaST).

PS: as your main problem in the output you posted seems to be polkit.service, maybe the output of “sudo systemctl status polkit.service” (in the case that the problem appears) might give a clue.
But then, on second thought, it appears to be actually caused by org.freedesktop.systemd1 (this is what times out all the time) which would of course point back to systemd again.