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

Thread: Extremely long shutdown time in a restart

Hybrid View

  1. #1
    Join Date
    Apr 2011
    Location
    Texas USA
    Posts
    465

    Default Extremely long shutdown time in a restart

    Machine is taking as long as 10 minutes to shutdown as part of a restart. It sits with a black screen with leap logo at bottom and asus lettering in middle. Extremely long duration, as much as 10 minutes. There does seem to be drive activity so it appears to be doing something. I feel confident that the system is not frozen only taking a long time to do something so I let it go. It does eventually restart. How to find out what is causing it?

    System is i7 cpu, 32g memory, large disk space available, mate desktop (in use for 10 years) . All active processes manually shutdown prior to restart command. Restart was issued from mate menu as has always been done.

    Hundreds of entries in sys log and systemd log. Don't know what is important for dagnosis.

    First question, I can't find a ref for using systemd analyze for a shutdown. Only seems to store info on startup. Any advice?

    Second question, will doing a "power-off" shutdown in the middle of the null period, followed by a "power-on" have a potential to bork my system or should just wait it out?

    thanks, tom kosvic

  2. #2
    Join Date
    Jan 2014
    Location
    Erlangen
    Posts
    3,837

    Default Re: Extremely long shutdown time in a restart

    Quote Originally Posted by tckosvic View Post
    Machine is taking as long as 10 minutes to shutdown as part of a restart. It sits with a black screen with leap logo at bottom and asus lettering in middle. Extremely long duration, as much as 10 minutes. There does seem to be drive activity so it appears to be doing something. I feel confident that the system is not frozen only taking a long time to do something so I let it go. It does eventually restart. How to find out what is causing it?

    System is i7 cpu, 32g memory, large disk space available, mate desktop (in use for 10 years) . All active processes manually shutdown prior to restart command. Restart was issued from mate menu as has always been done.

    Hundreds of entries in sys log and systemd log. Don't know what is important for dagnosis.

    First question, I can't find a ref for using systemd analyze for a shutdown. Only seems to store info on startup. Any advice?

    Second question, will doing a "power-off" shutdown in the middle of the null period, followed by a "power-on" have a potential to bork my system or should just wait it out?

    thanks, tom kosvic
    This is frequently ignored advice: Show what is going on:
    Code:
    erlangen:~ # journalctl -b -1 -o short-monotonic -g Stopped --no-pager                                    
    [    3.027925] erlangen systemd[1]: Stopped target Initrd Default Target. 
    [    3.027954] erlangen systemd[1]: Stopped target Basic System. 
    [    3.028025] erlangen systemd[1]: Stopped target Initrd Root Device. 
    [    3.028054] erlangen systemd[1]: Stopped target Initrd /usr File System. 
    [    3.028119] erlangen systemd[1]: Stopped target Path Units. 
    [    3.045320] erlangen systemd[1]: Stopped Dispatch Password Requests to Console Directory Watch. 
    [    3.045398] erlangen systemd[1]: Stopped target Remote File Systems. 
    [    3.045425] erlangen systemd[1]: Stopped target Preparation for Remote File Systems. 
    [    3.045466] erlangen systemd[1]: Stopped target Slice Units.
    ....
    [55954.643421] erlangen systemd[1]: Stopped target Graphical Interface. 
    [55954.643489] erlangen systemd[1]: Stopped target Multi-User System. 
    [55954.643620] erlangen systemd[1]: Stopped target Login Prompts. 
    [55954.643700] erlangen systemd[1]: Stopped target Sound Card. 
    [55954.643880] erlangen systemd[1]: Stopped target Timer Units. 
    [55954.644042] erlangen systemd[1]: Stopped Backup of /home. 
    [55954.644286] erlangen systemd[1]: Stopped Backup of RPM database. 
    [55954.644417] erlangen systemd[1]: Stopped Backup of /etc/sysconfig. 
    [55954.644584] erlangen systemd[1]: Stopped Balance block groups on a btrfs filesystem. 
    [55954.644945] erlangen systemd[1]: Stopped Scrub btrfs filesystem, verify block checksums. 
    [55954.645088] erlangen systemd[1]: Stopped Check if mainboard battery is Ok. 
    [55954.645218] erlangen systemd[1]: Stopped Discard unused blocks once a week. 
    [55954.645883] erlangen systemd[1]: Stopped Daily rotation of log files. 
    [55954.646004] erlangen systemd[1]: Stopped Daily man-db regeneration. 
    [55954.646251] erlangen systemd[1]: Stopped Daily locate database update. 
    [55954.646379] erlangen systemd[1]: Stopped Systemd timer to update the system daily with PackageKit. 
    [55954.646504] erlangen systemd[1]: Stopped Daily Cleanup of Snapper Snapshots. 
    [55954.646626] erlangen systemd[1]: Stopped Timeline of Snapper Snapshots. 
    [55954.646751] erlangen systemd[1]: Stopped Daily Cleanup of Temporary Directories. 
    [55954.649022] erlangen systemd[1]: Stopped auditd rules generation. 
    [55954.657554] erlangen systemd[1]: Stopped Apply settings from /etc/sysconfig/keyboard. 
    [55954.667937] erlangen systemd[1]: Stopped hd-idle disk spindown service. 
    [55954.668087] erlangen systemd[1]: Stopped irqbalance daemon. 
    [55954.668263] erlangen systemd[1]: Stopped CUPS Scheduler. 
    [55954.668660] erlangen systemd[1]: Stopped Machine Check Exception Logging Daemon. 
    [55954.668945] erlangen systemd[1]: Stopped Getty on tty1. 
    [55954.669740] erlangen systemd[1]: Stopped Command Scheduler. 
    [55954.670262] erlangen systemd[1]: Stopped Authorization Manager. 
    [55954.675026] erlangen systemd[1]: Stopped A remote-mail retrieval utility. 
    [55954.675328] erlangen systemd[1]: Stopped DBus interface for snapper. 
    [55954.676490] erlangen systemd[1]: Stopped Save/Restore Sound Card State. 
    [55954.677224] erlangen systemd[1]: Stopped Restore /run/initramfs on shutdown. 
    [55954.677791] erlangen systemd[1]: Stopped Load/Save Random Seed. 
    [55954.692434] erlangen systemd[1]: Stopped Start fetchmail. 
    [55954.692552] erlangen systemd[1]: Stopped Hold until boot process finishes up. 
    [55954.695288] erlangen systemd[1]: Stopped Disk Manager. 
    [55954.749709] erlangen systemd[1]: Stopped RealtimeKit Scheduling Policy Service. 
    [55954.750614] erlangen systemd[1]: Stopped Daemon for power management. 
    [55954.845047] erlangen systemd[1]: Stopped MiniDLNA is a DLNA/UPnP-AV server software. 
    [55954.845242] erlangen systemd[1]: Stopped target Network is Online. 
    [55954.863258] erlangen systemd[1]: Stopped Postfix Mail Transport Agent. 
    [55954.937733] erlangen systemd[1]: Stopped Initialize hardware monitoring sensors. 
    [55956.009043] erlangen systemd[1]: Stopped X Display Manager. 
    [55956.076728] erlangen systemd[1]: Stopped The Apache Webserver. 
    [55956.077680] erlangen systemd[1]: Stopped target System Time Synchronized. 
    [55956.077924] erlangen systemd[1]: Stopped target System Time Set. 
    [55956.081185] erlangen systemd[1]: Stopped NTP client/server. 
    [55956.082185] erlangen systemd[1]: Stopped target Host and Network Name Lookups. 
    [55956.771169] erlangen systemd[1]: Stopped Session 2 of User karl. 
    [55956.773062] erlangen systemd[1177]: Stopped Konsole - Terminal. 
    [55956.773434] erlangen systemd[1177]: Stopped target Main User Target. 
    [55956.775949] erlangen systemd[1177]: Stopped Save jAlbum Project Files. 
    [55956.776274] erlangen systemd[1177]: Stopped User preferences database. 
    [55956.776753] erlangen systemd[1177]: Stopped Virtual filesystem metadata service. 
    [55956.782187] erlangen systemd[1177]: Stopped Virtual filesystem service. 
    [55956.789530] erlangen systemd[1177]: Stopped D-Bus User Message Bus. 
    [55956.789865] erlangen systemd[1177]: Stopped Accessibility services bus. 
    [55956.789963] erlangen systemd[1177]: Stopped target Basic System. 
    [55956.790006] erlangen systemd[1177]: Stopped target Paths. 
    [55956.790046] erlangen systemd[1177]: Stopped target Sockets. 
    [55956.790084] erlangen systemd[1177]: Stopped target Timers. 
    [55956.790126] erlangen systemd[1177]: Stopped Daily Cleanup of User's Temporary Directories. 
    [55956.790357] erlangen systemd[1177]: Stopped Create User's Volatile Files and Directories. 
    [55956.805827] erlangen systemd[1177]: Stopped KMail - E-Mail-Programm. 
    [55956.813771] erlangen systemd[1177]: Stopped /usr/share/digikam/utils/digikam-camera. 
    [55956.849104] erlangen systemd[1]: Stopped User Manager for UID 1000. 
    [55956.950774] erlangen systemd[1]: Stopped User Login Management. 
    [55957.023901] erlangen systemd[1]: Stopped User Runtime Directory /run/user/1000. 
    [55957.046373] erlangen systemd[1]: Stopped D-Bus System Message Bus. 
    [55957.047874] erlangen systemd[1]: Stopped Permit User Sessions. 
    [55957.048322] erlangen systemd[1]: Stopped target Basic System. 
    [55957.048611] erlangen systemd[1]: Stopped target Network. 
    [55957.048803] erlangen systemd[1]: Stopped target Path Units. 
    [55957.061304] erlangen systemd[1]: Stopped Watch /etc/sysconfig/btrfsmaintenance. 
    [55957.109298] erlangen systemd[1]: Stopped Watch for changes in CA certificates. 
    [55957.109715] erlangen systemd[1]: Stopped CUPS Scheduler. 
    [55957.141293] erlangen systemd[1]: Stopped Watch for changes in issue snippets. 
    [55957.157288] erlangen systemd[1]: Stopped Watch for changes in smartmontools sysconfig file. 
    [55957.157556] erlangen systemd[1]: Stopped target Remote File Systems. 
    [55957.157749] erlangen systemd[1]: Stopped target Slice Units. 
    [55957.158466] erlangen systemd[1]: Stopped target Socket Units. 
    [55957.159491] erlangen systemd[1]: Stopped target System Initialization. 
    [55957.159942] erlangen systemd[1]: Stopped target Local Encrypted Volumes. 
    [55957.173327] erlangen systemd[1]: Stopped Dispatch Password Requests to Console Directory Watch. 
    [55957.173567] erlangen systemd[1]: Stopped target Local Verity Protected Volumes. 
    [55957.197843] erlangen systemd[1]: Stopped Network Name Resolution. 
    [55957.199883] erlangen systemd[1]: Stopped Record System Boot/Shutdown in UTMP. 
    [55957.205475] erlangen systemd[1]: Stopped Network Configuration. 
    [55957.206144] erlangen systemd[1]: Stopped Apply Kernel Variables. 
    [55957.206443] erlangen systemd[1]: Stopped Apply Kernel Variables for 5.16.1-1-default. 
    [55957.206731] erlangen systemd[1]: Stopped Load Kernel Modules. 
    [55957.268222] erlangen systemd[1]: Stopped Security Auditing Service. 
    [55957.268583] erlangen systemd[1]: Stopped Create Volatile Files and Directories. 
    [55957.268608] erlangen systemd[1]: Stopped target Local File Systems. 
    erlangen:~ #
    
    Shutdown of host erlangen takes three seconds.
    i7-6700K (2016), i5-8250U (2018), AMD Ryzen 5 3400G (2020), 5600X (2022) openSUSE Tumbleweed, KDE Plasma

  3. #3
    Join Date
    Apr 2011
    Location
    Texas USA
    Posts
    465

    Default Re: Extremely long shutdown time in a restart

    Code:
    mydesktop:/home/tom # journalctl -b -1 -o short-monotonic -g Stopped --no-pager
    Specifying boot ID or boot offset has no effect, no persistent journal was found.
    mydesktop:/home/tom #
    
    I am not sure what journal is not running and why. syslog is running and systemd journal is running

    Perhaps, I exagerated a bit. A system shutdown (not a restart) took 4min 14 sec per cellphone stopwatch. This is excesive to me.

    tom kosvic

  4. #4
    Join Date
    Jan 2014
    Location
    Erlangen
    Posts
    3,837

    Default Re: Extremely long shutdown time in a restart

    Quote Originally Posted by tckosvic View Post
    Code:
    mydesktop:/home/tom # journalctl -b -1 -o short-monotonic -g Stopped --no-pager
    Specifying boot ID or boot offset has no effect, no persistent journal was found.
    mydesktop:/home/tom #
    I am not sure what journal is not running and why. syslog is running and systemd journal is running

    Perhaps, I exagerated a bit. A system shutdown (not a restart) took 4min 14 sec per cellphone stopwatch. This is excesive to me.

    tom kosvic
    Configure persistent journal first:
    https://www.digitalocean.com/communi...e-systemd-logs
    Look for section Past Boots. Then reboot and run the command.
    i7-6700K (2016), i5-8250U (2018), AMD Ryzen 5 3400G (2020), 5600X (2022) openSUSE Tumbleweed, KDE Plasma

  5. #5
    Join Date
    Apr 2011
    Location
    Texas USA
    Posts
    465

    Default Re: Extremely long shutdown time in a restart

    Per instruction, I edited config file to storage = persistant. Rebooted. Shutdown took again 4 min 9 seconds.

    upon restart ran codes below:

    Code:
    mydesktop:/home/tom # journalctl -b -1 -o short-monotonic -g Stopped --no-pager
    Specifying boot ID or boot offset has no effect, no persistent journal was found.
    mydesktop:/home/tom # journalctl --list-boots
     0 96fcdcf72a2843cdb371e23dc93ea3e1 Wed 2022-01-26 04:15:05 CST—Wed 2022-01-26 10:22>
    mydesktop:/home/tom #
    
    
    journalctl command with no options runs and gives overwhelmingly long list. Too long, I think, to paste into the forum.

    Any other tweaks to get info needed for diagnosis?

    thanks, tom kosvic

  6. #6
    Join Date
    Jan 2014
    Location
    Erlangen
    Posts
    3,837

    Default Re: Extremely long shutdown time in a restart

    Quote Originally Posted by tckosvic View Post
    Per instruction, I edited config file to storage = persistant. Rebooted. Shutdown took again 4 min 9 seconds.

    upon restart ran codes below:

    Code:
    mydesktop:/home/tom # journalctl -b -1 -o short-monotonic -g Stopped --no-pager
    Specifying boot ID or boot offset has no effect, no persistent journal was found.
    mydesktop:/home/tom # journalctl --list-boots
     0 96fcdcf72a2843cdb371e23dc93ea3e1 Wed 2022-01-26 04:15:05 CST—Wed 2022-01-26 10:22>
    mydesktop:/home/tom #
    
    
    Obviously there is only the current boot. Double check your modifications and reboot. On host erlangen I didn't touch file /etc/systemd/journald.conf, but created directory /var/log/journal/ and rebooted. Try again.
    i7-6700K (2016), i5-8250U (2018), AMD Ryzen 5 3400G (2020), 5600X (2022) openSUSE Tumbleweed, KDE Plasma

  7. #7
    Join Date
    Apr 2011
    Location
    Texas USA
    Posts
    465

    Default Re: Extremely long shutdown time in a restart

    I re-edited the config file back to "auto". I created the journal file. I decided to to two reboots to give a track record. Then rerun the specified command.
    1st reboot took 4 min to shut dow.n Bizarrly, the second reboot only took about 15 seconds to shutdown. Somehow system healed itself.

    Code:
    mydesktop:/home/tom # journalctl -b -1 -o short-monotonic -g Stopped --no-pager
    -- Logs begin at Wed 2022-01-26 05:05:57 CST, end at Wed 2022-01-26 11:14:58 CST. --
    [   10.377747] mydesktop systemd[1]: Stopped target Initrd Default Target.
    [   10.377845] mydesktop systemd[1]: Stopped target Basic System.
    [   10.377954] mydesktop systemd[1]: Stopped target Initrd Root Device.
    [   10.378061] mydesktop systemd[1]: Stopped target Paths.
    [   10.378161] mydesktop systemd[1]: Stopped target Remote File Systems.
    [   10.378257] mydesktop systemd[1]: Stopped target Remote File Systems (Pre).
    [   10.378352] mydesktop systemd[1]: Stopped target Slices.
    [   10.378449] mydesktop systemd[1]: Stopped target Sockets.
    [   10.378546] mydesktop systemd[1]: Stopped target System Initialization.
    [   10.378644] mydesktop systemd[1]: Stopped target Swap.
    [   10.378739] mydesktop systemd[1]: Stopped target Timers.
    [   10.378933] mydesktop systemd[1]: Stopped dracut initqueue hook.
    [   10.380012] mydesktop systemd[1]: Stopped Apply Kernel Variables.
    [   10.380352] mydesktop systemd[1]: Stopped Load Kernel Modules.
    [   10.380688] mydesktop systemd[1]: Stopped Create Volatile Files and Directories.
    [   10.380834] mydesktop systemd[1]: Stopped target Local File Systems.
    [   10.380942] mydesktop systemd[1]: Stopped target Local File Systems (Pre).
    [   10.381185] mydesktop systemd[1]: Stopped Coldplug All udev Devices.
    [   10.409593] mydesktop systemd[1]: Stopped Rule-based Manager for Device Events and
     Files.
    [   10.410063] mydesktop systemd[1]: Stopped dracut pre-udev hook.
    [   10.410180] mydesktop systemd[1]: Stopped dracut cmdline hook.
    [   10.410291] mydesktop systemd[1]: Stopped dracut ask for additional cmdline parame
    ters.
    [   10.411099] mydesktop systemd[1]: Stopped Create Static Device Nodes in /dev.
    [   10.411267] mydesktop systemd[1]: Stopped Create list of static device nodes for t
    he current kernel.
    [   13.808855] mydesktop systemd[1]: Stopped Switch Root.
    [   13.810231] mydesktop systemd[1]: Stopped target Switch Root.
    [   13.810259] mydesktop systemd[1]: Stopped target Initrd File Systems.
    [   13.810280] mydesktop systemd[1]: Stopped target Initrd Root File System.
    [   13.818690] mydesktop systemd[1]: Stopped Show Plymouth Boot Screen.
    [   13.818919] mydesktop systemd[1]: Stopped Plymouth switch root service.
    [   13.833223] mydesktop systemd[1]: Stopped Journal Service.
    [   13.918556] mydesktop systemd[1]: Stopped Entropy Daemon based on the HAVEGE algor
    ithm.
    [  223.172539] mydesktop systemd[3324]: Stopped D-Bus User Message Bus.
    [  228.316386] mydesktop systemd[1]: Stopped target Bluetooth.
    [  228.316466] mydesktop systemd[1]: Stopped target Graphical Interface.
    [  228.319586] mydesktop systemd[1]: Stopped target Multi-User System.
    [  228.320080] mydesktop systemd[1]: Stopped target Login Prompts.
    [  228.320172] mydesktop systemd[1813]: Stopped target GNOME X11 Session (session: gn
    ome-login).
    [  228.320454] mydesktop systemd[1813]: Stopped target GNOME Session.
    [  228.320522] mydesktop systemd[1813]: Stopped target GNOME X11 Session.
    [  228.320601] mydesktop systemd[1813]: Stopped target GNOME Session (session: gnome-
    login).
    [  228.320682] mydesktop systemd[1813]: Stopped target GNOME Accessibility settings.
    [  228.320743] mydesktop systemd[1813]: Stopped target GNOME Color management.
    [  228.320807] mydesktop systemd[1813]: Stopped target GNOME Keyboard handling.
    [  228.320875] mydesktop systemd[1]: Stopped target Printer.
    [  228.320940] mydesktop systemd[1813]: Stopped target GNOME Media keys handling.
    [  228.321025] mydesktop systemd[1813]: Stopped target GNOME Power management handlin
    g.
    [  228.321088] mydesktop systemd[1813]: Stopped target GNOME Printer notifications.
    [  228.321176] mydesktop systemd[1813]: Stopped target GNOME RFKill handling.
    [  228.321241] mydesktop systemd[1813]: Stopped target GNOME Smartcard handling.
    [  228.321299] mydesktop systemd[1813]: Stopped target GNOME Wacom handling.
    [  228.321360] mydesktop systemd[1813]: Stopped target GNOME WWan management.
    [  228.321419] mydesktop systemd[1]: Stopped target Sound Card.
    [  228.321484] mydesktop systemd[1813]: Stopped target GNOME XSettings.
    [  228.321547] mydesktop systemd[1813]: Stopped target GNOME session X11 services.
    [  228.321606] mydesktop systemd[1]: Stopped target Timers.
    [  228.321845] mydesktop systemd[1]: Stopped Backup of RPM database.
    [  228.322041] mydesktop systemd[1]: Stopped Backup of /etc/sysconfig.
    [  228.322315] mydesktop systemd[1]: Stopped Check if mainboard battery is Ok.
    [  228.322492] mydesktop systemd[1]: Stopped Discard unused blocks once a week.
    [  228.322718] mydesktop systemd[1]: Stopped Daily rotation of log files.
    [  228.322946] mydesktop systemd[1]: Stopped Do daily mandb update.
    [  228.323168] mydesktop systemd[1]: Stopped Daily locate database update.
    [  228.323285] mydesktop systemd[1]: Stopped Daily Cleanup of Temporary Directories.
    [  228.323396] mydesktop systemd[1]: Stopped daily update of the root trust anchor fo
    r DNSSEC.
    [  228.323451] mydesktop systemd[1813]: Stopped target Current graphical user session
    .
    [  228.324024] mydesktop systemd[1813]: Stopped GNOME Accessibility settings.
    [  228.324153] mydesktop systemd[1813]: Stopped GNOME Printer notifications.
    [  228.324263] mydesktop systemd[1813]: Stopped GNOME RFKill handling.
    [  228.324369] mydesktop systemd[1813]: Stopped GNOME Smartcard handling.
    [  228.324471] mydesktop systemd[1813]: Stopped GNOME WWan management.
    [  228.325817] mydesktop systemd[1]: Stopped Detect if the system suffers from bsc#10
    89761.
    [  228.325942] mydesktop systemd[1813]: Stopped Monitor Session leader for GNOME Sess
    ion.
    [  228.327682] mydesktop systemd[1]: Stopped Apply settings from /etc/sysconfig/keybo
    ard.
    [  228.328071] mydesktop systemd[1]: Stopped Early Kernel Boot Messages.
    [  228.328581] mydesktop systemd[1]: Stopped download broadcom firmware files needed 
    for bcm43xx WLAN chips.
    [  228.338561] mydesktop systemd[1813]: Stopped GNOME Keyboard handling.
    [  228.339074] mydesktop systemd[1813]: Stopped GNOME Power management handling.
    [  228.340230] mydesktop systemd[1813]: Stopped GNOME Wacom handling.
    [  228.340393] mydesktop systemd[1]: Stopped irqbalance daemon.
    [  228.340847] mydesktop systemd[1813]: Stopped GNOME XSettings.
    [  228.340988] mydesktop systemd[1]: Stopped Self Monitoring and Reporting Technology
     (SMART) Daemon.
    [  228.341410] mydesktop systemd[1]: Stopped Machine Check Exception Logging Daemon.
    [  228.341476] mydesktop systemd[1813]: Stopped GNOME Media keys handling.
    [  228.341817] mydesktop systemd[1]: Stopped System Logging Service.
    [  228.342099] mydesktop systemd[1813]: Stopped GNOME Color management.
    [  228.342239] mydesktop systemd[1]: Stopped Make remote CUPS printers available loca
    lly.
    [  228.342585] mydesktop systemd[1813]: Stopped target GNOME Session is initialized.
    [  228.342654] mydesktop systemd[1813]: Stopped target GNOME Shell on X11.
    [  228.342787] mydesktop systemd[1]: Stopped Manage, Install and Generate Color Profi
    les.
    [  228.343544] mydesktop systemd[1]: Stopped Accounts Service.
    [  228.344676] mydesktop systemd[1813]: Stopped GNOME Shell on X11.
    [  228.344751] mydesktop systemd[1813]: Stopped target GNOME Session Manager is ready
    .
    [  228.346227] mydesktop systemd[1]: Stopped Command Scheduler.
    [  228.346971] mydesktop systemd[1]: Stopped Daemon for power management.
    [  228.347898] mydesktop systemd[1]: Stopped RealtimeKit Scheduling Policy Service.
    [  228.348934] mydesktop systemd[1]: Stopped Getty on tty1.
    [  228.349596] mydesktop systemd[1]: Stopped Save/Restore Sound Card State.
    [  228.361173] mydesktop systemd[1813]: Stopped GNOME Session Manager (session: gnome
    -login).
    [  228.361245] mydesktop systemd[1813]: Stopped target Tasks to be run before GNOME S
    ession starts.
    [  228.361318] mydesktop systemd[1813]: Stopped target Session services which should 
    run early before the graphical session is brought up.
    [  228.361967] mydesktop systemd[1813]: Stopped target Shutdown running GNOME Session
    .
    [  228.366988] mydesktop systemd[1813]: Stopped D-Bus User Message Bus.
    [  228.386751] mydesktop systemd[1]: Stopped Disk Manager.
    [  228.387411] mydesktop systemd[1]: Stopped Restore /run/initramfs on shutdown.
    [  228.389191] mydesktop systemd[1]: Stopped Hold until boot process finishes up.
    [  228.402441] mydesktop systemd[3324]: Stopped target Main User Target.
    [  228.404095] mydesktop systemd[3324]: Stopped PipeWire PulseAudio.
    [  228.406738] mydesktop systemd[1]: Stopped CUPS Scheduler.
    [  228.408398] mydesktop systemd[3324]: Stopped D-Bus User Message Bus.
    [  228.408738] mydesktop systemd[1]: Stopped Avahi mDNS/DNS-SD Stack.
    [  228.409408] mydesktop systemd[3324]: Stopped Multimedia Service Session Manager.
    [  228.410622] mydesktop systemd[3324]: Stopped Multimedia Service.
    [  228.410850] mydesktop systemd[3324]: Stopped target Basic System.
    [  228.410899] mydesktop systemd[3324]: Stopped target Paths.
    [  228.410945] mydesktop systemd[3324]: Stopped target Sockets.
    [  228.410988] mydesktop systemd[3324]: Stopped target Timers.
    [  228.414274] mydesktop systemd[1]: Stopped User Manager for UID 1000.
    [  228.421626] mydesktop systemd[1]: Stopped User Runtime Directory /run/user/1000.
    [  228.451960] mydesktop systemd[1]: Stopped Bluetooth service.
    [  228.456396] mydesktop systemd[1]: Stopped Postfix Mail Transport Agent.
    [  228.546218] mydesktop systemd[1]: Stopped Virtual Machine qemu-1-opensuseTW.
    [  228.584078] mydesktop systemd[1]: Stopped Modem Manager.
    [  228.762676] mydesktop systemd[1]: Stopped Session c1 of user gdm.
    [  228.763528] mydesktop systemd[1813]: Stopped target Main User Target.
    [  228.764984] mydesktop systemd[1813]: Stopped PipeWire PulseAudio.
    [  228.776550] mydesktop systemd[1813]: Stopped D-Bus User Message Bus.
    [  228.813195] mydesktop systemd[1813]: Stopped Multimedia Service Session Manager.
    [  228.814392] mydesktop systemd[1813]: Stopped Multimedia Service.
    [  228.814633] mydesktop systemd[1813]: Stopped target Basic System.
    [  228.814682] mydesktop systemd[1813]: Stopped target Paths.
    [  228.814730] mydesktop systemd[1813]: Stopped target Sockets.
    [  228.814777] mydesktop systemd[1813]: Stopped target Timers.
    [  228.818093] mydesktop systemd[1]: Stopped User Manager for UID 461.
    [  228.825528] mydesktop systemd[1]: Stopped User Runtime Directory /run/user/461.
    [  228.879882] mydesktop systemd[1]: Stopped Load/Save Random Seed.
    [  228.903036] mydesktop systemd[1]: Stopped Berkeley Open Infrastructure Network Com
    puting Client.
    [  229.001169] mydesktop systemd[1]: Stopped Virtualization daemon.
    [  229.002682] mydesktop systemd[1]: Stopped Virtual Machine and Container Registrati
    on Service.
    [  229.003259] mydesktop systemd[1]: Stopped Virtual machine log manager.
    [  229.041924] mydesktop systemd[1]: Stopped X Display Manager.
    [  229.043064] mydesktop systemd[1]: Stopped target System Time Synchronized.
    [  229.043181] mydesktop systemd[1]: Stopped target System Time Set.
    [  229.046329] mydesktop systemd[1]: Stopped NTP client/server.
    [  229.047519] mydesktop systemd[1]: Stopped target Host and Network Name Lookups.
    [  229.049786] mydesktop systemd[1]: Stopped Permit User Sessions.
    [  229.049975] mydesktop systemd[1]: Stopped target Remote File Systems.
    [  229.056411] mydesktop systemd[1]: Stopped Login and scanning of iSCSI devices.
    [  229.056618] mydesktop systemd[1]: Stopped target Network is Online.
    [  229.056703] mydesktop systemd[1]: Stopped target Network.
    [  229.097026] mydesktop systemd[1]: Stopped User Login Management.
    [  229.097268] mydesktop systemd[1]: Stopped target User and Group Name Lookups.
    [  229.112715] mydesktop systemd[1]: Stopped Name Service Cache Daemon.
    [  234.653397] mydesktop systemd[1]: Stopped wicked managed network interfaces.
    [  234.654241] mydesktop systemd[1]: Stopped wicked network nanny service.
    [  234.655076] mydesktop systemd[1]: Stopped wicked network management service daemon
    .
    [  234.656040] mydesktop systemd[1]: Stopped wicked AutoIPv4 supplicant service.
    [  234.656521] mydesktop systemd[1]: Stopped wicked DHCPv4 supplicant service.
    [  234.656925] mydesktop systemd[1]: Stopped wicked DHCPv6 supplicant service.
    [  234.657133] mydesktop systemd[1]: Stopped target Network (Pre).
    [  234.733404] mydesktop systemd[1]: Stopped WPA Supplicant daemon.
    [  236.753584] mydesktop systemd[1]: Stopped firewalld - dynamic firewall daemon.
    [  236.760530] mydesktop systemd[1]: Stopped D-Bus System Message Bus.
    [  236.808735] mydesktop systemd[1]: Stopped Authorization Manager.
    [  236.808966] mydesktop systemd[1]: Stopped target Basic System.
    [  236.824173] mydesktop systemd[1]: Stopped Forward Password Requests to Plymouth Di
    rectory Watch.
    [  236.824301] mydesktop systemd[1]: Stopped target Paths.
    [  236.920192] mydesktop systemd[1]: Stopped Watch for changes in CA certificates.
    [  236.920532] mydesktop systemd[1]: Stopped CUPS Scheduler.
    [  236.936138] mydesktop systemd[1]: Stopped Watch for changes in smartmontools sysco
    nfig file.
    [  236.936238] mydesktop systemd[1]: Stopped target Slices.
    [  236.936821] mydesktop systemd[1]: Stopped target Sockets.
    [  236.938287] mydesktop systemd[1]: Stopped target System Initialization.
    [  236.938450] mydesktop systemd[1]: Stopped target Local Encrypted Volumes.
    [  236.938503] mydesktop systemd[1]: Stopped target Swap.
    [  236.939019] mydesktop systemd[1]: Stopped Apply Kernel Variables.
    [  236.939214] mydesktop systemd[1]: Stopped Load Kernel Modules.
    [  236.947033] mydesktop systemd[1]: Stopped Update UTMP about System Boot/Shutdown.
    [  236.958200] mydesktop systemd[1]: Stopped Security Auditing Service.
    [  236.958382] mydesktop systemd[1]: Stopped Create Volatile Files and Directories.
    [  236.958442] mydesktop systemd[1]: Stopped target Local File Systems.
    [  236.975140] mydesktop systemd[1]: Stopped File System Check on /dev/disk/by-uuid/C
    93A-C87E.
    [  237.117052] mydesktop systemd[1]: Stopped File System Check on /dev/disk/by-uuid/e
    748b401-3a8f-4152-a9ea-ef540efb0230.
    [  237.117481] mydesktop systemd[1]: Stopped target Local File Systems (Pre).
    [  237.118430] mydesktop systemd[1]: Stopped Remount Root and Kernel File Systems.
    [  237.118629] mydesktop systemd[1]: Stopped File System Check on Root Device.
    [  237.118850] mydesktop systemd[1]: Stopped Create Static Device Nodes in /dev.
    [  237.277330] mydesktop systemd[1]: Stopped Monitoring of LVM2 mirrors, snapshots et
    c. using dmeventd or progress polling.
    mydesktop:/home/tom #
    
    Perhaps this gives a clue but I can live with last reboot.

    thanks, tom kosvic

  8. #8
    Join Date
    Apr 2011
    Location
    Texas USA
    Posts
    465

    Default Re: Extremely long shutdown time in a restart

    To verify reboot times, I did another restart. Only 10 sec or so to shutdown. Problem has gone away with no changes made. That means it will come back at some time. but dor now, it;s ok

    tom kosvic

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

    Default Re: Extremely long shutdown time in a restart

    Quote Originally Posted by tckosvic View Post
    I re-edited the config file back to "auto". I created the journal file. I decided to to two reboots to give a track record. Then rerun the specified command.
    1st reboot took 4 min to shut dow.n Bizarrly, the second reboot only took about 15 seconds to shutdown. Somehow system healed itself.

    Code:
    mydesktop:/home/tom # journalctl -b -1 -o short-monotonic -g Stopped --no-pager
    -- Logs begin at Wed 2022-01-26 05:05:57 CST, end at Wed 2022-01-26 11:14:58 CST. --
    [   10.377747] mydesktop systemd[1]: Stopped target Initrd Default Target.
    [   10.377845] mydesktop systemd[1]: Stopped target Basic System.
    [   10.377954] mydesktop systemd[1]: Stopped target Initrd Root Device.
    [   10.378061] mydesktop systemd[1]: Stopped target Paths.
    [   10.378161] mydesktop systemd[1]: Stopped target Remote File Systems.
    [   10.378257] mydesktop systemd[1]: Stopped target Remote File Systems (Pre).
    [   10.378352] mydesktop systemd[1]: Stopped target Slices.
    [   10.378449] mydesktop systemd[1]: Stopped target Sockets.
    [   10.378546] mydesktop systemd[1]: Stopped target System Initialization.
    [   10.378644] mydesktop systemd[1]: Stopped target Swap.
    [   10.378739] mydesktop systemd[1]: Stopped target Timers.
    [   10.378933] mydesktop systemd[1]: Stopped dracut initqueue hook.
    [   10.380012] mydesktop systemd[1]: Stopped Apply Kernel Variables.
    [   10.380352] mydesktop systemd[1]: Stopped Load Kernel Modules.
    [   10.380688] mydesktop systemd[1]: Stopped Create Volatile Files and Directories.
    [   10.380834] mydesktop systemd[1]: Stopped target Local File Systems.
    [   10.380942] mydesktop systemd[1]: Stopped target Local File Systems (Pre).
    [   10.381185] mydesktop systemd[1]: Stopped Coldplug All udev Devices.
    [   10.409593] mydesktop systemd[1]: Stopped Rule-based Manager for Device Events and Files.
    [   10.410063] mydesktop systemd[1]: Stopped dracut pre-udev hook.
    [   10.410180] mydesktop systemd[1]: Stopped dracut cmdline hook.
    [   10.410291] mydesktop systemd[1]: Stopped dracut ask for additional cmdline parameters.
    [   10.411099] mydesktop systemd[1]: Stopped Create Static Device Nodes in /dev.
    [   10.411267] mydesktop systemd[1]: Stopped Create list of static device nodes for the current kernel.
    [   13.808855] mydesktop systemd[1]: Stopped Switch Root.
    [   13.810231] mydesktop systemd[1]: Stopped target Switch Root.
    [   13.810259] mydesktop systemd[1]: Stopped target Initrd File Systems.
    [   13.810280] mydesktop systemd[1]: Stopped target Initrd Root File System.
    [   13.818690] mydesktop systemd[1]: Stopped Show Plymouth Boot Screen.
    [   13.818919] mydesktop systemd[1]: Stopped Plymouth switch root service.
    [   13.833223] mydesktop systemd[1]: Stopped Journal Service.
    [   13.918556] mydesktop systemd[1]: Stopped Entropy Daemon based on the HAVEGE algorithm.
    ...
    mydesktop:/home/tom #
    
    Perhaps this gives a clue but I can live with last reboot.
    erlangen is faster than mydesktop:
    Code:
    erlangen:~ # journalctl -b -1 -u init.scope -o short-monotonic -g Stopped|grep 'Create Static Device Nodes' 
    [    2.915677] erlangen systemd[1]: Stopped Create Static Device Nodes in /dev. 
    erlangen:~ #
    Thus I presume you get what you can hope for.
    i7-6700K (2016), i5-8250U (2018), AMD Ryzen 5 3400G (2020), 5600X (2022) openSUSE Tumbleweed, KDE Plasma

  10. #10
    Join Date
    Apr 2011
    Location
    Texas USA
    Posts
    465

    Default Re: Extremely long shutdown time in a restart

    I almost lost my computer due to no / disk space from diagnostic messages. I believe it was due to the diagnostic changes I made regarding shutdown times.

    I got message -- only 1 gig left in root. Then apps stopped running. I did restart and no normal start only black screen. Alt-f2 got me to a login. I got to root and /var/log. messages file was 65 gig. I deleted it. A restart was normal.

    Subsequently, I deleted all the files in /var/log/journal that I created. Maybe I should delete entire journal directory? I also made sure that systemd.journald.conf had "storage=auto" as it was originally.

    Anything else, I should do to make sure messages are under control? Now I am back at 30% root use out of 100 gig.

    thanks, tom kosvic

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
  •