[systemd-devel] Strange output of `systemd-analyze critical-chain`
Michael Biebl
mbiebl at gmail.com
Tue Nov 15 21:50:50 UTC 2016
systemd-analyze and systemd-analyze critical-chain output can be
misleading sometimes.
Would it be possible for you to install systemd-bootchart.
This will give you a much better picture of which process uses IO/CPU
ressources.
2016-11-15 21:40 GMT+01:00 Paul Menzel <paulepanter at users.sourceforge.net>:
> Dear systemd folks,
>
>
> I am using systemd 232-3 from Debian sid/unstable.
>
> ```
> $ systemd --version
> systemd 232
> +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDNar systemd folks,
> ```
>
> On the underpowered ASRock E350M1, startup is quite slow.
>
> The output of `systemd-analyze blame` also looks quite strange.
>
> ```
> $ systemd-analyze critical-chain
> The time after the unit is active or started is printed after the "@" character.
> The time the unit takes to start is printed after the "+" character.
>
> graphical.target @3min 6.269s
> └─acct.service @6min 32.163s +55ms
> └─basic.target @1min 29.644s
> └─paths.target @1min 29.639s
> └─cups.path @1min 29.634s
> └─sysinit.target @1min 29.554s
> └─systemd-timesyncd.service @1min 29.275s +263ms
> └─systemd-tmpfiles-setup.service @1min 28.575s +620ms
> └─systemd-journal-flush.service @13.493s +1min 15.054s
> └─var.mount @12.408s +1.057s
> └─systemd-fsck at dev-map\x2dvar.service @12.377s +17ms
> └─dev-mapper-speicher\x2dvar.device @12.205s
> ```
>
> It jumps from 1:30 to 6:32 minutes but the difference is shown as 55
> ms.
>
> As written, the systemd is quite underpowered. Might that be the
> reason?
>
> Here is the output of `systemd-analyze blame`.
>
> ```
> 5min 39.610s apt-daily.service
> 1min 21.012s tor at default.service
> 1min 15.054s systemd-journal-flush.service
> 1min 9.497s NetworkManager-wait-online.service
> 53.514s libvirt-guests.service
> 20.218s libvirtd.service
> 16.227s timidity.service
> 15.682s accounts-daemon.service
> 12.913s NetworkManager.service
> 12.889s vdr.service
> 11.915s apache2.service
> 11.143s ModemManager.service
> 10.434s dev-mapper-speicher\x2dusr.device
> 10.349s lirc.service
> 9.904s dev-mapper-speicher\x2droot.device
> 8.397s irqbalance.service
> 7.531s exim4.service
> 7.164s srv-bilder.mount
> 6.602s tor.service
> 6.568s lm-sensors.service
> 6.542s klogd.service
> 6.539s restorecond.service
> 6.518s rsyslog.service
> 6.509s pppd-dns.service
> 6.241s minissdpd.service
> 5.343s colord.service
> 4.982s ebtables.service
> 4.702s kdump-tools.service
> 4.631s polkit.service
> 4.620s rc-local.service
> 3.853s srv-filme.mount
> 3.302s binfmt-support.service
> 3.235s networking.service
> 3.157s lvm2-monitor.service
> 3.063s ssh.service
> 2.732s keyboard-setup.service
> 2.281s boot.mount
> 2.151s systemd-tmpfiles-setup-dev.service
> 1.915s gdm.service
> 1.857s systemd-tmpfiles-clean.service
> 1.788s console-setup.service
> 1.687s dev-mapper-speicher\x2dswap.swap
> 1.681s systemd-cryptsetup at md1_crypt.service
> 1.603s home.mount
> 1.270s iio-sensor-proxy.service
> 1.258s systemd-sysctl.service
> 1.063s systemd-random-seed.service
> 1.058s systemd-udevd.service
> 1.057s var.mount
> 1.049s speech-dispatcher.service
> 1.031s udhcpd.service
> […]
> ```
>
> Do you know what is going on?
>
>
> Thanks,
>
> Paul
> _______________________________________________
> systemd-devel mailing list
> systemd-devel at lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/systemd-devel
>
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
More information about the systemd-devel
mailing list