Page 1 of 6 123 ... LastLast
Results 1 to 10 of 52

Thread: Opensuse Boot Time

  1. #1

    Question Opensuse Boot Time

    Hi everyone, i was wondering if is normal my boot time take so long.

    Here the result of systemd-analyze blame

    Code:
         1min 6.308s ModemManager.service
         1min 4.279s avahi-daemon.service
         1min 4.266s nscd.service
         1min 1.653s SuSEfirewall2_init.service
              3.858s vboxadd-x11.service
              3.455s NetworkManager.service
              2.933s vboxadd.service
              2.625s alsa-restore.service
              2.617s wpa_supplicant.service
              2.545s rc-local.service
              2.202s postfix.service
              1.968s SuSEfirewall2.service
              1.773s polkit.service
              1.473s boot-grub2-i386\x2dpc.mount
              1.433s display-manager.service
              1.411s boot-grub2-x86_64\x2defi.mount
              1.072s lvm2-activation.service
               928ms systemd-udev-settle.service
               927ms vboxdrv.service
               885ms \x2esnapshots.mount
               866ms lvm2-activation-net.service
               821ms var-lib-mailman.mount
               819ms var-lib-pgsql.mount
               792ms lvm2-activation-early.service
               782ms var-crash.mount
               776ms sys-kernel-debug.mount
               775ms dev-mqueue.mount
               774ms dev-hugepages.mount
               769ms var-lib-named.mount
               765ms systemd-journald.service
               727ms systemd-tmpfiles-setup-dev.service
               722ms tmp.mount
               682ms dev-disk-by\x2duuid-a33a3a13\x2d6000\x2d49be\x2da99b\x2d295905819ee4.s
               678ms var-log.mount
               637ms srv.mount
               608ms systemd-tmpfiles-setup.service
               525ms boot-efi.mount
               516ms systemd-udev-trigger.service
               512ms systemd-fsck@dev-disk-by\x2duuid-8a52fc06\x2d4e19\x2d4832\x2d87d0\x2dc
               508ms systemd-udev-root-symlink.service
               469ms systemd-backlight@backlight:intel_backlight.service
               463ms plymouth-read-write.service
               431ms systemd-remount-fs.service
               342ms cycle.service
               317ms home.mount
               315ms rtkit-daemon.service
               302ms apparmor.service
               278ms var-spool.mount
               257ms var-tmp.mount
               220ms usr-local.mount
               216ms udisks2.service
               210ms systemd-sysctl.service
               185ms opt.mount
               168ms var-opt.mount
               160ms systemd-udevd.service
               149ms systemd-user-sessions.service
               107ms systemd-modules-load.service
                83ms user@1000.service
                77ms systemd-rfkill@rfkill0.service
                64ms systemd-update-utmp.service
                64ms systemd-readahead-replay.service
                63ms iscsi.service
                62ms upower.service
                41ms bluetooth.service
                32ms plymouth-start.service
                26ms systemd-logind.service
                25ms systemd-readahead-collect.service
                24ms auditd.service
                16ms systemd-random-seed.service
                15ms systemd-readahead-done.service
                 8ms systemd-vconsole-setup.service
                 5ms systemd-journal-flush.service
                 5ms kmod-static-nodes.service
                 4ms systemd-update-utmp-runlevel.service
    If not normal, what i can do for speed up my boot time?

    Thanks in advance.

  2. #2
    Join Date
    Nov 2009
    Location
    West Virginia Sector 13
    Posts
    15,743

    Default Re: Opensuse Boot Time

    Aree you connecting by mobil broadband?? Looks like it is just slow connecting.

  3. #3

    Default Re: Opensuse Boot Time

    Hi gogalthorp,
    Thanks for reply, and no, i'm not connecting to mobil broadband, i'm using my wifi connection normally. But you gave me a clue for what is happening. I'll try look in nertwork.service.

  4. #4

    Default Re: Opensuse Boot Time

    I disable the ModemManager.service in the hope to get a better time boot. Sadly, don't get better. I run systemd-analyze critical-chain, here's the result:
    Code:
    graphical.target @1min 41.994s
    └─multi-user.target @1min 41.994s
      └─cron.service @1min 41.994s
        └─postfix.service @1min 38.865s +3.127s
          └─network.target @1min 38.863s
            └─NetworkManager.service @1min 34.784s +4.079s
              └─SuSEfirewall2_init.service @18.352s +1min 16.430s
                └─basic.target @18.331s
                  └─timers.target @18.331s
                    └─systemd-tmpfiles-clean.timer @18.331s
                      └─sysinit.target @18.331s
                        └─systemd-journald.service @1min 35.966s +276ms
                          └─system.slice
                            └─-.slice
    Apparently, the Susefirewall is too slow to init. How i can fix this? Any clues?

  5. #5

    Default Re: Opensuse Boot Time

    Hi,
    Look like your machine is loading a lot of stuffs during boot.
    Maybe it might help for expert member in this area if you could describe
    to what do you use your mcahine for, in order that they can advice you on what service you
    can disable or maybe mask to avoid the long boot time.
    People who do not break things first will never learn to create anything

  6. #6

    Default Re: Opensuse Boot Time

    Hi conram, thanks for the reply. I use my laptop for work and study, mostly. I have a normal use of my machine. I'll be very grateful if someone give a clue, i'm new a user of opensuse and linux in general, have my learning curve yet. Thanks again for the help.

  7. #7

    Default Re: Opensuse Boot Time

    Quote Originally Posted by marcusvcl View Post
    Hi conram, thanks for the reply. I use my laptop for work and study, mostly. I have a normal use of my machine. I'll be very grateful if someone give a clue, i'm new a user of opensuse and linux in general, have my learning curve yet. Thanks again for the help.
    Did you change someting in the Services Manager?
    Code:
    multi-user.target @1min 41.994s
    If I look at mine shows like this
    Code:
    graphical.target @6.494s
    └─display-manager.service @5.837s +656ms
      └─systemd-user-sessions.service @5.811s +20ms
        └─basic.target @5.809s
          └─timers.target @5.809s
            └─systemd-tmpfiles-clean.timer @5.809s
              └─sysinit.target @5.809s
                └─apparmor.service @4.234s +1.574s
                  └─systemd-tmpfiles-setup.service @4.174s +59ms
                    └─local-fs.target @4.173s
                      └─var-run.mount @4.155s +16ms
                        └─var.mount @4.129s +10ms
                          └─systemd-fsck@dev-disk-by\x2duuid-6df39845\x2d32ae\x2d443e\x2d9c9d\x2d83bff7d
                            └─dev-disk-by\x2duuid-6df39845\x2d32ae\x2d443e\x2d9c9d\x2d83bff7dcf019.devic
    Code:
    systemd-analyze blame
              1.574s apparmor.service
               656ms display-manager.service
               254ms systemd-random-seed.service
               239ms SuSEfirewall2.service
               159ms systemd-rfkill@rfkill0.service
               132ms systemd-update-utmp.service
               126ms ntpd.service
               113ms systemd-rfkill@rfkill1.service
               112ms systemd-fsck@dev-disk-by\x2duuid-439d9e34\x2d415a\x2d4dd1\x2d89
               103ms systemd-fsck@dev-disk-by\x2duuid-6df39845\x2d32ae\x2d443e\x2d9c
                84ms systemd-tmpfiles-clean.service
                79ms SuSEfirewall2_init.service
                78ms NetworkManager.service
                59ms systemd-tmpfiles-setup.service
                56ms systemd-fsck@dev-disk-by\x2duuid-b0dd3ffd\x2d541a\x2d463f\x2d90
                50ms systemd-vconsole-setup.service
                45ms boot-efi.mount
                45ms udisks2.service
                37ms dev-disk-by\x2duuid-eb60395c\x2d09a4\x2d47b5\x2dbc23\x2d6a854db
                37ms systemd-tmpfiles-setup-dev.service
                34ms autofs.service
                27ms systemd-udev-root-symlink.service
                23ms systemd-fsck-root.service
    People who do not break things first will never learn to create anything

  8. #8

    Default Re: Opensuse Boot Time

    Quote Originally Posted by conram View Post
    Did you change someting in the Services Manager?
    No, but when i access the YaST. It said that the network is managed by NetworkManager and the YaST nothing can do. The only thing that i changed was my computer name. I read somewhere about wicked or ifup but haven't tried none of this. I tried disable my firewall to see if my boot time was affected, but i was wrong about the problem again.

    Edit: And, yes, my machine is loading more things that it should. Looking to you systemd-analyze blame is clear the difference. It's like my system is bloated. But i dont know why

  9. #9
    Join Date
    Feb 2009
    Location
    Spain
    Posts
    25,547

    Default Re: Opensuse Boot Time

    On 2014-12-10 14:56, marcusvcl wrote:
    >
    > I disable the ModemManager.service in the hope to get a better time
    > boot. Sadly, don't get better. I run systemd-analyze critical-chain,
    > here's the result:
    >
    > Code:
    > --------------------


    > └─SuSEfirewall2_init.service @18.352s +1min 16.430s
    >
    > --------------------


    It is not typical. The problem is there, clearly.

    > Apparently, the Susefirewall is too slow to init. How i can fix this?
    > Any clues?


    Dunno. We'd need to see in more detail what is happening during that
    firwall init.

    Have a read on the logs, see if something leaps to the eye...


    --
    Cheers / Saludos,

    Carlos E. R.
    (from 13.1 x86_64 "Bottle" at Telcontar)

  10. #10
    Join Date
    Feb 2009
    Location
    Spain
    Posts
    25,547

    Default Re: Opensuse Boot Time

    On 2014-12-11 02:46, marcusvcl wrote:

    > haven't tried none of this. I tried disable my firewall to see if my
    > boot time was affected, but i was wrong about the problem again.


    After each change, you have to run "systemd-analyze critical-chain". The
    important figures are those after the "+" symbol. So if you disable the
    firewall on boot, you have to look again what component is now slow.

    --
    Cheers / Saludos,

    Carlos E. R.
    (from 13.1 x86_64 "Bottle" at Telcontar)

Page 1 of 6 123 ... LastLast

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •