2017-07-07 13:24:39 UTC
I got a very strange behavior with tmux and systemd on my server and
maybe someone knows a way around it.
The way I start tmux is as follows:
Setting TMUX_TMPDIR to my user's XDG_RUNTIME_DIR and starting tmux in a
systemd user service . I do the same for other things, such as
weechat . They both use the same tmux.conf .
Lingering is activated for my user, so the enabled user services will
start with the system and stay running, even when it's disconnected...
in theory (and this used to work very well, without a problem for
With some changes in systemd however, this seems to fail now, and I
can't seem to find the reason why. Tmux just exits with "server lost"
once I do a detach.
At first I could only observe this behavior when I had a shared ssh
session to the server (so I thought), that I then quit, or when I
attached and detached the tmux session quickly.
Now I'm getting this nearly every time I detach from the tmux session!
I tried several things by now, and it doesn't seem to make any
- using legacy cgroups , because of maybe being affected by this 
- switching to single connections instead of shared connections for ssh
(lowered the amount of random tmux quits!)
- using hardened kernel (just to try another one)
- logging a tmux session, without getting any output, that would
explain, why this happens
- crossing fingers (actually helps, because the bug seems completely
random ;/ )
- using a system scope unit (***@username) , getting the same results
- downgrading tmux to >=2.3 (no difference)
- downgrading systemd to <=233-7 (seems to happen less frequently)
For some awkward reason, it seems to have worked again for a short time,
when Arch first switched to systemd 233 a few days back , but ever
since it moved to systemd-stable , the problem is back (and even
worse than before). Me thinking that might only be due to a "less
frequent occurence" though.
I'm just wondering, how to solve this. Maybe someone has a great idea to
share? It's getting beyond annoying by now and I can't seem to find out,
if it's tmux, systemd or some kernel problem... or all of them together.
P.S.: Doesn't seem to happen with screen. I don't want to adapt
everything to screen now though ;)