orbvs
January 27, 2022, 6:02am
1
Howdy!
I’m seeing incredibly slow shutdowns on a laptop running Tumbleweed (current), into the 4 and 5 minutes. It’s not a horrible problem, but I’m curious and trying to learn what might be the culprit.
Systemd shows all services being stopped rather quickly, but then between [25.522760] when it stops some /run/user/455 service, it takes almost 2350…points(?) before it stops “target Sleep”.
It shows “Stopped target Sleep // Stopped target Suspend” multiple times during shutdown, each time taking approximately 20-30seconds. Every other stopjob takes a lot less time it seems.
Only these two targets being stopped result in massive delays (along with bluetooth, which is disabled)
Google searches return nothing but how to disable sleep and suspend.
Disk is BTRFS, encrypted with LUKS. No LVM, and lvmpolld and lvm2 have been disabled.
sudo journalctl -b -1 -o short-monotonic -g Stopped --no-pager
25.522760] dyeth systemd[1]: Stopped User Manager for UID 455.
25.537625] dyeth systemd[1]: Stopped User Runtime Directory /run/user/455.
(gap added by me for illustration)
2378.881804] dyeth systemd[1]: Stopped target Sleep.
2378.881922] dyeth systemd[1]: Stopped target Suspend.
3078.575336] dyeth systemd[1]: Stopped target Sleep.
3078.575697] dyeth systemd[1]: Stopped target Suspend.
9372.904741] dyeth systemd[2453]: Stopped target Bluetooth.
9372.911245] dyeth systemd[1]: Stopped target Bluetooth Support.
(...data omitted)
9700.575853] dyeth systemd[1]: Stopped target Sleep.
9700.576193] dyeth systemd[1]: Stopped target Suspend.
[11563.256035] dyeth systemd[1]: Stopped target Sleep.
[11563.256335] dyeth systemd[1]: Stopped target Suspend.
There’s also this Leap 15.3 thread – <https://forums.opensuse.org/showthread.php/565739-Extremely-long-shutdown-time-in-a-restart> .
Often, hidden behind Shutdown’s splash screen, is a message something like “waiting for user X process to complete
Apart from that, there’s really only your method of tracing the systemd Journal.
orbvs
January 27, 2022, 9:15pm
3
I’d love to be able to hit Esc, but that key doesn’t actually show anything–whether a bug or something broken with my setup, there is no systemd output on shutdown. On boot there is, and I can watch services start. But I cannot watch the machine shutdown.
I get a line of @^@^@^@^@^@^@^@^, the machine freezes, fans whir, and 5-8 minutes later it powers off.
Perhaps it is some firmware bug, running the AMD 4750U, which may yet have issues (in addition to its sleep problems)…
mchnz
January 28, 2022, 12:10am
4
You can treat the symptom by reducing the 90 second wait by setting DefaultTimeoutStopSec in /etc/systemd/system.conf. Something like:
...
[Manager]
...
DefaultTimeoutStopSec=20s
...
I think the cause varies. In my case I suspect it may be due to volume’s still having unterminated user processes (as per fuser --mount).
orbvs
January 28, 2022, 4:04am
5
I’ll lower the timeout and see if it affects anything. It’s curious that this seems a common (?) issue, but it’s a very tough diagnosis!
I don’t know enough about systemd just yet to go spelunking through configs for the culprit(s).
But, this can only happen if, the user has Kleopatra running – possibly minimised alongside the System Tray in the Plasma Panel.
Which possibly means that, the user had Kleopatra running at logout, possibly, with the default Plasma setting to restore all running applications at the next login …
[HR][/HR]All of which begs the question –
What on earth is Kleopatra doing after the user’s session has been killed at system shutdown?hkps://hkps.pool.sks-keyservers.net ”.log-socket ” and “S.uiserver ” – the “S.uiserver ” socket should disappear when Kleopatra is closed.
[HR][/HR]BTW, Kleopatra is recommended by the openSUSE pattern “patterns-kde-kde_pim” – if you’re a member of the “I prefer to use KDE PIM for Personal Information Management ” community then, it’ll eventually be reinstalled …
And, yes, I’m a member of the KDE PIM community – with no long-term effects – despite about 17 years of usage …
orbvs
January 28, 2022, 6:16pm
8
I don’t have anything from the KDE-PIM suite installed, unchecked that box at the installer!
Perhaps their absence causes some issues? I don’t use the PIM suite, but I don’t mind having it if there is core functionality I miss out on. SSD space is cheap, as they say!
dcurtisfra:
But, this can only happen if, the user has Kleopatra running – possibly minimised alongside the System Tray in the Plasma Panel.
Which possibly means that, the user had Kleopatra running at logout, possibly, with the default Plasma setting to restore all running applications at the next login …
[HR][/HR]All of which begs the question –
What on earth is Kleopatra doing after the user’s session has been killed at system shutdown?hkps://hkps.pool.sks-keyservers.net ”.log-socket ” and “S.uiserver ” – the “S.uiserver ” socket should disappear when Kleopatra is closed.
[HR][/HR]BTW, Kleopatra is recommended by the openSUSE pattern “patterns-kde-kde_pim” – if you’re a member of the “I prefer to use KDE PIM for Personal Information Management ” community then, it’ll eventually be reinstalled …
And, yes, I’m a member of the KDE PIM community – with no long-term effects – despite about 17 years of usage …
The user was unaware of kleopatra running in the background. kleopatra caused gpg-agent to spawn processes, which were restarted upon being killed:https://forums.opensuse.org/showthread.php/565261-90-Sekunden-stop-job-beim-Shutdown-Warum-Was?p=3100054#post3100054 https://forums.opensuse.org/showthread.php/565261-90-Sekunden-stop-job-beim-Shutdown-Warum-Was?p=3100735#post3100735
Then, it’s unlikely that, Kleopatra is installed …
If it ain’t installed, then, the cause isn’t Kleopatra …
Users may browse their slice: systemctl status user-1000.slice
The above asked questions are not an issue if you stick to ext4. It just sits there.
tom kosvic
Is this slow shutdown issue on a system with a Btrfs partition encrypted with LUKS, also an issue on systems with ext4 system partitions, with or without LUKS?
I have slow shutdown issues on a leap 15.3 ext4 unencrypted (no luks) filesystem that is being examined in another thread on this forum but the ext4 filesystem has not been implicated as part of the diagnostics.
Just my opinion, but I don’t wish a “live” filesystem as I see it as another source of anamolies which can affect a major element of your system. I think a filesystem should just lay there.
I will step out of this thread as the system that is the problem is there and can’t be changed but needs to have a problem solved.
good luck, tom kosvic
orbvs
February 1, 2022, 2:10am
16
I think there’s enough space for all BTRFS functions…the disk itself is a 2TB (1.89 TiB) Samsung.
The drive is encrypted (LUKS), along with /boot. I’m not sure if any of this below is helpful.
I’m still learning how this all works, so I apologize if my questions or responses aren’t helpful! This deep-end of Linux is still new to me, but I do enjoy it.
I have run ‘btrfs scrub /’ but am not sure if it autoruns. “Balance” seems to be meant for RAID setups, which I am not employing.
btrfs filesystem df /
Data, single: total=369.01GiB, used=367.51GiB
System, DUP: total=8.00MiB, used=64.00KiB
Metadata, DUP: total=2.00GiB, used=1.68GiB
GlobalReserve, single: total=455.16MiB, used=0.00B
btrfs filesystem usage /
Data,single: Size:369.01GiB, Used:367.51GiB (99.59%)
/dev/mapper/cr_root 369.01GiB
Metadata,DUP: Size:2.00GiB, Used:1.68GiB (83.80%)
/dev/mapper/cr_root 4.00GiB
System,DUP: Size:8.00MiB, Used:64.00KiB (0.78%)
/dev/mapper/cr_root 16.00MiB
Unallocated:
/dev/mapper/cr_root 1.45TiB
orbvs:
I think there’s enough space for all BTRFS functions…the disk itself is a 2TB (1.89 TiB) Samsung.
The drive is encrypted (LUKS), along with /boot. I’m not sure if any of this below is helpful.
I’m still learning how this all works, so I apologize if my questions or responses aren’t helpful! This deep-end of Linux is still new to me, but I do enjoy it.
I have run ‘btrfs scrub /’ but am not sure if it autoruns. “Balance” seems to be meant for RAID setups, which I am not employing.
Show the following:
**erlangen:~ #** fdisk -l
**Disk /dev/sda: 1.82 TiB, 2000398934016 bytes, 3907029168 sectors**
Disk model: CT2000BX500SSD1
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: 24B476D2-CC39-4F91-9828-2024B84EFED2
**Device ****Start**** End**** Sectors**** Size****Type**
/dev/sda1 2048 3907028991 3907026944 1.8T Linux filesystem
**Disk /dev/sdb: 3.64 TiB, 4000787030016 bytes, 7814037168 sectors**
Disk model: WDC WD40EZRX-22S
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 27C8C52A-8091-403C-ADF1-E9C791667D40
**Device ****Start**** End**** Sectors**** Size****Type**
/dev/sdb1 4096 7814035455 7814031360 3.6T Linux filesystem
**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**** Size****Type**
/dev/nvme0n1p1 2048 1050623 1048576 512M EFI System
/dev/nvme0n1p2 1050624 3907029134 3905978511 1.8T Linux filesystem
**erlangen:~ #**
**erlangen:~ #** lsblk -f
NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS
sda
└─sda1 ext4 1.0 home-SSD 5605f149-34a7-4301-9bf3-f1f177e35ed6 407.9G 73% /home-SSD
sdb
└─sdb1 ext4 1.0 HDD f5177cae-4082-44ed-9471-b99030f06866
sr0
nvme0n1
├─nvme0n1p1 vfat FAT32 19CF-0B54 510.7M 0% /boot/efi
└─nvme0n1p2 btrfs 0e58bbe5-eff7-4884-bb5d-a0aac3d8a344 1.4T 21% /var
/usr/local
/srv
/root
/opt
/home
/boot/grub2/x86_64-efi
/boot/grub2/i386-pc
/.snapshots
/
**erlangen:~ #**
**erlangen:~ #** btrfs filesystem usage -T /
Overall:
Device size: 1.82TiB
Device allocated: 404.07GiB
Device unallocated: 1.42TiB
Device missing: 0.00B
Used: 385.05GiB
Free (estimated): 1.44TiB (min: 745.91GiB)
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 381.32GiB 1.87GiB 64.00KiB
**erlangen:~ #**
orbvs
February 1, 2022, 7:22am
18
Karl,
Here are the code outputs! Lots of extra disk space. For when I finally consolidate projects.
fdisk -l
**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: 76238507-3F49-4FA9-A5C4-D352380942C2
**Device **** Start**** End**** Sectors**** Size****Type**
/dev/nvme0n1p1 2048 1050623 1048576 512M EFI System
/dev/nvme0n1p2 1050624 3902834687 3901784064 1.8T Linux filesystem
/dev/nvme0n1p3 3902834688 3907029134 4194447 2G Linux swap
**Disk /dev/mapper/cr_root: 1.82 TiB, 1997711343616 bytes, 3901779968 sectors**
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
**Disk /dev/mapper/cr_swap: 2 GiB, 2145459712 bytes, 4190351 sectors**
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
----
lsblk -f
[FONT=monospace]NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS
nvme0n1
├─nvme0n1p1 vfat FAT32 C48D-B7DE 505.9M 1% /boot/efi
├─nvme0n1p2 crypto_LUKS 1 9f37ef19-c3e7-4f28-bb3a-c45b42a8ebfb
│ └─cr_root btrfs 2b8997a7-562e-4ba5-acbc-1c922daaaacb 1.5T 20% /var
│ /usr/local
│ /srv
│ /root
│ /opt
│ /home
│ /boot/grub2/x86_64-efi
│ /boot/grub2/i386-pc
│ /.snapshots
│ /
└─nvme0n1p3 crypto_LUKS 1 07ddcdc3-666b-4c8f-ac2f-9c02ea6a17ee
└─cr_swap swap 1 2c807fce-4110-4f2a-8aa0-ab5e9838eef5 [SWAP]
----
btrfs filesystem usage -T /
Overall:
Device size: 1.82TiB
Device allocated: 376.02GiB
Device unallocated: 1.45TiB
Device missing: 0.00B
Used: 371.68GiB
Free (estimated): 1.45TiB (min: 744.13GiB)
Free (statfs, df): 1.45TiB
Data ratio: 1.00
Metadata ratio: 2.00
Global reserve: 458.20MiB (used: 0.00B)
Multiple profiles: no
Data Metadata System
Id Path single DUP DUP Unallocated
-- ------------------- --------- -------- -------- -----------
1 /dev/mapper/cr_root 370.01GiB 6.00GiB 16.00MiB 1.45TiB
-- ------------------- --------- -------- -------- -----------
Total 370.01GiB 3.00GiB 8.00MiB 1.45TiB
Used 368.12GiB 1.78GiB 64.00KiB
[/FONT]
File system is fine. What about shutdown?
**erlangen:~ #** journalctl -b -1 -o short-monotonic --no-pager -g Stopped
3.058854] erlangen systemd[1]: Stopped target Initrd Default Target.
3.058884] erlangen systemd[1]: Stopped target Basic System.
...
5194.960899] erlangen systemd[1]: Stopped target Graphical Interface.
5194.960983] erlangen systemd[1]: Stopped target Multi-User System.
5194.961048] erlangen systemd[1]: Stopped target Login Prompts.
5194.961119] erlangen systemd[1]: Stopped target Sound Card.
5194.961192] erlangen systemd[1]: Stopped target Timer Units.
5194.961348] erlangen systemd[1]: Stopped Backup of /home.
5194.961480] erlangen systemd[1]: Stopped Backup of RPM database.
5194.961629] erlangen systemd[1]: Stopped Backup of /etc/sysconfig.
5194.961749] erlangen systemd[1]: Stopped Balance block groups on a btrfs filesystem.
5194.962120] erlangen systemd[1]: Stopped Scrub btrfs filesystem, verify block checksums.
5194.962260] erlangen systemd[1]: Stopped Check if mainboard battery is Ok.
5194.962383] erlangen systemd[1]: Stopped Discard unused blocks once a week.
5194.962506] erlangen systemd[1]: Stopped Daily rotation of log files.
5194.962970] erlangen systemd[1]: Stopped Daily man-db regeneration.
5194.963135] erlangen systemd[1]: Stopped Daily locate database update.
5194.963393] erlangen systemd[1]: Stopped Systemd timer to update the system daily with PackageKit.
5194.963629] erlangen systemd[1]: Stopped Daily Cleanup of Snapper Snapshots.
5194.963753] erlangen systemd[1]: Stopped Timeline of Snapper Snapshots.
5194.963874] erlangen systemd[1]: Stopped Daily Cleanup of Temporary Directories.
5194.965180] erlangen systemd[1]: Stopped auditd rules generation.
5194.965871] erlangen systemd[1]: Stopped Apply settings from /etc/sysconfig/keyboard.
5194.967139] erlangen systemd[1]: Stopped hd-idle disk spindown service.
5194.967357] erlangen systemd[1]: Stopped irqbalance daemon.
5194.967475] erlangen systemd[1]: Stopped Machine Check Exception Logging Daemon.
5194.967578] erlangen systemd[1]: Stopped CUPS Scheduler.
5194.967945] erlangen systemd[1]: Stopped A remote-mail retrieval utility.
5194.968135] erlangen systemd[1]: Stopped Save/Restore Sound Card State.
5194.968308] erlangen systemd[1]: Stopped Restore /run/initramfs on shutdown.
5194.968994] erlangen systemd[1]: Stopped Load/Save Random Seed.
5194.980817] erlangen systemd[1]: Stopped Start fetchmail.
5194.983177] erlangen systemd[1]: Stopped Getty on tty1.
5194.983714] erlangen systemd[1]: Stopped Command Scheduler.
5194.984065] erlangen systemd[1]: Stopped Authorization Manager.
5194.984627] erlangen systemd[1]: Stopped Hold until boot process finishes up.
5194.987583] erlangen systemd[1]: Stopped MiniDLNA is a DLNA/UPnP-AV server software.
5194.989775] erlangen systemd[1]: Stopped target Network is Online.
5195.036375] erlangen systemd[1]: Stopped RealtimeKit Scheduling Policy Service.
5195.036686] erlangen systemd[1]: Stopped Disk Manager.
5195.036889] erlangen systemd[1]: Stopped Session 2 of User karl.
5195.038234] erlangen systemd[1181]: Stopped Konsole - Terminal.
5195.038423] erlangen systemd[1181]: Stopped target Main User Target.
5195.039044] erlangen systemd[1181]: Stopped Save jAlbum Project Files.
5195.039097] erlangen systemd[1181]: Stopped Accessibility services bus.
5195.039194] erlangen systemd[1181]: Stopped Virtual filesystem service.
5195.039338] erlangen systemd[1181]: Stopped D-Bus User Message Bus.
5195.039417] erlangen systemd[1181]: Stopped User preferences database.
5195.042474] erlangen systemd[1181]: Stopped Firefox - Web Browser.
5195.050975] erlangen systemd[1181]: Stopped Sound Service.
5195.051392] erlangen systemd[1181]: Stopped target Basic System.
5195.051457] erlangen systemd[1181]: Stopped target Paths.
5195.051537] erlangen systemd[1181]: Stopped target Sockets.
5195.051605] erlangen systemd[1181]: Stopped target Timers.
5195.051667] erlangen systemd[1181]: Stopped Daily Cleanup of User's Temporary Directories.
5195.052026] erlangen systemd[1181]: Stopped Create User's Volatile Files and Directories.
5195.069714] erlangen systemd[1]: Stopped Postfix Mail Transport Agent.
5195.123252] erlangen systemd[1]: Stopped Initialize hardware monitoring sensors.
5195.125040] erlangen systemd[1]: Stopped Daemon for power management.
5195.132824] erlangen systemd[1181]: Stopped KMail - E-Mail-Programm.
5195.358059] erlangen systemd[1181]: Stopped /usr/bin/korgac.
5195.378299] erlangen systemd[1]: Stopped User Manager for UID 1000.
5195.440197] erlangen systemd[1]: Stopped User Runtime Directory /run/user/1000.
5195.518289] erlangen systemd[1]: Stopped D-Bus System Message Bus.
5196.378456] erlangen systemd[1]: Stopped X Display Manager.
5196.387365] erlangen systemd[1]: Stopped Permit User Sessions.
5196.441023] erlangen systemd[1]: Stopped The Apache Webserver.
5196.441181] erlangen systemd[1]: Stopped target Remote File Systems.
5196.441255] erlangen systemd[1]: Stopped target System Time Synchronized.
5196.441302] erlangen systemd[1]: Stopped target System Time Set.
5196.442223] erlangen systemd[1]: Stopped NTP client/server.
5196.442404] erlangen systemd[1]: Stopped target Network.
5196.442479] erlangen systemd[1]: Stopped target Host and Network Name Lookups.
5196.451959] erlangen systemd[1]: Stopped User Login Management.
5196.453533] erlangen systemd[1]: Stopped Network Name Resolution.
5196.454319] erlangen systemd[1]: Stopped target Basic System.
5196.454738] erlangen systemd[1]: Stopped target Path Units.
5196.477605] erlangen systemd[1]: Stopped Watch /etc/sysconfig/btrfsmaintenance.
5196.517604] erlangen systemd[1]: Stopped Watch for changes in CA certificates.
5196.518070] erlangen systemd[1]: Stopped CUPS Scheduler.
5196.553695] erlangen systemd[1]: Stopped Watch for changes in issue snippets.
5196.569603] erlangen systemd[1]: Stopped Watch for changes in smartmontools sysconfig file.
5196.569882] erlangen systemd[1]: Stopped target Slice Units.
5196.570847] erlangen systemd[1]: Stopped target Socket Units.
5196.572029] erlangen systemd[1]: Stopped target System Initialization.
5196.572527] erlangen systemd[1]: Stopped target Local Encrypted Volumes.
5196.585610] erlangen systemd[1]: Stopped Dispatch Password Requests to Console Directory Watch.
5196.585873] erlangen systemd[1]: Stopped target Local Verity Protected Volumes.
5196.600865] erlangen systemd[1]: Stopped Network Configuration.
5196.602656] erlangen systemd[1]: Stopped Apply Kernel Variables.
5196.603014] erlangen systemd[1]: Stopped Apply Kernel Variables for 5.16.2-1-default.
5196.603350] erlangen systemd[1]: Stopped Load Kernel Modules.
5196.610380] erlangen systemd[1]: Stopped Record System Boot/Shutdown in UTMP.
5196.708930] erlangen systemd[1]: Stopped Security Auditing Service.
5196.709227] erlangen systemd[1]: Stopped Create Volatile Files and Directories.
5196.709262] erlangen systemd[1]: Stopped target Local File Systems.
**erlangen:~ #**
orbvs
February 1, 2022, 5:18pm
20
For shutdown, I see the same weird “systemd Stopped Sleep/Suspend” as before:
For journalctl -b -X the outcome is very similar. Everything stops within a few seconds, then these “Sleep/Suspend” targets take a very long time.
journalctl -b -1 -o short-monotonic --no-pager -g Stopped
11.085549] dyeth systemd[1]: Stopped target Initrd Default Target.
11.085628] dyeth systemd[1]: Stopped target Basic System.
11.085679] dyeth systemd[1]: Stopped target Initrd Root Device.
11.085737] dyeth systemd[1]: Stopped target Initrd /usr File System.
11.085784] dyeth systemd[1]: Stopped target Path Units.
11.085833] dyeth systemd[1]: Stopped target Remote Encrypted Volumes.
11.085895] dyeth systemd[1]: Stopped target Remote File Systems.
11.085943] dyeth systemd[1]: Stopped target Preparation for Remote File Systems.
11.086002] dyeth systemd[1]: Stopped target Slice Units.
11.086049] dyeth systemd[1]: Stopped target Socket Units.
11.086112] dyeth systemd[1]: Stopped target System Initialization.
11.086164] dyeth systemd[1]: Stopped target Local Encrypted Volumes.
11.086217] dyeth systemd[1]: Stopped target Swaps.
11.086273] dyeth systemd[1]: Stopped target Timer Units.
11.086387] dyeth systemd[1]: Stopped dracut initqueue hook.
11.088181] dyeth systemd[1]: Stopped Apply Kernel Variables.
11.088333] dyeth systemd[1]: Stopped Load Kernel Modules.
11.088463] dyeth systemd[1]: Stopped Create Volatile Files and Directories.
11.088553] dyeth systemd[1]: Stopped target Local File Systems.
11.088645] dyeth systemd[1]: Stopped Coldplug All udev Devices.
11.089753] dyeth systemd[1]: Stopped Forward Password Requests to Plymouth.
11.111199] dyeth systemd[1]: Stopped Rule-based Manager for Device Events and Files.
11.111961] dyeth systemd[1]: Stopped dracut pre-udev hook.
11.112044] dyeth systemd[1]: Stopped dracut cmdline hook.
11.112130] dyeth systemd[1]: Stopped dracut ask for additional cmdline parameters.
11.112527] dyeth systemd[1]: Stopped Create Static Device Nodes in /dev.
11.112720] dyeth systemd[1]: Stopped Create List of Static Device Nodes.
11.476137] dyeth systemd[1]: Stopped Switch Root.
11.477565] dyeth systemd[1]: Stopped target Switch Root.
11.477580] dyeth systemd[1]: Stopped target Initrd File Systems.
11.477595] dyeth systemd[1]: Stopped target Initrd Root File System.
11.483936] dyeth systemd[1]: Stopped Show Plymouth Boot Screen.
11.484157] dyeth systemd[1]: Stopped Plymouth switch root service.
11.484236] dyeth systemd[1]: Stopped File System Check on Root Device.
11.484290] dyeth systemd[1]: Stopped Journal Service.
11.484332] dyeth systemd[1]: Stopped Entropy Daemon based on the HAVEGE algorithm.
18.061513] HOSTNAME systemd[1]: Stopped NordVPN Daemon.
87.070292] HOSTNAME systemd[2316]: Stopped target Main User Target.
87.072640] HOSTNAME systemd[2316]: Stopped D-Bus User Message Bus.
87.072831] HOSTNAME systemd[2316]: Stopped target Basic System.
87.072951] HOSTNAME systemd[2316]: Stopped target Paths.
87.073038] HOSTNAME systemd[2316]: Stopped target Sockets.
87.073127] HOSTNAME systemd[2316]: Stopped target Timers.
87.073194] HOSTNAME systemd[2316]: Stopped Daily Cleanup of User's Temporary Directories.
87.074079] HOSTNAME systemd[2316]: Stopped Create User's Volatile Files and Directories.
87.080235] HOSTNAME systemd[1]: Stopped User Manager for UID 455.
87.094146] HOSTNAME systemd[1]: Stopped User Runtime Directory /run/user/455.
96.818152] HOSTNAME systemd[1]: Stopped NordVPN Daemon.
1451.897330] HOSTNAME systemd[1]: Stopped target Sleep.
1451.897537] HOSTNAME systemd[1]: Stopped target Suspend.
1455.584389] HOSTNAME systemd[1]: Stopped target Sleep.
1455.584513] HOSTNAME systemd[1]: Stopped target Suspend.
