Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

This sucks.

$ tmux attach-session
no sessions

My sysadmin upgraded tmux and now I can't reattach. My processes are still running according to ps ux. Is there any hope of recovering my session?

Update: There's a socket in /tmp/tmux-1234, so I tried tmux -L /tmp/tmux-1234/default attach, but tmux does nothing. Hooray.

share|improve this question
up vote 19 down vote accepted

This quickest way to determine if you can recover is:

killall -10 tmux

That will send the signal to recreate all socket files for any running tmux processes. If you're not root, no problem it will only signal your tmux process anyway.

Long story short, if tmux is not running (ps xu | grep tmux), you're screwed :(

share|improve this answer
This works, but I was confused about why it works. It turns out that signal 10 is a user-defined signal, and tmux says it will "recreate the server socket on SIGUSR1". – DaoWen Jan 19 '15 at 19:47

tmux is not guaranteed to be compatible across updates; ask your sysadmin to let you know before doing upgrades or use a copy you built locally that he is less likely to mess with.

share|improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .