Page 1 of 2 12 LastLast
Results 1 to 10 of 12

Thread: Tumbleweed Long Shutdown Time

  1. #1

    Default Tumbleweed Long Shutdown Time

    After the last update Tumbleweed now takes a long time to shutdown or reboot.

    Here is the output of systemd-analyze blame:

    # systemd-analyze blame
    1.419s btrfsmaintenance-refresh.service
    1.148s postfix.service
    932ms apparmor.service
    858ms SuSEfirewall2_init.service
    718ms display-manager.service
    616ms SuSEfirewall2.service
    441ms lvm2-monitor.service
    436ms var-spool.mount
    415ms var-lib-mailman.mount
    388ms var-lib-machines.mount
    378ms opt.mount
    373ms srv.mount
    361ms var-lib-pgsql.mount
    337ms usr-local.mount
    326ms var-opt.mount
    321ms plymouth-quit-wait.service
    313ms dev-sdb3.device
    311ms var-crash.mount
    304ms var-lib-named.mount
    258ms home-dave-NASMusic.mount
    257ms var-tmp.mount
    237ms initrd-switch-root.service

    What would cause
    btrfsmaintenance-refresh.service and postfix.service to take so long? What should I be looking for?

    Thanks!




  2. #2
    Join Date
    Sep 2013
    Location
    Norfolk, UK
    Posts
    2,033

    Default Re: Tumbleweed Long Shutdown Time

    If it's shutdown where the delay is then "systemd-analyze blame" is not going to tell you a great deal...

    Take a look here: https://freedesktop.org/wiki/Softwar...emd/Debugging/

    Specifically the "Diagnosing Shutdown Problems" section.
    Regards, Paul

  3. #3
    Join Date
    Mar 2011
    Location
    Sauerland
    Posts
    6,721

    Default AW: Tumbleweed Long Shutdown Time

    1.419s btrfsmaintenance-refresh.service
    1.148s postfix.service
    That is one (and a half) Second.......

  4. #4
    Join Date
    Jun 2008
    Location
    Groningen, Netherlands
    Posts
    20,925
    Blog Entries
    14

    Default Re: AW: Tumbleweed Long Shutdown Time

    Quote Originally Posted by Sauerland View Post
    That is one (and a half) Second.......
    Not even .....
    ° Appreciate my reply? Click the star and let me know why.

    ° Perfection is not gonna happen. No way.

    http://en.opensuse.org/User:Knurpht
    http://nl.opensuse.org/Gebruiker:Knurpht

  5. #5
    Join Date
    Jan 2014
    Location
    Erlangen
    Posts
    3,278

    Default Re: Tumbleweed Long Shutdown Time

    Quote Originally Posted by AmigaOS View Post
    After the last update Tumbleweed now takes a long time to shutdown or reboot.

    Here is the output of systemd-analyze blame:

    # systemd-analyze blame
    1.419s btrfsmaintenance-refresh.service
    1.148s postfix.service
    932ms apparmor.service
    858ms SuSEfirewall2_init.service
    718ms display-manager.service
    616ms SuSEfirewall2.service
    441ms lvm2-monitor.service
    436ms var-spool.mount
    415ms var-lib-mailman.mount
    388ms var-lib-machines.mount
    378ms opt.mount
    373ms srv.mount
    361ms var-lib-pgsql.mount
    337ms usr-local.mount
    326ms var-opt.mount
    321ms plymouth-quit-wait.service
    313ms dev-sdb3.device
    311ms var-crash.mount
    304ms var-lib-named.mount
    258ms home-dave-NASMusic.mount
    257ms var-tmp.mount
    237ms initrd-switch-root.service

    What would cause
    btrfsmaintenance-refresh.service and postfix.service to take so long? What should I be looking for?
    Startup finished in 1.740s (kernel) + 757ms (initrd) + 1.835s (userspace) = 4.333s on my Intel i3-4130.

    Look here: http://mistelberger.net/plot.svg postfix.service takes 728ms from 1,835ms user space. However it is not in the critical chain. So it does not matter. btrfsmaintenance-refresh.service was enabled on my machine. However there was no such partition. Thus I disabled the service.
    AMD Athlon 4850e (2009), openSUSE 13.1, KDE 4, Intel i3-4130 (2014), i7-6700K (2016), i5-8250U (2018), AMD Ryzen 5 3400G (2020), openSUSE Tumbleweed, KDE Plasma 5

  6. #6
    Join Date
    Sep 2013
    Location
    Norfolk, UK
    Posts
    2,033

    Default Re: Tumbleweed Long Shutdown Time

    Quote Originally Posted by karlmistelberger View Post
    Startup finished in 1.740s (kernel) + 757ms (initrd) + 1.835s (userspace) = 4.333s on my Intel i3-4130.
    Yes... but... the OP stated the problem is with shutdown/reboot, not startup, which as can be seen from the "systemd-analyze blame" posted, is quite respectable. Looking at startup times with "systemd-analyze *" is all rather moot.
    Regards, Paul

  7. #7
    Join Date
    Nov 2009
    Location
    West Virginia Sector 13
    Posts
    16,287

    Default Re: Tumbleweed Long Shutdown Time

    Depending what services or programs that are running shut down can be fast or slow. The OS must wait until all critical operations for all services and programs are complete

  8. #8
    Join Date
    Apr 2017
    Location
    Piemont
    Posts
    274

    Default Re: Tumbleweed Long Shutdown Time

    Have you added any new devices?
    Have you tried the previous Kernel?
    Try also to change loginmanager
    loyalty returns to those who practice it

  9. #9
    Join Date
    Jan 2014
    Location
    Erlangen
    Posts
    3,278

    Default Re: Tumbleweed Long Shutdown Time

    Quote Originally Posted by gogalthorp View Post
    Depending what services or programs that are running shut down can be fast or slow. The OS must wait until all critical operations for all services and programs are complete
    Shut down is lengthy:

    Code:
    hofkirchen:~ # journalctl -b -1 |grep -i slice|grep 13:49
    Jan 02 13:49:08 hofkirchen systemd[1]: Removed slice system-systemd\x2dcoredump.slice.
    Jan 02 13:49:08 hofkirchen systemd[1]: Removed slice system-systemd\x2dhibernate\x2dresume.slice.
    Jan 02 13:49:09 hofkirchen systemd[1]: Removed slice system-getty.slice.
    Jan 02 13:49:09 hofkirchen systemd[1]: Removed slice User Slice of charlemagne.
    Jan 02 13:49:10 hofkirchen systemd[1]: Removed slice User Slice of erika.
    Jan 02 13:49:11 hofkirchen systemd[1]: Removed slice User Slice of karl.
    Jan 02 13:49:16 hofkirchen systemd[1]: Stopped target Slices.
    Jan 02 13:49:16 hofkirchen systemd[1]: Removed slice User and Session Slice.
    Jan 02 13:49:16 hofkirchen systemd[1]: Removed slice system-systemd\x2dbacklight.slice.
    Jan 02 13:49:17 hofkirchen systemd[1]: Removed slice system-systemd\x2dfsck.slice.
    hofkirchen:~ #
    Removing a graphical login takes a second each.

    Code:
    hofkirchen:~ # journalctl -b -1 -u wicked
    -- Logs begin at Tue 2016-10-25 15:09:12 CEST, end at Wed 2018-01-03 06:08:03 CET. --
    Dec 31 15:38:47 hofkirchen systemd[1]: Starting wicked managed network interfaces...
    Dec 31 15:39:02 hofkirchen wicked[855]: lo              up
    Dec 31 15:39:02 hofkirchen wicked[855]: enp0s25         enslaved
    Dec 31 15:39:02 hofkirchen wicked[855]: br0             up
    Dec 31 15:39:02 hofkirchen systemd[1]: Started wicked managed network interfaces.
    Jan 02 13:49:11 hofkirchen systemd[1]: Stopping wicked managed network interfaces...
    Jan 02 13:49:16 hofkirchen wicked[23090]: enp0s25         device-ready
    Jan 02 13:49:16 hofkirchen systemd[1]: Stopped wicked managed network interfaces.
    hofkirchen:~ #
    Starting wicked takes 15 seconds, stopping another 5 seconds.
    AMD Athlon 4850e (2009), openSUSE 13.1, KDE 4, Intel i3-4130 (2014), i7-6700K (2016), i5-8250U (2018), AMD Ryzen 5 3400G (2020), openSUSE Tumbleweed, KDE Plasma 5

  10. #10
    Join Date
    Jun 2008
    Location
    USA
    Posts
    1,447

    Default Re: Tumbleweed Long Shutdown Time

    I have the opposite problem. I looked at systemd analyze and found it was just over 3 minutes in userspace. I just upgraded from LEAP 42.2. I have a dual boot and run LEAP 42.3 on another disk. That loads up extremely fast. What could be slowing this upgrade down?
    Any sufficiently advanced technology is indistinguishable from magic. - Arthur C. Clarke

Page 1 of 2 12 LastLast

Posting Permissions

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