Slow boot, journald

English Install/Boot/Login
1

I am experiensing slow boot and systemd-analyze gives me:

➜  ~  systemd-analyze 
Startup finished in 1.891s (kernel) + 2.656s (initrd) + 46.209s (userspace) = 50.756s

output of: systemd-analyze


➜  ~  systemd-analyze blame | head
         35.067s systemd-journald.service
         26.238s systemd-udev-settle.service
         21.336s dev-sda2.device
         13.086s systemd-udevd.service
          3.386s ModemManager.service
          3.322s SuSEfirewall2_init.service
          3.068s dev-disk-by\x2duuid-bfa3dd11\x2d86e3\x2d4f13\x2d93d5\x2d55f219a4baa0.swap
          2.962s systemd-fsck@dev-disk-by\x2duuid-13723ccf\x2d5934\x2d4fb4\x2db40a\x2dbc3a0a01ce1d.service
          2.442s usr-local.mount
          2.180s wpa_supplicant.service

I might reinstall the system using ext4 filesystem, that would probably solve some issues. The sda2 device is BrtFS.

As you can see, systemd-journald takes alot of the boot process and i found some errors in journalctl:


org.freedesktop.thumbnails.Cache1[1290]: (tumblerd:1564): tumblerd-WARNING **: Failed to start the thumbnail cache service: Another
gnomesu-pam-backend[2205]: The gnome keyring socket is not owned with the same credentials as the user login: /run/user/1000/keyrin
gnomesu-pam-backend[2205]: gkr-pam: couldn't unlock the login keyring.



org.gnome.OnlineAccounts[5586]: goa-daemon-Message: goa-daemon version 3.14.1 starting
org.gnome.OnlineAccounts[5586]: (goa-daemon:5766): goa-daemon-CRITICAL **: Error preparing AM: The name org.freedesktop.Telepathy.A
org.gtk.Private.AfcVolumeMonitor[5586]: Volume monitor alive
org.freedesktop.thumbnails.Cache1[5586]: (tumblerd:5779): tumblerd-WARNING **: Failed to start the thumbnail cache service: Another
gnomesu-pam-backend[5855]: The gnome keyring socket is not owned with the same credentials as the user login: /run/user/1000/keyrin
gnomesu-pam-backend[5855]: gkr-pam: couldn't unlock the login keyring.
gnomesu-pam-backend[5855]: pam_unix(gnomesu-pam:session): session opened for user root by (uid=1000)
gnomesu-pam-backend[5930]: The gnome keyring socket is not owned with the same credentials as the user login: /run/user/1000/keyrin
gnomesu-pam-backend[5930]: gkr-pam: couldn't unlock the login keyring.
gnomesu-pam-backend[5930]: pam_unix(gnomesu-pam:session): session opened for user root by (uid=1000)
org.freedesktop.Notifications[5586]: Failed to create secure directory (/run/user/1000/pulse): Åtkomst nekas(access denied)

Any suggestions that could help me would be appreciated

2

in /etc/systemd/journald.conf, try setting

SystemMaxFileSize=10M

3

Or delete /var/log/journal/ to disable the on-disk journal completely. (journalctl will still work, but the messages will be lost on reboot)
You should then install rsyslog to have at least the old text file logs.

But your actual problem is not journald I think. Something seems to be wrong on your system, according to your posted messages.
Probably caused by the systemd update to 219?

4

On Mon, 30 Mar 2015 22:36:01 GMT wolfi323 wrote:

> Or delete /var/log/journal/ to disable the on-disk journal completely.
> (journalctl will still work, but the messages will be lost on reboot)
> You should then install rsyslog to have at least the old text file
> logs.

Another option could be to use ‘Storage=volatile’
in /etc/systemd/journald.conf and after the next reboot to delete the
content of /var/log/journal.

5

Hi,
this:

 systemd-analyze critical-chain

shows a little more sophisticated, what’s the problem.
It reduces the list produced by “blame” to the relevant pieces.

Hendrik