I initiated 'do-release-upgrade' over ssh, and then my (client) network connection died.

How can I reconnect to the session which is performing this command?


You cannot. Your command will be sent a SIGHUP. Take a look at: screen, tmux, nohup, or disown, ...

How to reconnect to a disconnected ssh session

| improve this answer | |

Your session was killed when you disconnected.

To be more specific: presuming you su-ed to root, then your su process was a child of your login process, and your 'do-release-upgrade' process was a child of that.

When you disconnected you have killed your login process, killing the related child processes unless one or other them has done the sort of backgrounding that an daemon init does. (OT, but for more information on the latter, you can read about daemon forking at Wikipedia.)

You probably should have used screen, or worked on the system console :-(

| improve this answer | |
  • 1
    The process was still stuck somehow, as apt-get was locked? – Jon Skarpeteig Jul 31 '11 at 11:01
  • 2
    If do-release-upgrade is something like Debian's apt-get dist-upgrade; then dpkg will detect that the process of upgrading has been interrupted due to the existence of the dpkg lock file (normally /var/lib/dpkg/lock). – rorycl Jul 31 '11 at 17:19

If screen is installed, the do-release-upgrade command automaticly starts a screen session. This session can be resumed in another ssh session.

| improve this answer | |

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.