Page 2 of 2 FirstFirst 12
Results 11 to 20 of 20

Thread: Extremely long shutdown time in a restart

  1. #11
    Join Date
    Jan 2014
    Location
    Erlangen
    Posts
    3,991

    Default Re: Extremely long shutdown time in a restart

    Quote Originally Posted by tckosvic View Post
    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.
    Stop tinkering. Don't try to be too clever. Undo those diagnostics. Rely on journal only.

    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?
    Nope. Journal is a matured application. Use this instead:
    Code:
    erlangen:~ # journalctl --vacuum-size 1G 
    Vacuuming done, freed 0B of archived journals from /run/log/journal. 
    Vacuuming done, freed 0B of archived journals from /var/log/journal. 
    Vacuuming done, freed 0B of archived journals from /var/log/journal/94f3af277bac4a8eb57da425c9677379. 
    erlangen:~ #
    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.
    Show usage:
    Code:
    erlangen:~ # btrfs filesystem usage -T /            
    Overall: 
        Device size:                   1.82TiB 
        Device allocated:            403.07GiB 
        Device unallocated:            1.42TiB 
        Device missing:                  0.00B 
        Used:                        384.71GiB 
        Free (estimated):              1.44TiB      (min: 745.61GiB) 
        Free (statfs, df):             1.44TiB 
        Data ratio:                       1.00 
        Metadata ratio:                   2.00 
        Global reserve:              512.00MiB      (used: 0.00B) 
        Multiple profiles:                  no 
    
                      Data      Metadata System               
    Id Path           single    DUP      DUP      Unallocated 
    -- -------------- --------- -------- -------- ----------- 
     1 /dev/nvme0n1p2 397.01GiB  6.00GiB 64.00MiB     1.42TiB 
    -- -------------- --------- -------- -------- ----------- 
       Total          397.01GiB  3.00GiB 32.00MiB     1.42TiB 
       Used           381.12GiB  1.79GiB 64.00KiB             
    erlangen:~ #

    Code:
    erlangen:~ # du -hd1 -t10k /var/log 
    12M     /var/log/YaST2 
    8.1M    /var/log/zypp 
    72M     /var/log/journal 
    3.0M    /var/log/cups 
    5.5M    /var/log/audit 
    16K     /var/log/samba 
    1.5M    /var/log/apache2 
    12M     /var/log/updateTestcase-2022-01-25-18-48-40 
    12M     /var/log/updateTestcase-2022-01-27-01-22-32 
    183M    /var/log 
    erlangen:~ #
    i7-6700K (2016), i5-8250U (2018), AMD Ryzen 5 3400G (2020), 5600X (2022) openSUSE Tumbleweed, KDE Plasma

  2. #12
    Join Date
    Apr 2011
    Location
    Texas USA
    Posts
    488

    Default Re: Extremely long shutdown time in a restart

    I have ext4 file system. I see nothing but problem threads from btrfs so I use ext4. I dont think an "active" filesystem is necessary.



    thanks, tom kosvic

  3. #13
    Join Date
    Apr 2011
    Location
    Texas USA
    Posts
    488

    Default Re: Extremely long shutdown time in a restart

    see code dump below. But this is after deleting almost 70 gig of messages in messages file.

    Code:
    (base) tom@mydesktop:~> sudo du -hd1 -t10k /var/log
    [sudo] password for root:  
    128K    /var/log/cepces
    8.0M    /var/log/audit
    50M     /var/log/YaST2
    2.3M    /var/log/cups
    1.6M    /var/log/libvirt
    3.7M    /var/log/zypp
    33M     /var/log/journal
    12K     /var/log/swtpm
    153M    /var/log
    (base) tom@mydesktop:~> 
    
    thanks, tomkosvic

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

    Default Re: Extremely long shutdown time in a restart

    Quote Originally Posted by tckosvic View Post
    I see nothing but problem threads from btrfs so I use ext4.
    There have been minor issues, which have been fixed some time ago: https://karlmistelberger.wordpress.c...g-on-opensuse/

    Actually btrfs is a big leap forward: https://forums.opensuse.org/showthre...49#post2978149

    Currently I have:
    Code:
    erlangen:~ # fdisk -l /dev/nvme0n1 
    Disk /dev/nvme0n1: 1.82 TiB, 2000398934016 bytes, 3907029168 sectors
    Disk model: Samsung SSD 970 EVO Plus 2TB             
    Units: sectors of 1 * 512 = 512 bytes 
    Sector size (logical/physical): 512 bytes / 512 bytes 
    I/O size (minimum/optimal): 512 bytes / 512 bytes 
    Disklabel type: gpt 
    Disk identifier: F5B232D0-7A67-461D-8E7D-B86A5B4C6C10 
    
    Device          Start       End   Sectors SizeType
    /dev/nvme0n1p1    2048    1050623    1048576  512M EFI System 
    /dev/nvme0n1p2 1050624 3907029134 3905978511  1.8T Linux filesystem 
    erlangen:~ # btrfs filesystem usage -T / 
    Overall: 
        Device size:                   1.82TiB 
        Device allocated:            404.07GiB 
        Device unallocated:            1.42TiB 
        Device missing:                  0.00B 
        Used:                        383.17GiB 
        Free (estimated):              1.44TiB      (min: 747.45GiB) 
        Free (statfs, df):             1.44TiB 
        Data ratio:                       1.00 
        Metadata ratio:                   2.00 
        Global reserve:              512.00MiB      (used: 0.00B) 
        Multiple profiles:                  no 
    
                      Data      Metadata System               
    Id Path           single    DUP      DUP      Unallocated 
    -- -------------- --------- -------- -------- ----------- 
     1 /dev/nvme0n1p2 398.01GiB  6.00GiB 64.00MiB     1.42TiB 
    -- -------------- --------- -------- -------- ----------- 
       Total          398.01GiB  3.00GiB 32.00MiB     1.42TiB 
       Used           379.78GiB  1.70GiB 64.00KiB             
    erlangen:~ # snapper list 
       # | Type   | Pre # | Date                     | User | Cleanup | Description           | Userdata      
    -----+--------+-------+--------------------------+------+---------+-----------------------+-------------- 
      0  | single |       |                          | root |         | current               |               
      1* | single |       | Wed Nov 24 21:33:32 2021 | root |         | first root filesystem |               
    170  | pre    |       | Fri Jan 21 12:08:55 2022 | root | number  | zypp(zypper)          | important=yes 
    171  | post   |   170 | Fri Jan 21 12:09:02 2022 | root | number  |                       | important=yes 
    180  | pre    |       | Sun Jan 23 19:17:43 2022 | root | number  | zypp(zypper)          | important=yes 
    181  | post   |   180 | Sun Jan 23 19:20:11 2022 | root | number  |                       | important=yes 
    184  | pre    |       | Tue Jan 25 03:20:04 2022 | root | number  | zypp(zypper)          | important=yes 
    185  | post   |   184 | Tue Jan 25 03:27:34 2022 | root | number  |                       | important=yes 
    186  | pre    |       | Tue Jan 25 18:48:39 2022 | root | number  | zypp(zypper)          | important=no  
    187  | post   |   186 | Tue Jan 25 18:48:43 2022 | root | number  |                       | important=no  
    188  | pre    |       | Thu Jan 27 01:22:31 2022 | root | number  | zypp(zypper)          | important=no  
    189  | post   |   188 | Thu Jan 27 01:22:45 2022 | root | number  |                       | important=no  
    190  | pre    |       | Thu Jan 27 02:18:42 2022 | root | number  | zypp(zypper)          | important=no  
    191  | post   |   190 | Thu Jan 27 02:19:39 2022 | root | number  |                       | important=no  
    192  | pre    |       | Thu Jan 27 15:55:49 2022 | root | number  | zypp(zypper)          | important=no  
    193  | post   |   192 | Thu Jan 27 15:55:55 2022 | root | number  |                       | important=no  
    194  | pre    |       | Thu Jan 27 20:25:29 2022 | root | number  | zypp(zypper)          | important=no  
    195  | post   |   194 | Thu Jan 27 20:26:52 2022 | root | number  |                       | important=no  
    196  | pre    |       | Fri Jan 28 04:59:03 2022 | root | number  | zypp(zypper)          | important=yes 
    197  | post   |   196 | Fri Jan 28 05:01:24 2022 | root | number  |                       | important=yes 
    198  | pre    |       | Fri Jan 28 05:11:27 2022 | root | number  | zypp(zypper)          | important=yes 
    199  | post   |   198 | Fri Jan 28 05:11:31 2022 | root | number  |                       | important=yes 
    200  | pre    |       | Fri Jan 28 07:58:05 2022 | root | number  | zypp(zypper)          | important=no  
    201  | post   |   200 | Fri Jan 28 07:58:15 2022 | root | number  |                       | important=no  
    204  | pre    |       | Fri Jan 28 18:24:57 2022 | root | number  | zypp(zypper)          | important=no  
    205  | post   |   204 | Fri Jan 28 18:25:09 2022 | root | number  |                       | important=no  
    erlangen:~ #
    No severe messages in journal. Warnings are rare:
    Code:
    erlangen:~ # journalctl --quiet --priority warning --grep btrfs 
    Jan 24 18:20:22 erlangen kernel: BTRFS warning (device nvme0n1p2): qgroup rescan init failed, qgroup is not enabled
    Jan 28 21:21:32 erlangen kernel: BTRFS warning (device nvme0n1p2): qgroup rescan init failed, qgroup is not enabled
    Jan 29 06:37:21 erlangen kernel: BTRFS warning (device nvme0n1p2): qgroup rescan init failed, qgroup is not enabled
    erlangen:~ #
    Summary

    btrfs has great features. It's built into the kernel, warranting easy maintenance and extreme robustness. It's flexible. It's the optimal file system for SSDs.

    Warning

    Don't use it on shaky hardware. Don't tinker. The default setup as shown above works best. When moving from ext4 to btrfs beware of pitfalls. Start with a pristine default installation and rsync your system: https://forums.opensuse.org/showthre...58#post3086058
    i7-6700K (2016), i5-8250U (2018), AMD Ryzen 5 3400G (2020), 5600X (2022) openSUSE Tumbleweed, KDE Plasma

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

    Default Re: Extremely long shutdown time in a restart

    Quote Originally Posted by tckosvic View Post
    see code dump below. But this is after deleting almost 70 gig of messages in messages file.

    Code:
    (base) tom@mydesktop:~> sudo du -hd1 -t10k /var/log
    [sudo] password for root:  
    128K    /var/log/cepces
    8.0M    /var/log/audit
    50M     /var/log/YaST2
    2.3M    /var/log/cups
    1.6M    /var/log/libvirt
    3.7M    /var/log/zypp
    33M     /var/log/journal
    12K     /var/log/swtpm
    153M    /var/log
    (base) tom@mydesktop:~> 
    
    Beware of syslog:
    Code:
    erlangen:~ # zypper search --installed-only syslog 
    Loading repository data... 
    Reading installed packages... 
    No matching items found. 
    erlangen:~ #
    
    None of my systems has /var/log/messages. Get familiar with journal and stick to it: https://www.digitalocean.com/communi...e-systemd-logs

    Always post properly filtered journal. Don't play Battleship with users willing to help.
    i7-6700K (2016), i5-8250U (2018), AMD Ryzen 5 3400G (2020), 5600X (2022) openSUSE Tumbleweed, KDE Plasma

  6. #16
    Join Date
    Apr 2011
    Location
    Texas USA
    Posts
    488

    Default Re: Extremely long shutdown time in a restart

    My system has /var/log/messages file and I don't know what put it there.

    I am not sure what you meant about playing battleship.

    I followed some ideas you gave me to diagnose my shutdown problem and I appreciate your advice. But, incorporating those changes for diagnosis made for the /var/log/messages file to grow very quickly to >65gig. It filled root and shutdown my machine. I was able to recover by deleting that file after getting into a terminal using alt-f2 . I undid all the changes made just before that happened and rebooted several times. Bt the way, shutdowns were tolerably short since then.

    Last time I reinstalled system due to nvidia grapgics issues, I formatted disk using openSUSE installer as ext4 rather than btrfs as I had problems with btrfs before and i saw many others asking for problem solutions. No one asks for any solutions to problems related to ext4. I did not convert system to ext4 from btrfs, ext4 was installed from scratch.

    From last comment here is code block:

    Code:
    (base) tom@mydesktop:~> sudo zypper search --installed-only syslog  
    [sudo] password for root:  
    Loading repository data...
    Reading installed packages...
    
    S | Name           | Summary                                 | Type
    --+----------------+-----------------------------------------+--------
    i | rsyslog        | The enhanced syslogd for Linux and Unix | package
    i | syslog-service | Syslog service files & scripts          | package
    (base) tom@mydesktop:~>
    


    Please advise me. Should the rsyslog packages be removed? It appears you don't have these packages from above code you posted. Did this app create the /var/log/messages file, maybe?

    thanks again, tom kosvic



  7. #17
    Join Date
    Apr 2011
    Location
    Texas USA
    Posts
    488

    Default Re: Extremely long shutdown time in a restart

    I examined message info in /var/log/messages file and in /var/log/journal/xxxxx file that is from systemd and message at same time were identical. It also appears that rsyslog and associated service were generating /var/log/message files so I deleted rsyslog and service through yast software manager. I also deleted /var/log/messages files and /var/log/warn file.

    All log info will be through systemd journal. I do not remember how, why, or when rsyslog got installled but it is no longer inplace.

    My shutdown times (the reason for this thread) have changed from 4+ minutes to tolerable even though no changes were implemented.

    thanks all, tom kosvic

  8. #18
    Join Date
    Jan 2014
    Location
    Erlangen
    Posts
    3,991

    Default Re: Extremely long shutdown time in a restart

    Quote Originally Posted by tckosvic View Post
    I examined message info in /var/log/messages file and in /var/log/journal/xxxxx file that is from systemd and message at same time were identical. It also appears that rsyslog and associated service were generating /var/log/message files so I deleted rsyslog and service through yast software manager. I also deleted /var/log/messages files and /var/log/warn file.

    All log info will be through systemd journal. I do not remember how, why, or when rsyslog got installled but it is no longer inplace.

    My shutdown times (the reason for this thread) have changed from 4+ minutes to tolerable even though no changes were implemented.

    thanks all, tom kosvic
    Great. As a courtesy to other readers you may show evidence by running and posting the output:

    Code:
    erlangen:~ # zypper search --installed-only syslog                                
    Loading repository data... 
    Reading installed packages... 
    No matching items found. 
    erlangen:~ #
    Code:
    erlangen:~ # du -h /var/log/journal/ 
    112M    /var/log/journal/94f3af277bac4a8eb57da425c9677379 
    112M    /var/log/journal/ 
    erlangen:~ #
    
    Code:
    erlangen:~ # journalctl -b -1 -o short-monotonic -g Stopped --no-pager  
    [    3.016008] erlangen systemd[1]: Stopped target Initrd Default Target. 
    [    3.016089] erlangen systemd[1]: Stopped target Basic System. 
    [    3.016117] erlangen systemd[1]: Stopped target Initrd Root Device. 
    [    3.016189] erlangen systemd[1]: Stopped target Initrd /usr File System. 
    [    3.016216] erlangen systemd[1]: Stopped target Path Units.
    ...
    [ 3425.227064] erlangen systemd[1]: Stopped target Graphical Interface. 
    [ 3425.227328] erlangen systemd[1]: Stopped target Multi-User System. 
    [ 3425.228066] erlangen systemd[1]: Stopped target Login Prompts. 
    [ 3425.228598] erlangen systemd[1]: Stopped target Sound Card. 
    [ 3425.228683] erlangen systemd[1]: Stopped target Timer Units. 
    [ 3425.228890] erlangen systemd[1]: Stopped Backup of /home. 
    [ 3425.229047] erlangen systemd[1]: Stopped Backup of RPM database. 
    [ 3425.229200] erlangen systemd[1]: Stopped Backup of /etc/sysconfig. 
    [ 3425.229369] erlangen systemd[1]: Stopped Balance block groups on a btrfs filesystem. 
    [ 3425.245649] erlangen systemd[1]: Stopped Scrub btrfs filesystem, verify block checksums. 
    [ 3425.246678] erlangen systemd[1]: Stopped Check if mainboard battery is Ok. 
    [ 3425.246897] erlangen systemd[1]: Stopped Discard unused blocks once a week. 
    [ 3425.247015] erlangen systemd[1]: Stopped Daily rotation of log files. 
    [ 3425.247118] erlangen systemd[1]: Stopped Daily man-db regeneration. 
    [ 3425.247241] erlangen systemd[1]: Stopped Daily locate database update. 
    [ 3425.247350] erlangen systemd[1]: Stopped Systemd timer to update the system daily with PackageKit. 
    [ 3425.247496] erlangen systemd[1]: Stopped Daily Cleanup of Snapper Snapshots. 
    [ 3425.247992] erlangen systemd[1]: Stopped Timeline of Snapper Snapshots. 
    [ 3425.248106] erlangen systemd[1]: Stopped Daily Cleanup of Temporary Directories. 
    [ 3425.248791] erlangen systemd[1]: Stopped auditd rules generation. 
    [ 3425.250047] erlangen systemd[1]: Stopped Apply settings from /etc/sysconfig/keyboard. 
    [ 3425.252069] erlangen systemd[1]: Stopped hd-idle disk spindown service. 
    [ 3425.252785] erlangen systemd[1]: Stopped irqbalance daemon. 
    [ 3425.253445] erlangen systemd[1]: Stopped Machine Check Exception Logging Daemon. 
    [ 3425.254037] erlangen systemd[1]: Stopped CUPS Scheduler. 
    [ 3425.254822] erlangen systemd[1]: Stopped Getty on tty1. 
    [ 3425.255465] erlangen systemd[1]: Stopped Command Scheduler. 
    [ 3425.256050] erlangen systemd[1]: Stopped Daemon for power management. 
    [ 3425.257976] erlangen systemd[1]: Stopped RealtimeKit Scheduling Policy Service. 
    [ 3425.259138] erlangen systemd[1]: Stopped A remote-mail retrieval utility. 
    [ 3425.260273] erlangen systemd[1]: Stopped Save/Restore Sound Card State. 
    [ 3425.261012] erlangen systemd[1]: Stopped Restore /run/initramfs on shutdown. 
    [ 3425.261808] erlangen systemd[1]: Stopped Load/Save Random Seed. 
    [ 3425.263652] erlangen systemd[1]: Stopped Start fetchmail. 
    [ 3425.263787] erlangen systemd[1]: Stopped Hold until boot process finishes up. 
    [ 3425.273701] erlangen systemd[1]: Stopped Authorization Manager. 
    [ 3425.302000] erlangen systemd[1]: Stopped MiniDLNA is a DLNA/UPnP-AV server software. 
    [ 3425.302303] erlangen systemd[1]: Stopped target Network is Online. 
    [ 3425.306386] erlangen systemd[1]: Stopped Disk Manager. 
    [ 3425.312068] erlangen systemd[1]: Stopped Session 2 of User karl. 
    [ 3425.333005] erlangen systemd[1168]: Stopped target Main User Target. 
    [ 3425.333615] erlangen systemd[1168]: Stopped Sound Service. 
    [ 3425.333922] erlangen systemd[1168]: Stopped Accessibility services bus. 
    [ 3425.333982] erlangen systemd[1168]: Stopped User preferences database. 
    [ 3425.334040] erlangen systemd[1168]: Stopped Save jAlbum Project Files. 
    [ 3425.334088] erlangen systemd[1168]: Stopped Terminal - Super User Mode. 
    [ 3425.334207] erlangen systemd[1168]: Stopped D-Bus User Message Bus. 
    [ 3425.346884] erlangen systemd[1]: Stopped Postfix Mail Transport Agent. 
    [ 3425.373193] erlangen systemd[1168]: Stopped Firefox - Web Browser. 
    [ 3425.398474] erlangen systemd[1168]: Stopped Virtual filesystem service. 
    [ 3425.398573] erlangen systemd[1168]: Stopped target Basic System. 
    [ 3425.398611] erlangen systemd[1168]: Stopped target Paths. 
    [ 3425.398658] erlangen systemd[1168]: Stopped target Sockets. 
    [ 3425.398697] erlangen systemd[1168]: Stopped target Timers. 
    [ 3425.398735] erlangen systemd[1168]: Stopped Daily Cleanup of User's Temporary Directories. 
    [ 3425.399096] erlangen systemd[1168]: Stopped Create User's Volatile Files and Directories. 
    [ 3425.425414] erlangen systemd[1168]: Stopped KMail - E-Mail-Programm. 
    [ 3425.463648] erlangen systemd[1]: Stopped Initialize hardware monitoring sensors. 
    [ 3425.729909] erlangen systemd[1168]: Stopped /usr/bin/korgac. 
    [ 3425.734197] erlangen systemd[1]: Stopped User Manager for UID 1000. 
    [ 3425.862311] erlangen systemd[1]: Stopped User Runtime Directory /run/user/1000. 
    [ 3425.877658] erlangen systemd[1]: Stopped D-Bus System Message Bus. 
    [ 3426.589430] erlangen systemd[1]: Stopped X Display Manager. 
    [ 3426.609626] erlangen systemd[1]: Stopped Permit User Sessions. 
    [ 3426.674360] erlangen systemd[1]: Stopped User Login Management. 
    [ 3426.714573] erlangen systemd[1]: Stopped The Apache Webserver. 
    [ 3426.714650] erlangen systemd[1]: Stopped target Remote File Systems. 
    [ 3426.714713] erlangen systemd[1]: Stopped target System Time Synchronized. 
    [ 3426.714758] erlangen systemd[1]: Stopped target System Time Set. 
    [ 3426.715674] erlangen systemd[1]: Stopped NTP client/server. 
    [ 3426.715798] erlangen systemd[1]: Stopped target Basic System. 
    [ 3426.715866] erlangen systemd[1]: Stopped target Network. 
    [ 3426.715917] erlangen systemd[1]: Stopped target Host and Network Name Lookups. 
    [ 3426.715962] erlangen systemd[1]: Stopped target Path Units. 
    [ 3426.721369] erlangen systemd[1]: Stopped Watch /etc/sysconfig/btrfsmaintenance. 
    [ 3426.769390] erlangen systemd[1]: Stopped Watch for changes in CA certificates. 
    [ 3426.769812] erlangen systemd[1]: Stopped CUPS Scheduler. 
    [ 3426.801385] erlangen systemd[1]: Stopped Watch for changes in issue snippets. 
    [ 3426.817395] erlangen systemd[1]: Stopped Watch for changes in smartmontools sysconfig file. 
    [ 3426.817600] erlangen systemd[1]: Stopped target Slice Units. 
    [ 3426.818511] erlangen systemd[1]: Stopped target Socket Units. 
    [ 3426.819671] erlangen systemd[1]: Stopped target System Initialization. 
    [ 3426.820184] erlangen systemd[1]: Stopped target Local Encrypted Volumes. 
    [ 3426.833523] erlangen systemd[1]: Stopped Dispatch Password Requests to Console Directory Watch. 
    [ 3426.833845] erlangen systemd[1]: Stopped target Local Verity Protected Volumes. 
    [ 3426.855058] erlangen systemd[1]: Stopped Network Name Resolution. 
    [ 3426.868146] erlangen systemd[1]: Stopped Record System Boot/Shutdown in UTMP. 
    [ 3426.902688] erlangen systemd[1]: Stopped Network Configuration. 
    [ 3426.904779] erlangen systemd[1]: Stopped Apply Kernel Variables. 
    [ 3426.905144] erlangen systemd[1]: Stopped Apply Kernel Variables for 5.16.2-1-default. 
    [ 3426.905949] erlangen systemd[1]: Stopped Load Kernel Modules. 
    [ 3426.962556] erlangen systemd[1]: Stopped Security Auditing Service. 
    [ 3426.962650] erlangen systemd[1]: Stopped Create Volatile Files and Directories. 
    [ 3426.962686] erlangen systemd[1]: Stopped target Local File Systems. 
    erlangen:~ #
    Shutdown time of erlangen is 3426.96 - 3425.22 = 1.74 seconds.

    BTW:

    "Battleship (also known as Battleships or Sea Battle) is a strategy type guessing game for two players. It is played on ruled grids (paper or board) on which each player's fleet of ships (including battleships) are marked. The locations of the fleets are concealed from the other player."

    Reduce guessing by showing the locations of the fleets. When posting reduce narrating and show evidence for your claims.
    i7-6700K (2016), i5-8250U (2018), AMD Ryzen 5 3400G (2020), 5600X (2022) openSUSE Tumbleweed, KDE Plasma

  9. #19
    Join Date
    Apr 2011
    Location
    Texas USA
    Posts
    488

    Default Re: Extremely long shutdown time in a restart

    I know what the game battleship is. I don't know what your implications were in bringing that up. I posted code blocks where I could. I couldn't post code block for the 65gig messages file in a directory listing because it was already deleted.

    Here are the actions you requested to be posted.

    Code:
    (base) tom@mydesktop:~> sudo zypper search --installed-only syslog
    [sudo] password for root:  
    Loading repository data...
    Reading installed packages...
    No matching items found.
    (base) tom@mydesktop:~> 
    
    Code:
    (base) tom@mydesktop:~> du -h /var/log/journal/  
    65M     /var/log/journal/128599b179684a9b94263a31be841993
    65M     /var/log/journal/
    (base) tom@mydesktop:~>
    
    Code:
    (base) tom@mydesktop:~> sudo journalctl -b -1 -o short-monotonic -g Stopped --no-page
    r
    -- Logs begin at Wed 2022-01-26 16:21:36 CST, end at Sun 2022-01-30 07:38:20 CST. --
    [   10.419580] mydesktop systemd[1]: Stopped target Initrd Default Target.
    [   10.419672] mydesktop systemd[1]: Stopped target Basic System.
    [   10.419771] mydesktop systemd[1]: Stopped target Initrd Root Device.
    [   10.419869] mydesktop systemd[1]: Stopped target Paths.
    [   10.434067] mydesktop systemd[1]: Stopped dracut cmdline hook.
    [   10.434172] mydesktop systemd[1]: Stopped dracut ask for additional cmdline parame
    ters.
    [   10.435023] mydesktop systemd[1]: Stopped Create Static Device Nodes in /dev.
    [   10.435179] mydesktop systemd[1]: Stopped Create list of static device nodes for t
    he current kernel.
    [   13.920410] mydesktop systemd[1]: Stopped Switch Root.
    [   13.921811] mydesktop systemd[1]: Stopped target Switch Root.
    [   13.921840] mydesktop systemd[1]: Stopped target Initrd File Systems.
    [   13.921860] mydesktop systemd[1]: Stopped target Initrd Root File System.
    [   13.930263] mydesktop systemd[1]: Stopped Show Plymouth Boot Screen.
    [   13.930493] mydesktop systemd[1]: Stopped Plymouth switch root service.
    [   13.930864] mydesktop systemd[1]: Stopped Journal Service.
    [   14.056307] mydesktop systemd[1]: Stopped Entropy Daemon based on the HAVEGE algor
    ithm.
    [174189.150405] mydesktop systemd[1]: Stopped target Graphical Interface.
    [174189.150473] mydesktop systemd[1]: Stopped target Multi-User System.
    [174189.150548] mydesktop systemd[1]: Stopped target Login Prompts.
    [174189.150634] mydesktop systemd[1]: Stopped target Printer.
    [174189.150703] mydesktop systemd[1]: Stopped target Sound Card.
    [174189.150767] mydesktop systemd[1]: Stopped target Timers.
    [174189.150887] mydesktop systemd[1]: Stopped Backup of RPM database.
    [174189.150987] mydesktop systemd[1]: Stopped Backup of /etc/sysconfig.
    [174189.151076] mydesktop systemd[1]: Stopped Check if mainboard battery is Ok.
    [174189.151168] mydesktop systemd[1]: Stopped Discard unused blocks once a week.
    [174189.151262] mydesktop systemd[1]: Stopped Daily rotation of log files.
    [174189.151352] mydesktop systemd[1]: Stopped Do daily mandb update.
    [174189.151439] mydesktop systemd[1]: Stopped Daily locate database update.
    [174189.151660] mydesktop systemd[1]: Stopped Daily Cleanup of Temporary Directories.
    [174189.151751] mydesktop systemd[1]: Stopped daily update of the root trust anchor f
    or DNSSEC.
    [174189.154279] mydesktop systemd[1]: Stopped Detect if the system suffers from bsc#1
    089761.
    [174189.156715] mydesktop systemd[1]: Stopped Apply settings from /etc/sysconfig/keyb
    oard.
    [174189.157130] mydesktop systemd[1]: Stopped download broadcom firmware files needed
     for bcm43xx WLAN chips.
    [174189.166502] mydesktop systemd[1]: Stopped irqbalance daemon.
    [174189.166970] mydesktop systemd[1]: Stopped Virtual Machine and Container Registrat
    ion Service.
    [174189.167397] mydesktop systemd[1]: Stopped Accounts Service.
    [174189.167891] mydesktop systemd[1]: Stopped Virtual machine log manager.
    [174189.168580] mydesktop systemd[1]: Stopped Daemon for power management.
    [174189.169296] mydesktop systemd[1]: Stopped Manage, Install and Generate Color Prof
    iles.
    [174189.169839] mydesktop systemd[1]: Stopped Command Scheduler.
    [174189.170274] mydesktop systemd[1]: Stopped RealtimeKit Scheduling Policy Service.
    [174189.170864] mydesktop systemd[1]: Stopped Getty on tty1.
    [174189.197379] mydesktop systemd[1]: Stopped Hold until boot process finishes up.
    [174189.258096] mydesktop systemd[2110]: Stopped target GNOME X11 Session (session: g
    nome-login).
    [174189.261478] mydesktop systemd[2110]: Stopped target GNOME Session.
    [174189.261540] mydesktop systemd[2110]: Stopped target GNOME X11 Session.
    [174189.261599] mydesktop systemd[2110]: Stopped target GNOME Session (session: gnome
    -login).
    [174189.261651] mydesktop systemd[2110]: Stopped target GNOME Accessibility settings.
    [174189.261708] mydesktop systemd[2110]: Stopped target GNOME Color management.
    [174189.261759] mydesktop systemd[2110]: Stopped target GNOME Keyboard handling.
    [174189.261820] mydesktop systemd[2110]: Stopped target GNOME Media keys handling.
    [174189.261879] mydesktop systemd[2110]: Stopped target GNOME Power management handli
    ng.
    [174189.261931] mydesktop systemd[2110]: Stopped target GNOME Printer notifications.
    [174189.261995] mydesktop systemd[2110]: Stopped target GNOME RFKill handling.
    [174189.262045] mydesktop systemd[2110]: Stopped target GNOME Smartcard handling.
    [174189.262096] mydesktop systemd[2110]: Stopped target GNOME Wacom handling.
    [174189.262153] mydesktop systemd[2110]: Stopped target GNOME WWan management.
    [174189.262204] mydesktop systemd[2110]: Stopped target GNOME XSettings.
    [174189.262259] mydesktop systemd[2110]: Stopped target GNOME session X11 services.
    [174189.291768] mydesktop systemd[2110]: Stopped target Current graphical user sessio
    n.
    [174189.374420] mydesktop systemd[2110]: Stopped GNOME Smartcard handling.
    [174189.376769] mydesktop systemd[2110]: Stopped Monitor Session leader for GNOME Ses
    sion.
    [174189.420119] mydesktop systemd[2110]: Stopped GNOME RFKill handling.
    [174189.605124] mydesktop systemd[1]: Stopped Restore /run/initramfs on shutdown.
    [174190.035688] mydesktop systemd[1]: Stopped Bluetooth service.
    [174190.044734] mydesktop systemd[2110]: Stopped GNOME WWan management.
    [174190.426623] mydesktop systemd[1]: Stopped Load/Save Random Seed.
    [174190.427118] mydesktop systemd[2110]: Stopped GNOME Accessibility settings.
    [174190.676469] mydesktop systemd[1]: Stopped Machine Check Exception Logging Daemon.
    [174190.704291] mydesktop systemd[1]: Stopped X Display Manager.
    [174190.764021] mydesktop systemd[1]: Stopped Make remote CUPS printers available loc
    ally.
    [174190.808482] mydesktop systemd[1]: Stopped Postfix Mail Transport Agent.
    [174190.808835] mydesktop systemd[1]: Stopped target System Time Synchronized.
    [174190.808953] mydesktop systemd[1]: Stopped target System Time Set.
    [174190.843517] mydesktop systemd[2110]: Stopped GNOME Shell on X11.
    [174191.310265] mydesktop systemd[1]: Stopped NTP client/server.
    [174191.310717] mydesktop systemd[1]: Stopped target Host and Network Name Lookups.
    [174191.370724] mydesktop systemd[1]: Stopped Save/Restore Sound Card State.
    [174191.381383] mydesktop systemd[1]: Stopped CUPS Scheduler.
    [174191.383882] mydesktop systemd[2110]: Stopped GNOME Printer notifications.
    [174191.473133] mydesktop systemd[1]: Stopped Avahi mDNS/DNS-SD Stack.
    [174191.475421] mydesktop systemd[4305]: Stopped D-Bus User Message Bus.
    [174191.514233] mydesktop systemd[1]: Stopped Self Monitoring and Reporting Technolog
    y (SMART) Daemon.
    [174191.536920] mydesktop systemd[1]: Stopped Disk Manager.
    [174191.557897] mydesktop systemd[2110]: Stopped GNOME Keyboard handling.
    [174191.558211] mydesktop systemd[2110]: Stopped GNOME Media keys handling.
    [174191.558520] mydesktop systemd[2110]: Stopped GNOME Power management handling.
    [174191.558817] mydesktop systemd[2110]: Stopped GNOME Wacom handling.
    [174191.580658] mydesktop systemd[2110]: Stopped GNOME Color management.
    [174191.630806] mydesktop systemd[2110]: Stopped GNOME XSettings.
    [174191.631207] mydesktop systemd[2110]: Stopped target GNOME Session is initialized.
    [174191.631281] mydesktop systemd[2110]: Stopped target GNOME Session Manager is read
    y.
    [174191.631341] mydesktop systemd[2110]: Stopped target GNOME Shell on X11.
    [174191.719938] mydesktop systemd[2110]: Stopped GNOME Session Manager (session: gnom
    e-login).
    [174191.720028] mydesktop systemd[2110]: Stopped target Tasks to be run before GNOME 
    Session starts.
    [174191.720104] mydesktop systemd[2110]: Stopped target Session services which should
     run early before the graphical session is brought up.
    [174191.727056] mydesktop systemd[2110]: Stopped target Shutdown running GNOME Sessio
    n.
    [174191.808620] mydesktop systemd[2110]: Stopped D-Bus User Message Bus.
    [174192.253209] mydesktop systemd[1]: Stopped Modem Manager.
    [174193.134834] mydesktop systemd[1]: Stopped Session 1 of user tom.
    [174193.186583] mydesktop systemd[4305]: Stopped target Main User Target.
    [174194.299750] mydesktop systemd[1]: Stopped Session c1 of user gdm.
    [174194.334538] mydesktop systemd[2110]: Stopped target Main User Target.
    [174194.389324] mydesktop systemd[1]: Stopped User Login Management.
    [174281.570089] mydesktop systemd[4305]: Stopped Evolution source registry.
    [174281.570340] mydesktop systemd[4305]: Stopped D-Bus User Message Bus.
    [174281.594688] mydesktop systemd[4305]: Stopped PipeWire PulseAudio.
    [174281.668714] mydesktop systemd[4305]: Stopped Multimedia Service Session Manager.
    [174281.687996] mydesktop systemd[4305]: Stopped Multimedia Service.
    [174281.688324] mydesktop systemd[4305]: Stopped target Basic System.
    [174281.688393] mydesktop systemd[4305]: Stopped target Paths.
    [174281.688455] mydesktop systemd[4305]: Stopped target Sockets.
    [174281.688512] mydesktop systemd[4305]: Stopped target Timers.
    [174281.692991] mydesktop systemd[1]: Stopped User Manager for UID 1000.
    [174281.705649] mydesktop systemd[1]: Stopped User Runtime Directory /run/user/1000.
    [174281.901372] mydesktop systemd[2110]: Stopped PipeWire PulseAudio.
    [174281.901760] mydesktop systemd[2110]: Stopped D-Bus User Message Bus.
    [174281.933710] mydesktop systemd[2110]: Stopped Multimedia Service Session Manager.
    [174281.935331] mydesktop systemd[2110]: Stopped Multimedia Service.
    [174281.935709] mydesktop systemd[2110]: Stopped target Basic System.
    [174281.935842] mydesktop systemd[2110]: Stopped target Paths.
    [174281.935954] mydesktop systemd[2110]: Stopped target Sockets.
    [174281.936069] mydesktop systemd[2110]: Stopped target Timers.
    [174282.007371] mydesktop systemd[1]: Stopped User Manager for UID 461.
    [174282.016255] mydesktop systemd[1]: Stopped User Runtime Directory /run/user/461.
    [174282.031639] mydesktop systemd[1]: Stopped Permit User Sessions.
    [174282.031848] mydesktop systemd[1]: Stopped target User and Group Name Lookups.
    [174282.031917] mydesktop systemd[1]: Stopped target Remote File Systems.
    [174282.072935] mydesktop systemd[1]: Stopped Name Service Cache Daemon.
    [174282.082226] mydesktop systemd[1]: Stopped Login and scanning of iSCSI devices.
    [174282.082404] mydesktop systemd[1]: Stopped target Network is Online.
    [174282.082478] mydesktop systemd[1]: Stopped target Network.
    [174283.951422] mydesktop systemd[1]: Stopped wicked managed network interfaces.
    [174283.952499] mydesktop systemd[1]: Stopped wicked network nanny service.
    [174283.978759] mydesktop systemd[1]: Stopped wicked network management service daemo
    n.
    [174283.979568] mydesktop systemd[1]: Stopped wicked AutoIPv4 supplicant service.
    [174283.979932] mydesktop systemd[1]: Stopped wicked DHCPv4 supplicant service.
    [174283.980269] mydesktop systemd[1]: Stopped wicked DHCPv6 supplicant service.
    [174283.980394] mydesktop systemd[1]: Stopped target Network (Pre).
    [174284.105600] mydesktop systemd[1]: Stopped WPA Supplicant daemon.
    [174285.612951] mydesktop systemd[1]: Stopped firewalld - dynamic firewall daemon.
    [174285.622986] mydesktop systemd[1]: Stopped D-Bus System Message Bus.
    [174285.636745] mydesktop systemd[1]: Stopped Authorization Manager.
    [174285.636868] mydesktop systemd[1]: Stopped target Basic System.
    [174285.652298] mydesktop systemd[1]: Stopped Forward Password Requests to Plymouth D
    irectory Watch.
    [174285.652485] mydesktop systemd[1]: Stopped target Paths.
    [174285.740252] mydesktop systemd[1]: Stopped Watch for changes in CA certificates.
    [174285.740456] mydesktop systemd[1]: Stopped CUPS Scheduler.
    [174285.748280] mydesktop systemd[1]: Stopped Watch for changes in smartmontools sysc
    onfig file.
    [174285.748416] mydesktop systemd[1]: Stopped target Slices.
    [174285.749011] mydesktop systemd[1]: Stopped target Sockets.
    [174285.750510] mydesktop systemd[1]: Stopped target System Initialization.
    [174285.750703] mydesktop systemd[1]: Stopped target Local Encrypted Volumes.
    [174285.750769] mydesktop systemd[1]: Stopped target Swap.
    [174285.752125] mydesktop systemd[1]: Stopped Apply Kernel Variables.
    [174285.752421] mydesktop systemd[1]: Stopped Load Kernel Modules.
    [174285.799686] mydesktop systemd[1]: Stopped Update UTMP about System Boot/Shutdown.
    [174285.832522] mydesktop systemd[1]: Stopped Security Auditing Service.
    [174285.832721] mydesktop systemd[1]: Stopped Create Volatile Files and Directories.
    [174285.832797] mydesktop systemd[1]: Stopped target Local File Systems.
    [174285.939606] mydesktop systemd[1]: Stopped File System Check on /dev/disk/by-uuid/
    C93A-C87E.
    [174287.355658] mydesktop systemd[1]: Stopped File System Check on /dev/disk/by-uuid/
    e748b401-3a8f-4152-a9ea-ef540efb0230.
    [174287.776222] mydesktop systemd[1]: Stopped target Local File Systems (Pre).
    
    (base) tom@mydesktop:~>
    Still significantly longer time than yours but I can live with this as long as any anamaly is not indicative of a problem that needs correction.

    thanks again, tom kosvic

  10. #20
    Join Date
    Jan 2014
    Location
    Erlangen
    Posts
    3,991

    Default Re: Extremely long shutdown time in a restart

    Quote Originally Posted by tckosvic View Post
    Code:
    [174194.389324] mydesktop systemd[1]: Stopped User Login Management.
    [174281.570089] mydesktop systemd[4305]: Stopped Evolution source registry.

    This large gap of 87 seconds is atypical. Further investigation may be worthwhile.
    i7-6700K (2016), i5-8250U (2018), AMD Ryzen 5 3400G (2020), 5600X (2022) openSUSE Tumbleweed, KDE Plasma

Page 2 of 2 FirstFirst 12

Posting Permissions

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