[SOLVED] Struggling with long reboot times - TMUX the culprit!

not_a_kangaroo · 2024-07-20 19:10:00

As in the title, for some reason my reboot time is really suffering at the moment and can get stuck for 7-8 mins. When I start the reboot and the computer is shutting down, it gets stuck on the message "A stop job is running for user manager UID 1000".

I've seen some advice elsewhere relating to gnome-session-restart-dbus.service, and adding Slice=-.slice - but this was already there, so sadly not the fix I was hoping for. (original thread: https://bbs.archlinux.org/viewtopic.php?id=261556)

Another path I went down was by trying the following:

sudo systemctl --user list-jobs

I get back "Failed to connect to bus: no medium found"

Apologies for the slightly muddled info, I've been trying to sort this for a few days now and can't specifically remember exactly what train of thought I had / other post I was referencing when trying the above two things.

Let me know what else is useful to help diagnose the issue and thanks as always for being a great forum for newbie's such as myself.

Last edited by not_a_kangaroo (2024-07-21 10:05:15)

Head_on_a_Stick · 2024-07-20 19:21:10

The systemctl command should be run as your normal user if you want to query units run under that user, don't use sudo for that.

You should probably share the full journal from a boot that shows this problem (preferably as brief as possible).

not_a_kangaroo · 2024-07-20 20:52:07

Thanks for the reply. I have added the journalctl -b output into a file. Is there a commonly used sensible way of sharing it? I can add it to a github repo if that's the best way?

Head_on_a_Stick · 2024-07-20 21:08:51

Either gists or https://wiki.archlinux.org/title/List_o … ted_client are fine here.

not_a_kangaroo · 2024-07-20 21:20:39

Head_on_a_Stick wrote:

Either gists or https://wiki.archlinux.org/title/List_o … ted_client are fine here.

Thanks, here's a gist . If I'm totally honest I'm not really sure what I'm looking for in here so any pointers really appreciated.

https://gist.github.com/JonnySB/5b93335 … c22ee47bac

Head_on_a_Stick · 2024-07-20 23:09:07

That doesn't seem to show any shutdown. Or have I missed something?

not_a_kangaroo · 2024-07-21 08:30:12

Head_on_a_Stick wrote:

That doesn't seem to show any shutdown. Or have I missed something?

Right I'm an idiot - I now know what the "-1" is for in the journalctl -b command!

I've updated the gist with a better version: https://gist.github.com/JonnySB/5b93335 … c22ee47bac

This was actually a pretty fast shutdown compared to usual but still ~30s. Seems to be something about tmux that caught my eye. This makes sense given that it's after a notice about lightdm that it pauses when shutting down. Snippet of the bit I mean below. I have a tmux autostart feature running by popping ZSH_TMUX_AUTOSTART=true in my .zshrc, not sure if this could have anything to do with it?

