![]() The cloud console may take a little time to start up and what I ran into was that the networking service was causing startup to take around 2 minutes. Luckily Digital Ocean provide a cloud console you can use to directly access the server even when it's networking is down. This happened mostly on the 16.04 servers but during their upgrade from 18.04 to 20.04. On a bunch of the servers I upgraded, I ran into networking issues where I couldn't connect over ssh to it, and once inside couldn't ping out. If everything's good, you can repeat the previous step again and continue on to upgrade from 18.04 to 20.04. Uncomment, sudo apt update to check it's working and sudo apt upgrade where needed, then repeat. IT's worth checking your apt repos here too, over in your /etc/apt/sources.list file and the files in your /etc/apt/ folder, check for commented out repos from the upgrade and check if you want to bring them back and if so do so one at a time. Checks & repeatĪfter the 16.04 to 18.04 upgrade, you'll want to check everything is up and running well on your server before continuing to upgrade.Ĭheck key services are up and running, view your sites on the frontend etc., check api monitoring etc. However, if you do find the server doesn't come back online after a couple minutes, skip down to the Resolving Network Issues section below. In all my upgrades, the 16.04 to 18.04 upgrades came back up fine, the only issues I ran into were during the 18.04 to 20.04 upgrade which was mainly network issues. Lastly, if needed you have your backup / snapshot to go back to as well if ever needed.Īfter finishing up the last stage of this command will be when it requests to restart your machine. The same goes if you went the other way and said yes to changing the files, you'll have. etc/nginx/-dist so you can use this to compare your custom version to the new default they'd have provided later. The nice thing to remember here though is that if you don't upgrade the config files, it'll save the new default one to the same location but with a. then you'll not want to have to re-do them, but on some files it's worth checking the differences to see what's changed. My advice during this is answer Y (yes) to the questions about starting and automated restarts, but answer D (diff) or N (no) to the config changes.Įspecially if you know you've made custom changes around files like your /etc/nf or your /etc/nginx/nf file etc. Now you're ready to begin the upgrade, simply start it with the following command and follow the on screen instructions: sudo do-release-upgrade (Check if you're running ufw with sudo ufw status) ![]() If you're using ufw you can run: sudo ufw allow 1022/tcp This is a port the release upgrade process opens for ssh in case there's an issue. Run the release upgradeīefore starting the next upgrade process, you'll want to open port 1022 ready. If you notice there's any issues like apt repos now 404'ing etc, make a note of them as you can either see if they can be fixed now, but as you're upgrading from EOL you may find some repos are no longer available on your current version and you'll need to come back to these after the upgrade. Pretty standard but run and check the output of both to make sure everything's ok: sudo apt update & sudo apt upgrade You'll want to make sure your packages on the server are working and up to date before you continue. For several of the servers this process took less than half an hour, all down to the size of the server, and as I ran into Network issues later, the snapshot proved especially useful as I restored back to it while I debugged the issue further. ![]() First, start with backup / snapshot.ĭigital Ocean provide a great way to take live snapshots of the servers, but the preferable way if you're able to is to turn off the server and snapshot it before continuing. In this post I'll run through my tips for doing each server upgrade from 16.04 to 18.04, and then to 20.04, along with a few common issues noticed along the way to help if you run into them too. If that's an option for you, it's a good one, but in my case that wasn't as simple an option. They mentioned their recommendation is that for anyone that can, is to install a new server and transfer over the files instead. Talking to Digital Ocean support about this, its not an uncommon issue with larger upgrades like these. While upgrading, half of them had no issues at all, while the other half ran into networking issues, bad times but this article will help you resolve those. ![]() (Why 20.04 vs 21.04? because every 2 years Ubuntu releases an LTS release for long term support, 20.04 is the latest LTS) ![]() Recently I upgraded a bunch of our app servers that were on old 16.04 and other similar sub 20.04 Ubuntu versions. Upgrading Ubuntu servers from 16.04 to 20.04 on Digital Ocean (includes handling floating IP) Home Subscribe Upgrading Ubuntu servers from 16.04 to 20.04 on Digital Ocean (includes handling floating IP) 10 April 2021 ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |