Results 1 to 10 of 10

Thread: RealTimeKit Scheduling Policy Service Delays shutdown for 3 minutes. WTF

  1. #1
    Join Date
    Nov 2008
    Posts
    2,393
    Blog Entries
    1

    Default RealTimeKit Scheduling Policy Service Delays shutdown for 3 minutes. WTF

    It has been normal for me to have to wait for a shutdown while some service or other takes 1 1/2 minutes before closing down but the captioned issue is new for me and is timed at 3 minutes.
    Please could somebody help me turn this off or change the timer setting.
    Budge.
    Last edited by malcolmlewis; 25-Jun-2022 at 17:21. Reason: Fix thread title

  2. #2

    Default Re: RealTimeKit Scheduling Policy Service Delays shutdown for 3 minutes. WTF

    Hi,
    See post number 3 of this thread.
    https://forums.opensuse.org/showthread.php/571409-Ninety-second-shutdown-delay-quot-A-stop-job-is-running-for-system-logging-service-quot

    The option is already there you just have to reduce the number & un-comment it.
    Last edited by malcolmlewis; 25-Jun-2022 at 17:22. Reason: Fix thread title
    People who do not break things first will never learn to create anything

  3. #3
    Join Date
    Jun 2008
    Location
    East of Podunk
    Posts
    33,243
    Blog Entries
    15

    Default Re: RealTimeKit Scheduling Policy Service Delays shutdown for 3 minutes. WTF

    Quote Originally Posted by conram View Post
    Hi,
    See post number 3 of this thread.
    https://forums.opensuse.org/showthread.php/571409-Ninety-second-shutdown-delay-quot-A-stop-job-is-running-for-system-logging-service-quot

    The option is already there you just have to reduce the number & un-comment it.
    Hi
    That may cause more issues, better to identify the real cause of the slow shutdown. It could be syncing disks, or remote files systems etc...
    Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
    SUSE SLE, openSUSE Leap/Tumbleweed (x86_64) | GNOME DE
    If you find this post helpful and are logged into the web interface,
    please show your appreciation and click on the star below... Thanks!

  4. #4

    Default Re: RealTimeKit Scheduling Policy Service Delays shutdown for 3 minutes. WTF

    Quote Originally Posted by malcolmlewis View Post
    Hi
    That may cause more issues, better to identify the real cause of the slow shutdown. It could be syncing disks, or remote files systems etc...
    Hi,
    Thanks for that, I am one of those who just can't really wait shutting down quickly.
    Good to see warnings like this, it helps me slowdown.
    People who do not break things first will never learn to create anything

  5. #5
    Join Date
    Jun 2008
    Location
    East of Podunk
    Posts
    33,243
    Blog Entries
    15

    Default Re: RealTimeKit Scheduling Policy Service Delays shutdown for 3 minutes. WTF

    Hi
    So look at the previous journal to investigate (the -e starts at the end);

    Code:
    journalctl -b -1 -e
    Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
    SUSE SLE, openSUSE Leap/Tumbleweed (x86_64) | GNOME DE
    If you find this post helpful and are logged into the web interface,
    please show your appreciation and click on the star below... Thanks!

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

    Default Re: RealTimeKit Scheduling Policy Service Delays shutdown for 3 minutes. WTF

    Quote Originally Posted by Budgie2 View Post
    It has been normal for me to have to wait for a shutdown while some service or other takes 1 1/2 minutes before closing down but the captioned issue is new for me and is timed at 3 minutes. Please could somebody help me turn this off or change the timer setting.
    You may turn this off by hitting the reset button. A more canonical option is to find the service causing the timeout. To my experience many users have strong preconceptions how their system works and are reluctant to use a systematic approach. This may result in lengthy and frustrating discussions.

    There is good news: On a properly maintained machine rtkit-daemon.service starts and stops really fast:
    Code:
    erlangen:~ # journalctl -b -1 -u rtkit-daemon.service -p6 -o short-monotonic  
    [   14.728510] erlangen systemd[1]: Starting RealtimeKit Scheduling Policy Service... 
    [   14.746404] erlangen systemd[1]: Started RealtimeKit Scheduling Policy Service. 
    [   14.748488] erlangen rtkit-daemon[1282]: Successfully made thread 1272 of process 1272 owned by '1000' high priority at nice level -11. 
    [   14.749253] erlangen rtkit-daemon[1282]: Successfully made thread 1274 of process 1274 owned by '1000' high priority at nice level -11. 
    [   14.752694] erlangen rtkit-daemon[1282]: Successfully made thread 1315 of process 1274 owned by '1000' RT at priority 20. 
    [   14.753600] erlangen rtkit-daemon[1282]: Successfully made thread 1318 of process 1272 owned by '1000' RT at priority 20. 
    [   16.534856] erlangen rtkit-daemon[1282]: Successfully made thread 2157 of process 2157 owned by '1000' high priority at nice level -11. 
    [   16.540465] erlangen rtkit-daemon[1282]: Successfully made thread 2167 of process 1583 owned by '1000' RT at priority 10. 
    [   16.542570] erlangen rtkit-daemon[1282]: Successfully made thread 2171 of process 2157 owned by '1000' RT at priority 20. 
    [ 5048.423429] erlangen rtkit-daemon[1282]: Successfully made thread 21873 of process 21449 owned by '1000' RT at priority 10. 
    [ 5367.857493] erlangen systemd[1]: Stopping RealtimeKit Scheduling Policy Service... 
    [ 5367.992256] erlangen systemd[1]: rtkit-daemon.service: Deactivated successfully. 
    [ 5367.992339] erlangen systemd[1]: Stopped RealtimeKit Scheduling Policy Service. 
    erlangen:~ #
    Shutdown of rtkit-daemon.service is complete after 0.14 seconds.

    You may search for the process causing the timeout and have corrective actions applied: https://forums.opensuse.org/showthre...own-Warum-Was/

    Proper maintenance of the system always results in a smooth and fast shutdown:
    Code:
    erlangen:~ # journalctl -b -1 -u init.scope -g Stopped -o short-monotonic --no-pager  
    [    6.618981] erlangen systemd[1]: Stopped target Initrd Default Target. 
    [    6.619019] erlangen systemd[1]: Stopped target Basic System. 
    [    6.619053] erlangen systemd[1]: Stopped target Initrd Root Device. 
    ....
    [ 5367.842936] erlangen systemd[1]: Stopped target Graphical Interface. 
    [ 5367.843050] erlangen systemd[1]: Stopped target Multi-User System. 
    [ 5367.843154] erlangen systemd[1]: Stopped target Login Prompts. 
    [ 5367.843268] erlangen systemd[1]: Stopped target Sound Card. 
    [ 5367.843651] erlangen systemd[1]: Stopped target Timer Units. 
    [ 5367.843751] erlangen systemd[1]: Stopped Backup of /home. 
    [ 5367.843817] erlangen systemd[1]: Stopped Backup of RPM database. 
    [ 5367.843880] erlangen systemd[1]: Stopped Backup of /etc/sysconfig. 
    [ 5367.843952] erlangen systemd[1]: Stopped Balance block groups on a btrfs filesystem. 
    [ 5367.844017] erlangen systemd[1]: Stopped Scrub btrfs filesystem, verify block checksums. 
    [ 5367.844082] erlangen systemd[1]: Stopped Check if mainboard battery is Ok. 
    [ 5367.844169] erlangen systemd[1]: Stopped Systemd timer to update the system daily with Zypper. 
    [ 5367.844379] erlangen systemd[1]: Stopped Discard unused blocks once a week. 
    [ 5367.844520] erlangen systemd[1]: Stopped Daily rotation of log files. 
    [ 5367.847120] erlangen systemd[1]: Stopped Daily man-db regeneration. 
    [ 5367.847493] erlangen systemd[1]: Stopped Daily locate database update. 
    [ 5367.847624] erlangen systemd[1]: Stopped Daily Cleanup of Snapper Snapshots. 
    [ 5367.847717] erlangen systemd[1]: Stopped Daily Cleanup of Temporary Directories. 
    [ 5367.847897] erlangen systemd[1]: Stopped auditd rules generation. 
    [ 5367.848331] erlangen systemd[1]: Stopped Apply settings from /etc/sysconfig/keyboard. 
    [ 5367.865952] erlangen systemd[1]: Stopped hd-idle disk spindown service. 
    [ 5367.866309] erlangen systemd[1]: Stopped irqbalance daemon. 
    [ 5367.866601] erlangen systemd[1]: Stopped OpenSSH Daemon. 
    [ 5367.866827] erlangen systemd[1]: Stopped Machine Check Exception Logging Daemon. 
    [ 5367.867139] erlangen systemd[1]: Stopped Restore /run/initramfs on shutdown. 
    [ 5367.868871] erlangen systemd[1]: Stopped Load/Save Random Seed. 
    [ 5367.876841] erlangen systemd[1]: Stopped Getty on tty1. 
    [ 5367.877130] erlangen systemd[1]: Stopped Command Scheduler. 
    [ 5367.877619] erlangen systemd[1]: Stopped Session 7 of User karl. 
    [ 5367.877762] erlangen systemd[1]: Stopped Hold until boot process finishes up. 
    [ 5367.896127] erlangen systemd[1]: Stopped Disk Manager. 
    [ 5367.896977] erlangen systemd[1]: Stopped Authorization Manager. 
    [ 5367.923912] erlangen systemd[1]: Stopped A remote-mail retrieval utility. 
    [ 5367.924230] erlangen systemd[1]: Stopped CUPS Scheduler. 
    [ 5367.924498] erlangen systemd[1]: Stopped Daemon for power management. 
    [ 5367.925044] erlangen systemd[1]: Stopped Start fetchmail. 
    [ 5367.955975] erlangen systemd[1]: Stopped Initialize hardware monitoring sensors. 
    [ 5367.991992] erlangen systemd[1]: Stopped MiniDLNA is a DLNA/UPnP-AV server software. 
    [ 5367.992339] erlangen systemd[1]: Stopped RealtimeKit Scheduling Policy Service. 
    [ 5367.992800] erlangen systemd[1]: Stopped target Network is Online. 
    [ 5368.059982] erlangen systemd[1]: Stopped Postfix Mail Transport Agent. 
    [ 5368.203859] erlangen systemd[1]: Stopped User Manager for UID 1000. 
    [ 5368.268448] erlangen systemd[1]: Stopped User Runtime Directory /run/user/1000. 
    [ 5368.287800] erlangen systemd[1]: Stopped D-Bus System Message Bus. 
    [ 5368.336110] erlangen systemd[1]: Stopped Start the rsync server daemon. 
    [ 5368.767564] erlangen systemd[1]: Stopped X Display Manager. 
    [ 5368.771352] erlangen systemd[1]: Stopped Permit User Sessions. 
    [ 5368.807611] erlangen systemd[1]: Stopped The Apache Webserver. 
    [ 5368.807738] erlangen systemd[1]: Stopped target Remote File Systems. 
    [ 5368.807801] erlangen systemd[1]: Stopped target System Time Synchronized. 
    [ 5368.807847] erlangen systemd[1]: Stopped target System Time Set. 
    [ 5368.808510] erlangen systemd[1]: Stopped NTP client/server. 
    [ 5368.808601] erlangen systemd[1]: Stopped target Network. 
    [ 5368.808639] erlangen systemd[1]: Stopped target Host and Network Name Lookups. 
    [ 5368.828579] erlangen systemd[1]: Stopped Network Name Resolution. 
    [ 5368.836297] erlangen systemd[1]: Stopped User Login Management. 
    [ 5368.836409] erlangen systemd[1]: Stopped target Basic System. 
    [ 5368.836456] erlangen systemd[1]: Stopped target Path Units. 
    [ 5368.855794] erlangen systemd[1]: Stopped Watch /etc/sysconfig/btrfsmaintenance. 
    [ 5368.907993] erlangen systemd[1]: Stopped Watch for changes in CA certificates. 
    [ 5368.908160] erlangen systemd[1]: Stopped CUPS Scheduler. 
    [ 5368.939975] erlangen systemd[1]: Stopped Watch for changes in issue snippets. 
    [ 5368.940117] erlangen systemd[1]: Stopped target Slice Units. 
    [ 5368.940205] erlangen systemd[1]: Stopped target Socket Units. 
    [ 5368.940365] erlangen systemd[1]: Stopped target System Initialization. 
    [ 5368.940432] erlangen systemd[1]: Stopped target Local Encrypted Volumes. 
    [ 5368.955968] erlangen systemd[1]: Stopped Dispatch Password Requests to Console Directory Watch. 
    [ 5368.956101] erlangen systemd[1]: Stopped target Local Integrity Protected Volumes. 
    [ 5368.956141] erlangen systemd[1]: Stopped target Local Verity Protected Volumes. 
    [ 5368.958265] erlangen systemd[1]: Stopped Network Configuration. 
    [ 5368.958553] erlangen systemd[1]: Stopped Apply Kernel Variables. 
    [ 5368.958602] erlangen systemd[1]: Stopped Apply Kernel Variables for 5.18.4-1-default. 
    [ 5368.958648] erlangen systemd[1]: Stopped Load Kernel Modules. 
    [ 5368.960311] erlangen systemd[1]: Stopped Record System Boot/Shutdown in UTMP. 
    [ 5369.016126] erlangen systemd[1]: Stopped Security Auditing Service. 
    [ 5369.016288] erlangen systemd[1]: Stopped Create Volatile Files and Directories. 
    [ 5369.016314] erlangen systemd[1]: Stopped target Local File Systems. 
    [ 5369.021169] erlangen systemd[1]: Stopped target Swaps. 
    erlangen:~ #
    Total shutdown time is 1.18 seconds.

    i7-6700K (2016), i5-8250U (2018), AMD Ryzen 5 3400G (2020), 5600X (2022) openSUSE Tumbleweed, KDE Plasma

  7. #7
    Join Date
    Nov 2008
    Posts
    2,393
    Blog Entries
    1

    Default Re: RealTimeKit Scheduling Policy Service Delays shutdown for 3 minutes. WTF

    Hi and many thanks for the replies. I am firmly of the opinion that if there is a problem it should be fixed rather than plastered over so I started with Malcolm's suggestion and immediately ran into a problem trying to look into the result of the command:-

    Code:
    alastair@IBMW530:~> sudo journalctl -b -l -e 
    [sudo] password for root:  
    Jun 26 09:42:19 IBMW530 rtkit-daemon[5134]: Successfully made thread 12589 of process 12473 owned by 'alastair' RT a>
    Jun 26 09:42:19 IBMW530 rtkit-daemon[5134]: Supervising 8 threads of 5 processes of 1 users.
    Jun 26 09:42:20 IBMW530 rtkit-daemon[5134]: Supervising 8 threads of 5 processes of 1 users.
    Jun 26 09:42:20 IBMW530 rtkit-daemon[5134]: Supervising 8 threads of 5 processes of 1 users.
    Jun 26 09:42:26 IBMW530 nscd[868]: 868 checking for monitored file `/etc/services': No such file or directory
    Jun 26 09:42:34 IBMW530 plasmashell[12473]: IPDL protocol error: Handler returned error code! 
    Jun 26 09:42:34 IBMW530 plasmashell[12473]: ###!!! [Parent][DispatchAsyncMessage] Error: PClientManager::Msg_ExpectF>
    Jun 26 09:42:34 IBMW530 plasmashell[12473]: IPDL protocol error: Handler returned error code! 
    Jun 26 09:42:34 IBMW530 plasmashell[12473]: ###!!! [Parent][DispatchAsyncMessage] Error: PClientManager::Msg_ForgetF>
    Jun 26 09:42:41 IBMW530 nscd[868]: 868 checking for monitored file `/etc/services': No such file or directory
    Jun 26 09:42:42 IBMW530 rtkit-daemon[5134]: Supervising 8 threads of 5 processes of 1 users.
    Jun 26 09:42:42 IBMW530 rtkit-daemon[5134]: Supervising 8 threads of 5 processes of 1 users.
    Jun 26 09:49:07 IBMW530 systemd[4559]: Started Konsole - Terminal. 
    Jun 26 09:49:14 IBMW530 pcloud[5013]: Update for linux-x64-prod-v1.9.9 is not available 
    Jun 26 09:49:38 IBMW530 sudo[12877]: alastair : TTY=pts/1 ; PWD=/home/alastair ; USER=root ; COMMAND=/usr/bin/journa>
    Jun 26 09:49:38 IBMW530 sudo[12877]: pam_unix(sudo:session): session opened for user root(uid=0) by alastair(uid=100>
    lines 985-1000/1000 (END)
    
    Two questions immediately come to mind,
    Why the 1000 line limit?
    Baloo is making hard work of this as it seems to be checking rather a large number of my photo album files, which number several thousand. If it starts on my music database tens of thousands. Is this to be expected and this process alone could take some time!!!?

  8. #8
    Join Date
    Nov 2008
    Posts
    2,393
    Blog Entries
    1

    Default Re: RealTimeKit Scheduling Policy Service Delays shutdown for 3 minutes. WTF

    Hi Karl,
    I ran both of your suggested commands and didn't see anything I could recognise as a possible cause of my problem:-

    Code:
    alastair@IBMW530:~> sudo journalctl -b -1 -u rtkit-daemon.service -p6 -o short-monotonic 
    [sudo] password for root:  
    [   31.701051] IBMW530 systemd[1]: Starting RealtimeKit Scheduling Policy Service... 
    [   31.832331] IBMW530 systemd[1]: Started RealtimeKit Scheduling Policy Service. 
    [   31.836252] IBMW530 rtkit-daemon[2336]: Successfully made thread 2325 of process 2325 owned by 'alastair' high pr>
    [   31.838438] IBMW530 rtkit-daemon[2336]: Successfully made thread 2328 of process 2328 owned by 'alastair' high pr>
    [   31.840315] IBMW530 rtkit-daemon[2336]: Successfully made thread 2326 of process 2326 owned by 'alastair' high pr>
    [   31.862246] IBMW530 rtkit-daemon[2336]: Successfully made thread 2345 of process 2326 owned by 'alastair' RT at p>
    [   31.869852] IBMW530 rtkit-daemon[2336]: Successfully made thread 2348 of process 2328 owned by 'alastair' RT at p>
    [   31.870847] IBMW530 rtkit-daemon[2336]: Successfully made thread 2350 of process 2325 owned by 'alastair' RT at p>
    [   40.424260] IBMW530 rtkit-daemon[2336]: Successfully made thread 2916 of process 2748 owned by 'alastair' RT at p>
    [  561.780419] IBMW530 systemd[1]: Stopping RealtimeKit Scheduling Policy Service... 
    [  561.848699] IBMW530 systemd[1]: rtkit-daemon.service: Deactivated successfully. 
    [  561.848840] IBMW530 systemd[1]: Stopped RealtimeKit Scheduling Policy Service. 
    lines 1-12/12 (END)
    
    Code:
    alastair@IBMW530:~> sudo journalctl -b -1 -u init.scope -g Stopped -o short-monotonic --no-pager 
    [sudo] password for root:  
    [    5.272331] IBMW530 systemd[1]: Stopped target Initrd Default Target. 
    [    5.272445] IBMW530 systemd[1]: Stopped target Basic System. 
    [    5.275150] IBMW530 systemd[1]: Stopped target Initrd Root Device. 
    [    5.277816] IBMW530 systemd[1]: Stopped target Initrd /usr File System. 
    [    5.280386] IBMW530 systemd[1]: Stopped target Path Units. 
    [    5.282878] IBMW530 systemd[1]: Stopped target Remote File Systems. 
    [    5.285258] IBMW530 systemd[1]: Stopped target Preparation for Remote File Systems. 
    [    5.286397] IBMW530 systemd[1]: Stopped target Slice Units. 
    [    5.287449] IBMW530 systemd[1]: Stopped target Socket Units. 
    [    5.288538] IBMW530 systemd[1]: Stopped target System Initialization. 
    [    5.289569] IBMW530 systemd[1]: Stopped target Swaps. 
    [    5.290583] IBMW530 systemd[1]: Stopped target Timer Units. 
    [    5.291705] IBMW530 systemd[1]: Stopped dracut initqueue hook. 
    [    5.293874] IBMW530 systemd[1]: Stopped Apply Kernel Variables. 
    [    5.295524] IBMW530 systemd[1]: Stopped Load Kernel Modules. 
    [    5.297696] IBMW530 systemd[1]: Stopped Create Volatile Files and Directories. 
    [    5.299808] IBMW530 systemd[1]: Stopped target Local File Systems. 
    [    5.301881] IBMW530 systemd[1]: Stopped target Preparation for Local File Systems. 
    [    5.304051] IBMW530 systemd[1]: Stopped Coldplug All udev Devices. 
    [    5.330903] IBMW530 systemd[1]: Stopped Rule-based Manager for Device Events and Files. 
    [    5.334666] IBMW530 systemd[1]: Stopped dracut pre-udev hook. 
    [    5.336913] IBMW530 systemd[1]: Stopped dracut cmdline hook. 
    [    5.337763] IBMW530 systemd[1]: Stopped dracut ask for additional cmdline parameters. 
    [    5.338616] IBMW530 systemd[1]: Stopped Create Static Device Nodes in /dev. 
    [    5.338752] IBMW530 systemd[1]: Stopped Create List of Static Device Nodes. 
    [   36.615294] IBMW530 systemd[1]: Stopped User Manager for UID 460. 
    [   36.698336] IBMW530 systemd[1]: Stopped User Runtime Directory /run/user/460. 
    [  561.765017] IBMW530 systemd[1]: Stopped target Bluetooth Support. 
    [  561.765301] IBMW530 systemd[1]: Stopped target Graphical Interface. 
    [  561.765400] IBMW530 systemd[1]: Stopped target Multi-User System. 
    [  561.765501] IBMW530 systemd[1]: Stopped target Login Prompts. 
    [  561.765586] IBMW530 systemd[1]: Stopped target RPC Port Mapper. 
    [  561.765670] IBMW530 systemd[1]: Stopped target Smart Card. 
    [  561.765749] IBMW530 systemd[1]: Stopped target Sound Card. 
    [  561.765838] IBMW530 systemd[1]: Stopped target Timer Units. 
    [  561.766020] IBMW530 systemd[1]: Stopped Backup of RPM database. 
    [  561.766447] IBMW530 systemd[1]: Stopped Backup of /etc/sysconfig. 
    [  561.766604] IBMW530 systemd[1]: Stopped Balance block groups on a btrfs filesystem. 
    [  561.766742] IBMW530 systemd[1]: Stopped Scrub btrfs filesystem, verify block checksums. 
    [  561.766893] IBMW530 systemd[1]: Stopped Check if mainboard battery is Ok. 
    [  561.767043] IBMW530 systemd[1]: Stopped Discard unused blocks once a week. 
    [  561.767229] IBMW530 systemd[1]: Stopped Daily rotation of log files. 
    [  561.767375] IBMW530 systemd[1]: Stopped Daily man-db regeneration. 
    [  561.767514] IBMW530 systemd[1]: Stopped Daily Cleanup of Snapper Snapshots. 
    [  561.767658] IBMW530 systemd[1]: Stopped Timeline of Snapper Snapshots. 
    [  561.767820] IBMW530 systemd[1]: Stopped Daily Cleanup of Temporary Directories. 
    [  561.771664] IBMW530 systemd[1]: Stopped auditd rules generation. 
    [  561.778145] IBMW530 systemd[1]: Stopped Apply settings from /etc/sysconfig/keyboard. 
    [  561.786708] IBMW530 systemd[1]: Stopped Avahi mDNS/DNS-SD Stack. 
    [  561.787307] IBMW530 systemd[1]: Stopped irqbalance daemon. 
    [  561.787799] IBMW530 systemd[1]: Stopped Machine Check Exception Logging Daemon. 
    [  561.788766] IBMW530 systemd[1]: Stopped Save/Restore Sound Card State. 
    [  561.789263] IBMW530 systemd[1]: Stopped Restore /run/initramfs on shutdown. 
    [  561.791067] IBMW530 systemd[1]: Stopped Session 3 of User alastair. 
    [  561.799426] IBMW530 systemd[1]: Stopped Login and scanning of iSCSI devices. 
    [  561.800475] IBMW530 systemd[1]: Stopped target Network is Online. 
    [  561.802166] IBMW530 systemd[1]: Stopped Network Manager Wait Online. 
    [  561.802499] IBMW530 systemd[1]: Stopped Getty on tty1. 
    [  561.803068] IBMW530 systemd[1]: Stopped Command Scheduler. 
    [  561.803562] IBMW530 systemd[1]: Stopped Hold until boot process finishes up. 
    [  561.814436] IBMW530 systemd[1]: Stopped CUPS Scheduler. 
    [  561.833300] IBMW530 systemd[1]: Stopped Disk Manager. 
    [  561.842921] IBMW530 systemd[1]: Stopped Load/Save Random Seed. 
    [  561.845512] IBMW530 systemd[1]: Stopped Self Monitoring and Reporting Technology (SMART) Daemon. 
    [  561.846016] IBMW530 systemd[1]: Stopped Bluetooth service. 
    [  561.846613] IBMW530 systemd[1]: Stopped Power Profiles daemon. 
    [  561.848256] IBMW530 systemd[1]: Stopped PC/SC Smart Card Daemon. 
    [  561.848840] IBMW530 systemd[1]: Stopped RealtimeKit Scheduling Policy Service. 
    [  561.869327] IBMW530 systemd[1]: Stopped Daemon for power management. 
    [  561.885684] IBMW530 systemd[1]: Stopped Modem Manager. 
    [  563.065028] IBMW530 systemd[1]: Stopped User Manager for UID 1000. 
    [  563.145890] IBMW530 systemd[1]: Stopped User Runtime Directory /run/user/1000. 
    [  564.199753] IBMW530 systemd[1]: Stopped X Display Manager. 
    [  564.200392] IBMW530 systemd[1]: Stopped target System Time Synchronized. 
    [  564.200678] IBMW530 systemd[1]: Stopped target System Time Set. 
    [  564.207087] IBMW530 systemd[1]: Stopped NTP client/server. 
    [  564.207659] IBMW530 systemd[1]: Stopped target Host and Network Name Lookups. 
    [  564.260126] IBMW530 systemd[1]: Stopped Permit User Sessions. 
    [  564.260392] IBMW530 systemd[1]: Stopped target Network. 
    [  564.281868] IBMW530 systemd[1]: Stopped User Login Management. 
    [  564.282365] IBMW530 systemd[1]: Stopped target User and Group Name Lookups. 
    [  564.301413] IBMW530 systemd[1]: Stopped Name Service Cache Daemon. 
    [  564.647149] IBMW530 systemd[1]: Stopped Network Manager. 
    [  564.647717] IBMW530 systemd[1]: Stopped target Preparation for Network. 
    [  564.710682] IBMW530 systemd[1]: Stopped WPA Supplicant daemon. 
    [  564.737637] IBMW530 systemd[1]: Stopped firewalld - dynamic firewall daemon. 
    [  564.745777] IBMW530 systemd[1]: Stopped D-Bus System Message Bus. 
    [  564.785893] IBMW530 systemd[1]: Stopped Authorization Manager. 
    [  564.786424] IBMW530 systemd[1]: Stopped target Basic System. 
    [  564.801002] IBMW530 systemd[1]: Stopped Forward Password Requests to Plymouth Directory Watch. 
    [  564.801301] IBMW530 systemd[1]: Stopped target Path Units. 
    [  564.808810] IBMW530 systemd[1]: Stopped Watch /etc/sysconfig/btrfsmaintenance. 
    [  564.860808] IBMW530 systemd[1]: Stopped Watch for changes in CA certificates. 
    [  564.861389] IBMW530 systemd[1]: Stopped CUPS Scheduler. 
    [  564.888784] IBMW530 systemd[1]: Stopped Watch for changes in issue snippets. 
    [  564.896795] IBMW530 systemd[1]: Stopped Watch for changes in smartmontools sysconfig file. 
    [  564.897192] IBMW530 systemd[1]: Stopped target Slice Units. 
    [  564.898114] IBMW530 systemd[1]: Stopped target Socket Units. 
    [  564.899475] IBMW530 systemd[1]: Stopped target System Initialization. 
    [  564.899847] IBMW530 systemd[1]: Stopped target Local Encrypted Volumes. 
    [  564.899980] IBMW530 systemd[1]: Stopped target Local Integrity Protected Volumes. 
    [  564.900112] IBMW530 systemd[1]: Stopped target Swaps. 
    [  564.900235] IBMW530 systemd[1]: Stopped target Local Verity Protected Volumes. 
    [  564.905216] IBMW530 systemd[1]: Stopped Apply Kernel Variables. 
    [  564.905549] IBMW530 systemd[1]: Stopped Apply Kernel Variables for 5.18.4-1-default. 
    [  564.905900] IBMW530 systemd[1]: Stopped Load Kernel Modules. 
    [  564.956162] IBMW530 systemd[1]: Stopped Load/Save Screen Backlight Brightness of backlight:intel_backlight. 
    [  564.957759] IBMW530 systemd[1]: Stopped Load/Save Screen Backlight Brightness of leds:tpacpi::kbd_backlight. 
    [  564.962419] IBMW530 systemd[1]: Stopped Record System Boot/Shutdown in UTMP. 
    [  565.039656] IBMW530 systemd[1]: Stopped Security Auditing Service. 
    [  565.039939] IBMW530 systemd[1]: Stopped Create Volatile Files and Directories. 
    [  565.040020] IBMW530 systemd[1]: Stopped target Local File Systems. 
    [  565.059764] IBMW530 systemd[1]: Stopped File System Check on /dev/disk/by-uuid/10A2-1035. 
    alastair@IBMW530:~> 
    
    As far as I can tell in my ignorance this all looks unremarkable.

    I do still wish to clean up my system however as I am sure there is some rubbish in there and I need to aproach it is a systematic way as advocated above.
    If I could get past the rather many lines of baloo I might be able to see some examples of stoppage delays. Please could I get some more help sorting this out please.

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

    Default Re: RealTimeKit Scheduling Policy Service Delays shutdown for 3 minutes. WTF

    Quote Originally Posted by Budgie2 View Post
    Hi Karl,
    I ran both of your suggested commands and didn't see anything I could recognise as a possible cause of my problem:-

    Code:
    alastair@IBMW530:~> sudo journalctl -b -1 -u rtkit-daemon.service -p6 -o short-monotonic 
    [sudo] password for root:  
    [   31.701051] IBMW530 systemd[1]: Starting RealtimeKit Scheduling Policy Service... 
    [   31.832331] IBMW530 systemd[1]: Started RealtimeKit Scheduling Policy Service. 
    [   31.836252] IBMW530 rtkit-daemon[2336]: Successfully made thread 2325 of process 2325 owned by 'alastair' high pr>
    [   31.838438] IBMW530 rtkit-daemon[2336]: Successfully made thread 2328 of process 2328 owned by 'alastair' high pr>
    [   31.840315] IBMW530 rtkit-daemon[2336]: Successfully made thread 2326 of process 2326 owned by 'alastair' high pr>
    [   31.862246] IBMW530 rtkit-daemon[2336]: Successfully made thread 2345 of process 2326 owned by 'alastair' RT at p>
    [   31.869852] IBMW530 rtkit-daemon[2336]: Successfully made thread 2348 of process 2328 owned by 'alastair' RT at p>
    [   31.870847] IBMW530 rtkit-daemon[2336]: Successfully made thread 2350 of process 2325 owned by 'alastair' RT at p>
    [   40.424260] IBMW530 rtkit-daemon[2336]: Successfully made thread 2916 of process 2748 owned by 'alastair' RT at p>
    [  561.780419] IBMW530 systemd[1]: Stopping RealtimeKit Scheduling Policy Service... 
    [  561.848699] IBMW530 systemd[1]: rtkit-daemon.service: Deactivated successfully. 
    [  561.848840] IBMW530 systemd[1]: Stopped RealtimeKit Scheduling Policy Service. 
    lines 1-12/12 (END)
    
    Code:
    alastair@IBMW530:~> sudo journalctl -b -1 -u init.scope -g Stopped -o short-monotonic --no-pager 
    [sudo] password for root:  
    [    5.272331] IBMW530 systemd[1]: Stopped target Initrd Default Target. 
    [    5.272445] IBMW530 systemd[1]: Stopped target Basic System. 
    ...
    [  565.039939] IBMW530 systemd[1]: Stopped Create Volatile Files and Directories. 
    [  565.040020] IBMW530 systemd[1]: Stopped target Local File Systems. 
    [  565.059764] IBMW530 systemd[1]: Stopped File System Check on /dev/disk/by-uuid/10A2-1035. 
    alastair@IBMW530:~> 
    
    As far as I can tell in my ignorance this all looks unremarkable.

    I do still wish to clean up my system however as I am sure there is some rubbish in there and I need to aproach it is a systematic way as advocated above.
    If I could get past the rather many lines of baloo I might be able to see some examples of stoppage delays. Please could I get some more help sorting this out please.
    Shut down journal looks great. Presumable systemd readily stopped running fsck. What about wait? Did it occur? I think applying common sense when reporting as above tells users to add this information without being explicitly asked to do so.
    i7-6700K (2016), i5-8250U (2018), AMD Ryzen 5 3400G (2020), 5600X (2022) openSUSE Tumbleweed, KDE Plasma

  10. #10
    Join Date
    Nov 2008
    Posts
    2,393
    Blog Entries
    1

    Default Re: RealTimeKit Scheduling Policy Service Delays shutdown for 3 minutes. WTF

    Hi Karl,
    The problems to which I refer whizz past during starting and stopping.
    I was under the impressions that I would be able to see them by running journalctl but I was not able to go back through it. Of course I had intended to show the problem lines and would if I could.

    Meanwhile I am now on a different machine to cannot easily show but meanwhile I have just done a system update and reboot on my Leap15.3 system which I am using as I write this and have not had any issues. It is the TW laptop installation where the problems sit. On that system I also now have a problem with the NFS connection when starting. Will try and send info later, meanwhile thanks for the reply.
    Regards,
    Budge.

Posting Permissions

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