9

Every time I detach from all the tmux sessions in the terminal, after I want to get back, I get this:

[me@CentOS7 ~]$ tmux ls
error connecting to /tmp/tmux-1000/default (No such file or directory)

It seems the /tmp directory get cleared in the meantime. It doesn't happen straight away and it's hard to tell when exactly but usually after a couple of days of running I know I can't detach in order not to lose the session.

Anyone knows how to retain the session? Prevent CentOS from removing the tmux server somehow? (I assume it's CentOS as it never happened to me on Debian-based distros.)

9

You can attempt to send a SIGUSR1 to the process in order for the tmux server to recreate the socket

pkill -USR1 tmux

Source

| improve this answer | |
  • 2
    Missed that one, thanks. Any idea why this happens on CentOS? – qwrtln Apr 9 '18 at 6:56
  • Thanks much. I tried killing the process (SIGKILL) hoping that it would recreate the socket next time it starts. It didn't. It needed USR1 for somereason. I cant believe tmux doesn't check of missing socket and recreate it upon startup 🤦🏻‍♂️ – Thamme Gowda Sep 14 at 18:40

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.