Leap takes way too long to load vs 13.2

English Install/Boot/Login
1

Hello

I am trying to figure out why my pc since upgrading to leap is taking way longer to boot.
I am using a ssd, and 13.2 booted in about 10 seconds total (grub/bios/kde).
Leap is taking about a minute to boot 32 seconds just for the OS
Any help is appreciated


Kilbert@linux-oaak:~> systemd-analyze time
Startup finished in 8.954s (kernel) + 1.848s (initrd) + 21.139s (userspace) = 31.942s

Kilbert@linux-oaak:~> systemd-analyze blame
         18.287s wicked.service
           998ms display-manager.service
           631ms Movies.mount
           426ms ModemManager.service
           417ms Data3tb.mount
           417ms TVShows2.mount
           414ms systemd-fsck@dev-disk-by\x2dlabel-TVShows2.service
           401ms postfix.service
           398ms systemd-fsck@dev-disk-by\x2dlabel-Data3tb.service
           376ms udisks2.service
           362ms systemd-fsck@dev-disk-by\x2dlabel-Data2.service
           362ms SuSEfirewall2_init.service
           341ms apparmor.service
           285ms SuSEfirewall2.service
           263ms systemd-fsck@dev-disk-by\x2dlabel-Movies.service
           234ms dev-sdc2.device
           215ms Data2.mount
           192ms systemd-vconsole-setup.service
           185ms systemd-fsck@dev-disk-by\x2dlabel-TVCompleted.service
           159ms systemd-fsck@dev-disk-by\x2dlabel-Videos.service
           158ms systemd-fsck@dev-disk-by\x2duuid-663bf4e5\x2db185\x2d46cc\x2d82a5\x2dccb5be50070d.service
           154ms systemd-fsck@dev-disk-by\x2dlabel-Documentaries.service
           150ms systemd-fsck@dev-disk-by\x2duuid-9a705170\x2dd848\x2d40cd\x2dbdff\x2de77b628450d3.service
           145ms systemd-fsck@dev-disk-by\x2dlabel-TVShows.service
           109ms systemd-tmpfiles-clean.service
           106ms Videos.mount
            94ms Documentaries.mount
            94ms TVShows.mount
            86ms Data.mount
            55ms systemd-fsck-root.service
            52ms systemd-tmpfiles-setup-dev.service
            51ms ntpd.service
            50ms TVCompleted.mount
            42ms dev-hugepages.mount
            42ms dev-mqueue.mount
            41ms systemd-tmpfiles-setup.service
            41ms sys-kernel-debug.mount
            40ms home.mount
            37ms systemd-journald.service
            34ms systemd-modules-load.service
            31ms plymouth-read-write.service
            27ms systemd-update-utmp-runlevel.service
            27ms systemd-udev-trigger.service
            26ms kmod-static-nodes.service
            25ms user@1000.service
            22ms avahi-daemon.service
            22ms rtkit-daemon.service
            20ms polkit.service
            19ms wickedd-dhcp6.service
            18ms systemd-readahead-collect.service
            16ms systemd-user-sessions.service
            16ms systemd-remount-fs.service
            16ms wpa_supplicant.service
            16ms wickedd-auto4.service
            15ms plexmediaserver.service
            14ms plymouth-start.service
            13ms wickedd-dhcp4.service
            13ms dev-disk-by\x2duuid-57b954a9\x2ddbcc\x2d4bbf\x2db0e4\x2dc6e33f15a601.swap
            13ms nscd.service
            11ms systemd-readahead-replay.service
            11ms rc-local.service
            11ms bluetooth.service
            11ms alsa-restore.service
            11ms systemd-udev-root-symlink.service
             8ms systemd-sysctl.service
             7ms upower.service
             5ms iscsi.service
             5ms sys-fs-fuse-connections.mount
             4ms systemd-logind.service
             4ms systemd-random-seed.service
             4ms systemd-journal-flush.service
             3ms systemd-readahead-done.service
             3ms systemd-update-utmp.service
             3ms wickedd-nanny.service
             2ms wickedd.service
             2ms auditd.service
             1ms systemd-udevd.service



