You are not logged in.

Pages: 1

#1 2019-06-21 20:41:29

razaq
Member
Registered: 2019-06-21
Posts: 5

[SOLVED] Slow boot because of NetworkManager

Hello!

i installed wpa_supplicant to get networking setup and installed NetworkManager after. So now I have both (I tried removing wpa_supplicant, but that breaks networking all together...). Currently networking (ethernet and wifi) works fine.

However the problem is a very long time at boot where nothing happens.

Here is the output from journalctl -b:

Jun 21 18:54:11 hostname systemd[1]: systemd-rfkill.service: Succeeded.
Jun 21 18:54:11 hostname audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-rfkill comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Jun 21 18:54:11 hostname kernel: kauditd_printk_skb: 10 callbacks suppressed
Jun 21 18:54:11 hostname kernel: audit: type=1131 audit(1561136051.752:24): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-rfkill comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Jun 21 18:54:14 hostname dbus-daemon[319]: [system] Activating via systemd: service name='org.freedesktop.resolve1' unit='dbus-org.freedesktop.resolve1.service' requested by ':1.1' (uid=0 pid=320 comm="/usr/bin/NetworkManager --no-daemon ")
Jun 21 18:54:14 hostname dbus-daemon[319]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.resolve1.service': Unit dbus-org.freedesktop.resolve1.service not found.
Jun 21 18:54:14 hostname dbus-daemon[319]: [system] Activating via systemd: service name='org.freedesktop.resolve1' unit='dbus-org.freedesktop.resolve1.service' requested by ':1.1' (uid=0 pid=320 comm="/usr/bin/NetworkManager --no-daemon ")
Jun 21 18:54:14 hostname dbus-daemon[319]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.resolve1.service': Unit dbus-org.freedesktop.resolve1.service not found.
Jun 21 18:54:18 hostname systemd[1]: NetworkManager-dispatcher.service: Succeeded.
Jun 21 18:54:18 hostname audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Jun 21 18:54:18 hostname kernel: audit: type=1131 audit(1561136058.352:25): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Jun 21 18:54:22 hostname dbus-daemon[319]: [system] Activating via systemd: service name='org.freedesktop.resolve1' unit='dbus-org.freedesktop.resolve1.service' requested by ':1.1' (uid=0 pid=320 comm="/usr/bin/NetworkManager --no-daemon ")
Jun 21 18:54:22 hostname dbus-daemon[319]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.resolve1.service': Unit dbus-org.freedesktop.resolve1.service not found.
Jun 21 18:54:22 hostname dbus-daemon[319]: [system] Activating via systemd: service name='org.freedesktop.resolve1' unit='dbus-org.freedesktop.resolve1.service' requested by ':1.1' (uid=0 pid=320 comm="/usr/bin/NetworkManager --no-daemon ")
Jun 21 18:54:22 hostname dbus-daemon[319]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.resolve1.service': Unit dbus-org.freedesktop.resolve1.service not found.
Jun 21 18:54:33 hostname NetworkManager[320]: <error> [1561136073.4223] sup-iface[0x55c43e5cd030,wlp5s0]: error adding interface: Timeout was reached
Jun 21 18:54:33 hostname NetworkManager[320]: <info>  [1561136073.4224] device (wlp5s0): supplicant interface state: starting -> down
Jun 21 18:54:33 hostname NetworkManager[320]: <info>  [1561136073.4226] manager: startup complete
Jun 21 18:54:38 hostname systemd[1]: systemd-hostnamed.service: Succeeded.
Jun 21 18:54:37 hostname audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-hostnamed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Jun 21 18:54:38 hostname kernel: audit: type=1131 audit(1561136077.992:26): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-hostnamed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Jun 21 18:54:38 hostname dbus-daemon[319]: [system] Activating via systemd: service name='org.freedesktop.resolve1' unit='dbus-org.freedesktop.resolve1.service' requested by ':1.1' (uid=0 pid=320 comm="/usr/bin/NetworkManager --no-daemon ")
Jun 21 18:54:38 hostname dbus-daemon[319]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.resolve1.service': Unit dbus-org.freedesktop.resolve1.service not found.
Jun 21 18:54:38 hostname dbus-daemon[319]: [system] Activating via systemd: service name='org.freedesktop.resolve1' unit='dbus-org.freedesktop.resolve1.service' requested by ':1.1' (uid=0 pid=320 comm="/usr/bin/NetworkManager --no-daemon ")
Jun 21 18:54:38 hostname dbus-daemon[319]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.resolve1.service': Unit dbus-org.freedesktop.resolve1.service not found.
Jun 21 18:54:43 hostname NetworkManager[320]: <warn>  [1561136083.3557] device (wlp5s0): re-acquiring supplicant interface (#1).
Jun 21 18:55:08 hostname NetworkManager[320]: <error> [1561136108.3824] sup-iface[0x55c43e5cd110,wlp5s0]: error adding interface: Timeout was reached
Jun 21 18:55:08 hostname NetworkManager[320]: <info>  [1561136108.3825] device (wlp5s0): supplicant interface state: starting -> down
Jun 21 18:55:10 hostname dbus-daemon[319]: [system] Activating via systemd: service name='org.freedesktop.resolve1' unit='dbus-org.freedesktop.resolve1.service' requested by ':1.1' (uid=0 pid=320 comm="/usr/bin/NetworkManager --no-daemon ")
Jun 21 18:55:10 hostname dbus-daemon[319]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.resolve1.service': Unit dbus-org.freedesktop.resolve1.service not found.
Jun 21 18:55:10 hostname dbus-daemon[319]: [system] Activating via systemd: service name='org.freedesktop.resolve1' unit='dbus-org.freedesktop.resolve1.service' requested by ':1.1' (uid=0 pid=320 comm="/usr/bin/NetworkManager --no-daemon ")
Jun 21 18:55:10 hostname dbus-daemon[319]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.resolve1.service': Unit dbus-org.freedesktop.resolve1.service not found.
Jun 21 18:55:18 hostname NetworkManager[320]: <warn>  [1561136118.3587] device (wlp5s0): re-acquiring supplicant interface (#2).
Jun 21 18:55:43 hostname NetworkManager[320]: <error> [1561136143.3854] sup-iface[0x55c43e5cd1f0,wlp5s0]: error adding interface: Timeout was reached
Jun 21 18:55:43 hostname NetworkManager[320]: <info>  [1561136143.3855] device (wlp5s0): supplicant interface state: starting -> down
Jun 21 18:55:53 hostname NetworkManager[320]: <warn>  [1561136153.3607] device (wlp5s0): re-acquiring supplicant interface (#3).
Jun 21 18:56:14 hostname dbus-daemon[319]: [system] Activating via systemd: service name='org.freedesktop.resolve1' unit='dbus-org.freedesktop.resolve1.service' requested by ':1.1' (uid=0 pid=320 comm="/usr/bin/NetworkManager --no-daemon ")
Jun 21 18:56:14 hostname dbus-daemon[319]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.resolve1.service': Unit dbus-org.freedesktop.resolve1.service not found.
Jun 21 18:56:14 hostname dbus-daemon[319]: [system] Activating via systemd: service name='org.freedesktop.resolve1' unit='dbus-org.freedesktop.resolve1.service' requested by ':1.1' (uid=0 pid=320 comm="/usr/bin/NetworkManager --no-daemon ")
Jun 21 18:56:14 hostname dbus-daemon[319]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.resolve1.service': Unit dbus-org.freedesktop.resolve1.service not found.
Jun 21 18:56:18 hostname NetworkManager[320]: <error> [1561136178.3668] sup-iface[0x55c43e5cd2d0,wlp5s0]: error adding interface: Timeout was reached
Jun 21 18:56:18 hostname NetworkManager[320]: <info>  [1561136178.3669] device (wlp5s0): supplicant interface state: starting -> down
Jun 21 18:56:26 hostname kernel: random: crng init done
Jun 21 18:56:26 hostname kernel: random: 7 urandom warning(s) missed due to ratelimiting
Jun 21 18:56:26 hostname sddm[348]: Initializing...
Jun 21 18:56:26 hostname sddm[348]: Starting...

Im trying since about 4 hours to get this fixed, unfortunately there is nothing in the wiki and google doesnt help either.
Thanks for any replies...

Last edited by razaq (2019-06-22 09:21:07)

Offline

#2 2019-06-21 21:22:32

ewaller
Administrator
From: Pasadena, CA
Registered: 2009-07-13
Posts: 20,643

Re: [SOLVED] Slow boot because of NetworkManager

Welcome to Arch Linux.  Please post the output of
systemd-analyze blame
systemd-analyze critical-chain
and
find /etc/systemd/system/
Thanks

Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
The shortest way to ruin a country is to give power to demagogues.— Dionysius of Halicarnassus
---
How to Ask Questions the Smart Way

Offline

#3 2019-06-21 21:52:32

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 76,104

Re: [SOLVED] Slow boot because of NetworkManager

Jun 21 18:56:26 hostname kernel: random: crng init done

https://wiki.archlinux.org/index.php/Haveged
https://bbs.archlinux.org/viewtopic.php?id=244874

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#4 2019-06-21 22:34:16

razaq
Member
Registered: 2019-06-21
Posts: 5

Re: [SOLVED] Slow boot because of NetworkManager

seth wrote:

im on the lts kernel

uname -a
Linux hostname 4.19.53-1-lts #1 SMP Wed Jun 19 16:24:23 CEST 2019 x86_64 GNU/Linux

so

lscpu | grep -i rdrand

unfortunately returns nothing

Offline

#5 2019-06-21 22:39:10

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 76,104

Re: [SOLVED] Slow boot because of NetworkManager

Install & enable haveged

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#6 2019-06-21 22:46:10

razaq
Member
Registered: 2019-06-21
Posts: 5

Re: [SOLVED] Slow boot because of NetworkManager

ewaller wrote:

Welcome to Arch Linux.  Please post the output of
systemd-analyze blame
systemd-analyze critical-chain
and
find /etc/systemd/system/
Thanks

$ systemd-analyze blame
    4min 26.185s man-db.service
          2.200s sshdgenkeys.service
          1.318s systemd-logind.service
          1.300s lvm2-monitor.service
           887ms dev-sda2.device
           514ms udisks2.service
           482ms upower.service
           422ms systemd-udevd.service
           368ms logrotate.service
           331ms systemd-journald.service
           320ms ldconfig.service
           230ms systemd-journal-flush.service
           195ms NetworkManager.service
           161ms systemd-fsck@dev-disk-by\x2duuid-c47f781b\x2d489b\x2d4c67\x2db21c\x2d16084d6efe15.service
           139ms polkit.service
            99ms systemd-rfkill.service
            91ms user@1000.service
            86ms systemd-udev-trigger.service
            62ms wpa_supplicant.service
            60ms systemd-journal-catalog-update.service
            58ms systemd-tmpfiles-setup.service
            53ms haveged.service
            45ms systemd-tmpfiles-clean.service
            38ms systemd-sysusers.service
            35ms systemd-update-utmp.service
            35ms sys-kernel-debug.mount
            32ms systemd-sysctl.service
            31ms home.mount
            31ms dev-mqueue.mount
            29ms dev-hugepages.mount
            25ms dev-disk-by\x2duuid-2f21830c\x2d3dee\x2d4dc5\x2da80f\x2d938648471a3f.swap
            23ms systemd-backlight@backlight:acpi_video0.service
            22ms systemd-remount-fs.service
            20ms user-runtime-dir@1000.service
            20ms tmp.mount
            19ms kmod-static-nodes.service
            17ms systemd-tmpfiles-setup-dev.service
            17ms systemd-random-seed.service
            14ms systemd-update-done.service
            13ms sys-kernel-config.mount
            12ms systemd-user-sessions.service
            10ms rtkit-daemon.service
             8ms proc-sys-fs-binfmt_misc.mount
$ systemd-analyze critical-chain
The time when unit became active or started is printed after the "@" character.
The time the unit took to start is printed after the "+" character.

graphical.target @3.466s
└─multi-user.target @3.465s
  └─systemd-logind.service @2.142s +1.318s
    └─basic.target @2.129s
      └─sockets.target @2.129s
        └─dbus.socket @2.128s
          └─sysinit.target @2.127s
            └─systemd-update-done.service @2.112s +14ms
              └─ldconfig.service @1.790s +320ms
                └─local-fs.target @1.782s
                  └─home.mount @1.751s +31ms
                    └─systemd-fsck@dev-disk-by\x2duuid-c47f781b\x2d489b\x2d4c67\x2db21c\x2d16084d6efe15.service @1.586s +161ms
                      └─local-fs-pre.target @1.584s
                        └─lvm2-monitor.service @283ms +1.300s
                          └─lvm2-lvmetad.service @321ms
                            └─systemd-journald.socket @282ms
                              └─-.mount @252ms
                                └─system.slice @252ms
                                  └─-.slice @252ms
$ find /etc/systemd/system
/etc/systemd/system
/etc/systemd/system/sysinit.target.wants
/etc/systemd/system/sysinit.target.wants/haveged.service
/etc/systemd/system/display-manager.service
/etc/systemd/system/dbus-fi.w1.wpa_supplicant1.service
/etc/systemd/system/getty.target.wants
/etc/systemd/system/getty.target.wants/getty@tty1.service
/etc/systemd/system/multi-user.target.wants
/etc/systemd/system/multi-user.target.wants/wpa_supplicant.service
/etc/systemd/system/multi-user.target.wants/remote-fs.target
/etc/systemd/system/multi-user.target.wants/NetworkManager.service
/etc/systemd/system/dbus-org.freedesktop.nm-dispatcher.service
/etc/systemd/system/network-online.target.wants
/etc/systemd/system/network-online.target.wants/NetworkManager-wait-online.service

Last edited by razaq (2019-06-21 22:49:07)

Offline

#7 2019-06-21 22:54:58

razaq
Member
Registered: 2019-06-21
Posts: 5

Re: [SOLVED] Slow boot because of NetworkManager

seth wrote:

Install & enable haveged

done, will reboot in a sec and try
thanks for the suggestion!

Last edited by razaq (2019-06-21 22:55:13)

Offline

#8 2019-06-21 23:04:05

razaq
Member
Registered: 2019-06-21
Posts: 5

Re: [SOLVED] Slow boot because of NetworkManager

seth wrote:

Install & enable haveged

wow! That really fixed it!
Thank you so much!

Offline

#9 2019-06-22 01:19:37

2ManyDogs
Forum Fellow
Registered: 2012-01-15
Posts: 4,648

Re: [SOLVED] Slow boot because of NetworkManager

Please remember to mark your thread [SOLVED] (edit the title of your first post).

Offline

Pages: 1

Board footer

Powered by FluxBB