Ask Ubuntu is a question and answer site for Ubuntu users and developers. It only takes a minute to sign up.
Sign up to join this community
When I run
sudo do-release-upgrade
over ssh, I get the following message.
This session appears to be running under ssh. It is not recommended to perform a upgrade over ssh currently because in case of failure it is harder to recover. If you continue, an additional ssh daemon will be started at port '9004'. Do you want to continue?
What is the real risk of upgrading over ssh? How does the additional ssh daemon help mitigate this?
@Marco-Ceppi 's solution is already integrated into do-release-upgrade.
When you run do-release-upgrade it starts a screen session automatically. If your ssh session gets disconnected, you can resume the installation. All you have to do is open a new ssh session, and run do-release-upgrade again. It will reconnect to your previous installation.
A second risk, pointed out by @sepp2k is that your sshd server might need to be upgraded, and it could perhaps not restart correctly. Therefore the upgrade program runs a second deamon, at the port specified. You should check your network configuration to make sure you have access through this port, before resuming.
Good luck.
Moreover, the screen-session do-release-upgrade starts by itself is run under the root account, so if your own screen-session crashes, you will be able to recover by running sudo screen -x, if (for some reason) the command do-release-upgrade doesn't recover it by itself, which seems to be common.
do-release-upgrade did not start a screen session) I am now upgrading from 10.04 LTS to 12.04 LTS and now do-release-upgrade now starts a screen session automatically.
do-release-upgrade take care of everything before hand, then: 1) you can reconnect from a broken ssh by re-running do-release-upgrade after re-logging and 2) you can re-log from a failed sshd upgrade through the port specified at the beginning by do-release-upgrade. Is that it ?
screen is installed as it can only be used if it is installed. You might have to install it with apt-get install screen. At least this is what I realized when upgrading from Ubuntu 17.10 to 18.04. screen was not installed and not used on my first attempt. I stopped the upgrade before the download, installed screen, and run do-release-upgrade again. Then screen was used.
What I would recommend doing is launching a screen session on the server and running the upgrade in screen - that way if your SSH session drops (for whatever reason) the upgrade process will not halt.
Screen is a program that allows for persistent terminal(s) on a machine. So you can start a screen session and so long as the machine is on that screen session (and it's history, running programs, etc) will continue to operate though no one user is on the machine. It was designed in the early days to provide a multi-windowed text terminal prior to the days of X Server. You can install it using APT:
sudo apt-get install screen
So you can ssh into your server, start screen, initiate the upgrade process and not have to worry about the upgrade bing botched because you've lost Internet connection or your computer crashed.
do-release-upgrade (since precise) is automatically executing screen.
screen -dmS do-release-upgrade -> screen -r to switch to the running screen -> Ctrl + A, Ctrl + D to leave the screen running in the background and go back to the main screen
Oct 8, 2018 at 22:00
screen, but then I got scared and thought it might get killed during upgrades (which SSH, again more intuitively, seems to be better at handling due to its daemons being detached from the actual service). Has anyone here actually used screen for upgrades without problems?
May 5 at 13:50
If a new version of the ssh daemon is installed as part of the upgrade, the daemon will be restarted. If the update breaks the daemon for some reason, it would fail to start up again and you'd have no way of logging into the machine anymore.
By starting a separate sshd, which is not handled by the init system and thus won't be restarted during the upgrade, it is ensured that the old version of sshd will still be running even if the new version fails to start. Thus you can still log into the system and see what caused the daemon to break.
I've never (yet) had a problem doing that, though I've only upgraded half a dozen or so boxes that way. It is just that if something goes wrong the additional SSH daemon may be your only hope of avoiding a visit (or making use of whatever remote re-install options you have).