Kilbert@linux-oaak:~> 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 @21.111s
└─multi-user.target @21.111s
  └─cron.service @21.110s
    └─postfix.service @20.708s +401ms
      └─network.target @20.707s
        └─wicked.service @2.420s +18.287s
          └─wickedd-nanny.service @2.416s +3ms
            └─wickedd.service @2.412s +2ms
              └─wickedd-auto4.service @2.394s +16ms
                └─SuSEfirewall2_init.service @2.023s +362ms
                  └─basic.target @1.928s
                    └─timers.target @1.928s
                      └─systemd-tmpfiles-clean.timer @1.928s
                        └─sysinit.target @1.927s
                          └─sys-fs-fuse-connections.mount @6.259s +5ms
                            └─systemd-modules-load.service @234ms +34ms
                              └─systemd-readahead-replay.service @219ms +11ms
                                └─system.slice
                                  └─-.slice
Kilbert@linux-oaak:~>
2

Hi,
Try shifting to network manager
Your wicked takes too long.
My networkmanager here takes only 171ms.

Even here wicked takes too long almost same as yours.
Trick is before you switch to networkmanager
while in yast2-system-network settings change your connection
to hotplug rather than at boot time save it and open the network settings again and
switch it to networkmanager.

Do you really need the modemmanager.service?

3

Maay thanks, while not as fast as my 13.3 install, this is at least now workable!

enabled network manager in yast, rebooted:


Kilbert@linux-oaak:~> systemd-analyze time
Startup finished in 8.938s (kernel) + 1.645s (initrd) + 2.289s (userspace) = 12.873s

No, I don’t even have a modem installed on the pc, I have broadband. This is all new territory, how do I disable?

thanskagain
JOhn Kilbert

4

Go to yast2-system-services manager

5

I noted last October that the (openSUSE 13.2) wicked systemd service needs about 16.8 seconds at boot time.
The wicked DHCP4 and DHCP6 systemd services need only about 4 ms to 8 ms before the wicked systemd service is started.
I also noted that if the wicked systemd service is restarted after the initial boot completes it needs only about 7 seconds.
I also noted that on a 13.2 laptop Network Manager needs about 25 seconds at boot time (no Ethernet cable - WLAN activated by user login);Leap resolved the issue: Network Manager now needs only about 50 ms at laptop boot time.

[HR][/HR]Enabling wicked or Network Manager - systemd:
IMHO one has to be careful to choose either one or the other.
As noted in October last year, if wicked is chosen then (to avoid some annoying dependency messages in the journal’s boot entries) the following unit files need to be not only disabled but masked:


# systemctl list-unit-files
UNIT FILE                               STATE
.
NetworkManager-dispatcher.service       masked
NetworkManager-wait-online.service      masked
NetworkManager.service                  masked
.
#

Please note that other network services need to remain enabled:


UNIT FILE                               STATE
dbus-org.opensuse.Network.AUTO4.service enabled
dbus-org.opensuse.Network.DHCP4.service enabled
dbus-org.opensuse.Network.DHCP6.service enabled
dbus-org.opensuse.Network.Nanny.service enabled
network.service                         enabled
network-online.target                   static
network-pre.target                      static
network.target                          static

And the other way around, if the Network Manager service is enabled then, the following wicked services have to be at least disabled if not masked (on this 13.2 machine they are enabled ;))


UNIT FILE                               STATE
wicked.service                          enabled
wickedd-auto4.service                   enabled
wickedd-dhcp4.service                   enabled
wickedd-dhcp6.service                   enabled
wickedd-nanny.service                   enabled
wickedd.service                         enabled

[HR][/HR]@kilbert:
The systemd services are enabled/disabled - managed - by means of the “systemctl” command (root CLI)


# systemctl enable NetworkManager.service
# systemctl disable wickedd.service
# systemctl mask wickedd.service
# systemctl restart NetworkManager.service
# systemctl status NetworkManager.service

On doesn’t need to type everything: <Tab> will cause the bash prompt will auto-complete each portion of the command or list all the possible command variations if insufficient characters have been typed.