1. Forum
  2. Usenet
  3. ALT.OS.LINUX.UBUNTU

  • Ubuntu slow to shut down

    From Ace Crysler@21:1/5 to All on Sat Aug 20 10:28:26 2022
    Been using 18.04 for quite a long time, but a month ago I started having
    slow shut down. Where what used to be maybe 10 sec was now maybe 10
    min. I googled and there is a command to see the shutdown sequence
    after next boot up, but there's so many processes shown that I can't differentiate between a normal shutdown versus one that lags.

    Only thing I've done so far is modify the timeout and watchdog options
    in config from their defaults to seconds. This cuts shutdown a lot, but
    still like 2 min, and really doesn't solve the issue.

    Any help would be welcome and thanks in advance.

    Ace

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Marco Moock@21:1/5 to All on Sat Aug 20 17:51:58 2022
    Am Samstag, 20. August 2022, um 10:28:26 Uhr schrieb Ace Crysler:

    Been using 18.04 for quite a long time, but a month ago I started
    having slow shut down. Where what used to be maybe 10 sec was now
    maybe 10 min. I googled and there is a command to see the shutdown
    sequence after next boot up, but there's so many processes shown that
    I can't differentiate between a normal shutdown versus one that lags.

    There is a problem.
    Run journalctl -b-1 to see the last journal log that includes the
    shutdown messages. Check the end of the output. You see the time, check
    which item needs minutes to end.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Sativa GNutella@21:1/5 to Ace Crysler on Sat Aug 20 19:50:42 2022
    Ace Crysler <[email protected]> Wrote in message:r
    Been using 18.04 for quite a long time, but a month ago I started having slow shut down. Where what used to be maybe 10 sec was now maybe 10 min. I googled and there is a command to see the shutdown sequence after next boot up, but there's so many
    processes shown that I can't differentiate between a normal shutdown versus one that lags.Only thing I've done so far is modify the timeout and watchdog options in config from their defaults to seconds. This cuts shutdown a lot, but still like 2 min,
    and really doesn't solve the issue.Any help would be welcome and thanks in advance.Ace

    sudo systemctl status

    Does it say 'Degraded' ?
    --

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Ace Crysler@21:1/5 to Marco Moock on Sat Aug 20 13:45:35 2022
    On 8/20/22 11:51, Marco Moock wrote:
    Am Samstag, 20. August 2022, um 10:28:26 Uhr schrieb Ace Crysler:

    Been using 18.04 for quite a long time, but a month ago I started
    having slow shut down. Where what used to be maybe 10 sec was now
    maybe 10 min. I googled and there is a command to see the shutdown
    sequence after next boot up, but there's so many processes shown that
    I can't differentiate between a normal shutdown versus one that lags.

    There is a problem.
    Run journalctl -b-1 to see the last journal log that includes the
    shutdown messages. Check the end of the output. You see the time, check
    which item needs minutes to end.


    Tried that. Reveals a bunch of processes, but I can't tell what should
    be there versus not. No times indicated either.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Ace Crysler@21:1/5 to Sativa GNutella on Sat Aug 20 14:01:00 2022
    On 8/20/22 13:50, Sativa GNutella wrote:
    Ace Crysler <[email protected]> Wrote in message:r
    Been using 18.04 for quite a long time, but a month ago I started having slow shut down. Where what used to be maybe 10 sec was now maybe 10 min. I googled and there is a command to see the shutdown sequence after next boot up, but there's so many
    processes shown that I can't differentiate between a normal shutdown versus one that lags.Only thing I've done so far is modify the timeout and watchdog options in config from their defaults to seconds. This cuts shutdown a lot, but still like 2 min,
    and really doesn't solve the issue.Any help would be welcome and thanks in advance.Ace

    sudo systemctl status

    Does it say 'Degraded' ?

    Interesting. Not close to my desktop at the moment (the PC with the slow
    shut down), but tried it on the laptop which doesn't have the issue. It
    did say degraded.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Marco Moock@21:1/5 to All on Sat Aug 20 20:51:02 2022
    Am Samstag, 20. August 2022, um 13:45:35 Uhr schrieb Ace Crysler:

    Tried that. Reveals a bunch of processes, but I can't tell what
    should be there versus not. No times indicated either.

    e.g.
    Aug 20 20:49:54 ryz kernel: snd_ens1371 0000:06:00.0: AMD-Vi: Event logged [IO_>
    Then see the next entry and find the entry that is minutes after
    predecessor.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Sativa GNutella@21:1/5 to Ace Crysler on Sun Aug 21 20:30:41 2022
    Ace Crysler <[email protected]> Wrote in message:r
    On 8/20/22 13:50, Sativa GNutella wrote:> Ace Crysler <[email protected]> Wrote in message:r>> Been using 18.04 for quite a long time, but a month ago I started having slow shut down. Where what used to be maybe 10 sec was now maybe 10 min. I googled
    and there is a command to see the shutdown sequence after next boot up, but there's so many processes shown that I can't differentiate between a normal shutdown versus one that lags.Only thing I've done so far is modify the timeout and watchdog options
    in config from their defaults to seconds. This cuts shutdown a lot, but still like 2 min, and really doesn't solve the issue.Any help would be welcome and thanks in advance.Ace> > sudo systemctl status> > Does it say 'Degraded' ?Interesting. Not close
    to my desktop at the moment (the PC with the slow shut down), but tried it on the laptop which doesn't have the issue. It did say degraded.


    That means some of your services failed to start. You can see them
    if you run systemctl; without the status argument.

    sudo systemctl --failed

    What does that say?


    sudo systemctl reset-failed

    You can manually clear out failed units with the systemctl
    reset-failed command. This can be done for all units, or a single
    one. Services which are no longer needed, are better to be
    stopped and disabled.


    sudo systemctl status <service>



    https://unix.stackexchange.com/questions/447561/systemctl-status-s hows-state-degraded


    --

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)