Jul 21 09:13:27 jonnyarch systemd[1921]: Closed D-Bus User Message Bus Socket.
Jul 21 09:13:27 jonnyarch systemd[1921]: Removed slice User Application Slice.
Jul 21 09:13:27 jonnyarch systemd[1]: lightdm.service: Deactivated successfully.
Jul 21 09:13:27 jonnyarch systemd[1]: Stopped Light Display Manager.
Jul 21 09:14:55 jonnyarch systemd[1921]: tmux-spawn-0517b47f-8af7-43eb-a3fd-b4afe201a731.scope: Stopping timed out. Killing.
Jul 21 09:14:55 jonnyarch systemd[1921]: tmux-spawn-0517b47f-8af7-43eb-a3fd-b4afe201a731.scope: Killing process 4517 (zsh) with signal SIGKILL.
Jul 21 09:14:55 jonnyarch systemd[1921]: tmux-spawn-93cb6642-1a69-43ed-a6e9-b193c30ba66c.scope: Stopping timed out. Killing.
Jul 21 09:14:55 jonnyarch systemd[1921]: tmux-spawn-93cb6642-1a69-43ed-a6e9-b193c30ba66c.scope: Killing process 4405 (zsh) with signal SIGKILL.
Jul 21 09:14:55 jonnyarch systemd[1921]: tmux-spawn-9cac58fd-567e-45c3-94df-86ca9ba0b92f.scope: Stopping timed out. Killing.
Jul 21 09:14:55 jonnyarch systemd[1921]: tmux-spawn-9cac58fd-567e-45c3-94df-86ca9ba0b92f.scope: Killing process 4770 (zsh) with signal SIGKILL.
Jul 21 09:14:55 jonnyarch systemd[1921]: tmux-spawn-3bc3a715-6083-4ca9-aa07-a302b9e02a8c.scope: Stopping timed out. Killing.
Jul 21 09:14:55 jonnyarch systemd[1921]: tmux-spawn-3bc3a715-6083-4ca9-aa07-a302b9e02a8c.scope: Killing process 4703 (zsh) with signal SIGKILL.
Jul 21 09:14:55 jonnyarch systemd[1921]: tmux-spawn-63a61028-80e9-4db8-a1c5-5e5e18d7a3bf.scope: Stopping timed out. Killing.
Jul 21 09:14:55 jonnyarch systemd[1921]: tmux-spawn-63a61028-80e9-4db8-a1c5-5e5e18d7a3bf.scope: Killing process 4600 (zsh) with signal SIGKILL.
Jul 21 09:14:55 jonnyarch systemd[1921]: tmux-spawn-10ce14c4-c94c-4bb0-bb42-c64d5f0bdccc.scope: Stopping timed out. Killing.
Jul 21 09:14:55 jonnyarch systemd[1921]: tmux-spawn-10ce14c4-c94c-4bb0-bb42-c64d5f0bdccc.scope: Killing process 4449 (zsh) with signal SIGKILL.
Jul 21 09:14:55 jonnyarch systemd[1921]: tmux-spawn-0517b47f-8af7-43eb-a3fd-b4afe201a731.scope: Failed with result 'timeout'.
Jul 21 09:14:55 jonnyarch systemd[1921]: Stopped tmux child pane 4517 launched by process 3156.
Jul 21 09:14:55 jonnyarch systemd[1921]: tmux-spawn-10ce14c4-c94c-4bb0-bb42-c64d5f0bdccc.scope: Failed with result 'timeout'.
Jul 21 09:14:55 jonnyarch systemd[1921]: Stopped tmux child pane 4449 launched by process 3156.
Jul 21 09:14:55 jonnyarch systemd[1921]: tmux-spawn-3bc3a715-6083-4ca9-aa07-a302b9e02a8c.scope: Failed with result 'timeout'.
Jul 21 09:14:55 jonnyarch systemd[1921]: Stopped tmux child pane 4703 launched by process 3156.
Jul 21 09:14:55 jonnyarch systemd[1921]: tmux-spawn-63a61028-80e9-4db8-a1c5-5e5e18d7a3bf.scope: Failed with result 'timeout'.
Jul 21 09:14:55 jonnyarch systemd[1921]: Stopped tmux child pane 4600 launched by process 3156.
Jul 21 09:14:55 jonnyarch systemd[1921]: tmux-spawn-9cac58fd-567e-45c3-94df-86ca9ba0b92f.scope: Failed with result 'timeout'.
Jul 21 09:14:55 jonnyarch systemd[1921]: Stopped tmux child pane 4770 launched by process 3156.
Jul 21 09:14:55 jonnyarch systemd[1921]: tmux-spawn-93cb6642-1a69-43ed-a6e9-b193c30ba66c.scope: Failed with result 'timeout'.
Jul 21 09:14:55 jonnyarch systemd[1921]: Stopped tmux child pane 4405 launched by process 3156.
Jul 21 09:14:55 jonnyarch systemd[1921]: Reached target Shutdown.
Jul 21 09:14:55 jonnyarch systemd[1921]: Finished Exit the Session.

Last edited by not_a_kangaroo (2024-07-21 08:30:29)

not_a_kangaroo · 2024-07-21 10:04:28

SOLVED!

I found this thread - https://github.com/tmux/tmux/issues/3905

Seems to suggest that the issue is something to do with systemd cgroups being used to install the package. (bit over my head and so not 100% sure what is happening to be honest)

But long story short - solved by installing this image instead of the default on pacman (https://aur.archlinux.org/packages/tmux-git)

Thanks as always for the help - feel like I'm starting to understand how to look at logs a bit more now

Arch Linux

#1 2024-07-20 19:10:00

[SOLVED] Struggling with long reboot times - TMUX the culprit!

#2 2024-07-20 19:21:10

Re: [SOLVED] Struggling with long reboot times - TMUX the culprit!

#3 2024-07-20 20:52:07

Re: [SOLVED] Struggling with long reboot times - TMUX the culprit!

#4 2024-07-20 21:08:51

Re: [SOLVED] Struggling with long reboot times - TMUX the culprit!

#5 2024-07-20 21:20:39

Re: [SOLVED] Struggling with long reboot times - TMUX the culprit!

#6 2024-07-20 23:09:07

Re: [SOLVED] Struggling with long reboot times - TMUX the culprit!

#7 2024-07-21 08:30:12

Re: [SOLVED] Struggling with long reboot times - TMUX the culprit!

#8 2024-07-21 10:04:28

Re: [SOLVED] Struggling with long reboot times - TMUX the culprit!

Board footer