You are not logged in.
Hi everybody,
first post here, so any advice is welcome.
Now, I was doing some mainteinance, when I noticed the systemd-journald service slows down my boot up process.
systemd-analyze gives the following output
Startup finished in 2.037s (firmware) + 3.335s (loader) + 3.182s (kernel) + 12.278s (userspace) = 20.833s
And when I add blame it says:
7.169s systemd-journald.service
3.271s dev-sda2.device
1.998s systemd-fsck@dev-disk-by\x2duuid-a9d5e94b\x2dd4e5\x2d4e50\x2d8207\x2df18824abb475.service
1.649s netctl-auto@wlp2s0.service
1.349s boot.mount
871ms tmp.mount
754ms systemd-tmpfiles-setup-dev.service
590ms systemd-journal-flush.service
588ms systemd-udevd.service
571ms fcron.service
518ms systemd-tmpfiles-setup.service
501ms bluetooth.service
414ms dev-sda4.swap
378ms polkit.service
352ms systemd-backlight@backlight:intel_backlight.service
350ms systemd-modules-load.service
336ms systemd-backlight@leds:dell::kbd_backlight.service
317ms home.mount
312ms systemd-rfkill.service
196ms systemd-udev-trigger.service
140ms systemd-random-seed.service
108ms alsa-restore.service
105ms dev-mqueue.mount
104ms dev-hugepages.mount
92ms user@1000.service
83ms systemd-vconsole-setup.service
78ms systemd-remount-fs.service
70ms systemd-logind.service
68ms systemd-sysctl.service
58ms kmod-static-nodes.service
51ms sys-kernel-debug.mount
51ms systemd-update-utmp.service
42ms rtkit-daemon.service
27ms systemd-user-sessions.service
1ms sys-kernel-config.mount
I was curious and went to see some typical values of time for the incriminated service, and it turned out it normally is of a few tens of milliseconds.
So, I vacuumed my journal to make it less than 100M and set up a limit of size. I also ran verify and nuked a journal file which turned out to be corrupted.
Still, the time value when booting did not change appreciably. Do you guys have any other ideas on what to try or the possible cause of this?
When I read journalctl -b to see what is going on at boot the only entries relative to systemd-journald are
Sep 18 18:10:49 caprica systemd-journald[208]: Runtime journal (/run/log/journal/) is 8.0M, max 392.2M, 384.2M free.
Sep 18 18:10:49 caprica systemd-journald[208]: System journal (/var/log/journal/) is 88.0M, max 100.0M, 11.9M free.
Sep 18 18:10:50 caprica systemd-journald[208]: Time spent on flushing to /var is 897.448ms for 2 entries.
Also, how can I reduce the time relative to userspace?
Thank you all in advance!
Last edited by chftyrol (2016-09-18 16:33:06)
Offline
Not a Sysadmin issue, moving to NC...
Offline
My guess is your journal grew too big. Limiting the maximum size might help: https://wiki.archlinux.org/index.php/sy … size_limit
Offline
Thank you for your reply, but I actually already tried that. I have a maximum size of 100M now.
Offline