DigitalOcean repository for MariaDB 10.3 is broken

Question

I am trying to work on upgrading an older droplet, both the Ubuntu version (currently 18.04 LTS) and MariaDB (10.3). I replaced all the references to DO’s mirrors throughout souces.lst but there seems to be no substitute for nyc2.mirrors.digitalocean.com so I can upgrade MariaDB. Nothing I’ve found online, or in MariaDB’s documentation, has been helpful. (MariaDB apparently only wants to support newer versions.) I need to fix this repository so I can upgrade Ubuntu, then upgrade MariaDB to a more current version. Any ideas where to start?

alexdo · Answer

Hi there, The short version is that the per-region mirror hostnames like nyc2.mirrors.digitalocean.com were consolidated into a single geo-routed host, mirrors.digitalocean.com , which picks a nearby mirror for you automatically. So there is no nyc2-specific replacement to track down, the generic host is the replacement. I checked and mirrors.digitalocean.com still serves the 18.04 (bionic) archive, so pointing your sources at it (or straight at Ubuntu’s own archive.ubuntu.com ) gets apt working again. It also helps to keep two separate things apart here, since they tend to get tangled: Your base Ubuntu repos in /etc/apt/sources.list The MariaDB repo, which lives in its own file under /etc/apt/sources.list.d/ For the base repos, a working bionic sources.list looks like this: deb http://mirrors.digitalocean.com/ubuntu/ bionic main restricted universe multiversedeb http://mirrors.digitalocean.com/ubuntu/ bionic-updates main restricted universe multiversedeb http://mirrors.digitalocean.com/ubuntu/ bionic-backports main restricted universe multiversedeb http://security.ubuntu.com/ubuntu/ bionic-security main restricted universe multiverse If the DigitalOcean host ever gives you trouble, swapping mirrors.digitalocean.com for archive.ubuntu.com behaves identically, both are serving bionic right now. Then run apt update. For MariaDB, 10.3 reached end of life in May 2023 and the project moved the retired repos to archive.mariadb.org . If your MariaDB .list file points at a mirror that now 404s, you can repoint it at the archive for the exact release you are on (10.3.39 is the last 10.3): deb [arch=amd64] https://archive.mariadb.org/mariadb-10.3.39/repo/ubuntu/ bionic main That said, I would not re-pin a dead MariaDB repo just to stay on 10.3. The cleaner route, and the one that avoids external repos entirely, is to let the Ubuntu release upgrades carry MariaDB forward: Ubuntu 20.04 ships MariaDB 10.3 as its own package, so upgrading 18.04 to 20.04 keeps you on 10.3 but from the distro, no external repo needed. Ubuntu 22.04 ships MariaDB 10.6, so the following hop moves you onto a supported series. So the plan I would run: Snapshot the Droplet first, and separately take a mysqldump of your databases. A release upgrade combined with a database major-version bump is exactly the kind of thing you want a clean rollback for. Fix sources.list as above, then apt update, apt upgrade, and reboot. Comment out or remove the external MariaDB repo file so do-release-upgrade does not choke on it. Run sudo do-release-upgrade to move to 20.04. Once it is back up, run sudo mariadb-upgrade. Run do-release-upgrade again to reach 22.04 (MariaDB 10.6), then mariadb-upgrade once more. The one firm rule with MariaDB is to not skip major versions. Upgrade one LTS at a time and run mariadb-upgrade after each so the system tables get updated. Jumping 18.04 straight to 22.04 in a single step is usually where people get bitten. One honest caveat: 18.04 is past standard support and on ESM now, so the sooner you are off it the better. If you need it to stay patched during the migration window, Ubuntu Pro (free for personal use on a handful of machines) re-enables bionic security updates. Regards

KFSys · Answer

Older droplets were built with MariaDB’s apt repo pointing at a DigitalOcean mirror, usually nyc2.mirrors.digitalocean.com/mariadb/ … That mirror no longer hosts MariaDB, and MariaDB’s live mirrors dropped 10.3 when it reached end of life. That’s why apt update fails. MariaDB still keeps every old release on archive.mariadb.org , so you can point apt there. Step 1: Find the dead repo line grep -rn "mirrors.digitalocean.com" /etc/apt/sources.list /etc/apt/sources.list.d/ It’s usually in /etc/apt/sources.list.d/mariadb.list, or directly in sources.list, and looks like this: deb [arch=amd64] http://nyc2.mirrors.digitalocean.com/mariadb/repo/10.3/ubuntu bionic main Step 2: Replace it with the archive Open the file: sudo nano /etc/apt/sources.list.d/mariadb.list Replace the old line with: deb [arch=amd64] https://archive.mariadb.org/mariadb-10.3/repo/ubuntu bionic main Install the tools needed to fetch the key over HTTPS: sudo apt-get install -y curl ca-certificates apt-transport-https Refresh the signing key in case the old one has expired: curl -fsSL https://supplychain.mariadb.com/mariadb-keyring-2019.gpg | sudo tee /usr/share/keyrings/mariadb-keyring-2019.gpg >/dev/null If apt later complains about NO_PUBKEY, use this version of the repo line instead: deb [arch=amd64 signed-by=/usr/share/keyrings/mariadb-keyring-2019.gpg] https://archive.mariadb.org/mariadb-10.3/repo/ubuntu bionic main Then update: sudo apt update apt update should now finish cleanly, which you need before you can run the release upgrade. Step 3: Upgrade safely Back up first. Take a droplet snapshot from the control panel, and also dump all databases: sudo mysqldump --all-databases --routines --events > all.sql Upgrade Ubuntu one LTS at a time: 18.04 → 20.04 → 22.04 → 24.04. Run this once per step: sudo do-release-upgrade It disables third-party repos such as MariaDB’s during each step. That’s expected.3. Once you’re on the release you want, add MariaDB’s current repo for that Ubuntu version with their official script. Pick a supported LTS, such as 10.11 or 11.4: curl -LsS https://r.mariadb.com/downloads/mariadb_repo_setup | sudo bash -s -- --mariadb-server-version="mariadb-10.11" Install the new version: sudo apt update && sudo apt install mariadb-server Upgrade the system tables: sudo mariadb-upgrade Then delete or comment out the old 10.3 archive line so it doesn’t come back. Going straight from 10.3 to 10.11 is supported for a normal in-place upgrade. Check the logs for warnings afterwards: journalctl -u mariadb -n 50 You also have the mysqldump from step 1 as a fallback.

Bobby · Answer

Hi there, In addition to the answers above, a few things worth checking before you start: Find which repo apt is really using. This shows where the installed MariaDB package came from, so you fix the right file: apt-cache policy mariadb-server grep -rn "mariadb\|digitalocean.com" /etc/apt/sources.list /etc/apt/sources.list.d/ Pick one upgrade path. The two answers above differ a bit. One says to go one Ubuntu LTS at a time and let the distro MariaDB move forward. The other adds MariaDB’s own repo at the end and jumps to a newer series. Both can work, but I would go with the first. It keeps fewer external repos in the mix, and you only change one big thing at a time. Free disk space and a safe session. do-release-upgrade needs a few GB free, so check with df -h /. Run it inside tmux or screen. If your SSH session drops in the middle of an upgrade, you can end up with a broken system. Better dump command. If your tables use InnoDB, add --single-transaction, so the dump is consistent without locking the tables: sudo mysqldump --all-databases --routines --events --single-transaction > all.sql Check your app, not only the database. Each Ubuntu release also changes the PHP, Python or Node version. The database can upgrade fine and your app can still break because of the language version. Honestly, for an old Droplet like this, I would not upgrade in place. A cleaner option is to create a new Droplet with a current Ubuntu LTS, install a supported MariaDB version, restore the dump, and test your app there. When it works, switch the DNS or move a Reserved IP. If something goes wrong, the old server is still untouched. If you still want to do the in-place upgrade, restore your snapshot to a temporary Droplet first and do a test run there. Then you will know about the problems before you touch production.

Become a contributor for community

DigitalOcean Documentation

Resources for startups and AI-native businesses

The developer cloud

Start building today

Report this

DigitalOcean repository for MariaDB 10.3 is broken

Related questions

How to upgrade the distribution used by my droplet?

I just used ssh to do-release-upgrade from ubuntu 18.04 to 20.04 and now site is down

Unable to Reset Root Password in Ubuntu 18.04 LTS

Need to install php.7.4 on Ubuntu 18. Can't get it in my list to update.

What is the best Linux (or at least ABI-compatible) OS distribution to use for building a custom image for small 1GB 1cpu VMs?

eth0 not getting configured correctly after upgrade.

Cannot upgrade mysql from 5.7 to 8 (Ubunto 18)

Hosting 3 Sites On the Same Droplet using subdomains

Permission Denied (Pubkey) whilst deploying Terragraph

Dashboard shows older version of Ubuntu after several upgrades.

Error during upgrade Ubuntu 18.04 to 22.04

MySQL upgrade issue during migration from Ubuntu 18.04

Report this

DigitalOcean repository for MariaDB 10.3 is broken

Related questions

How to upgrade the distribution used by my droplet?

I just used ssh to do-release-upgrade from ubuntu 18.04 to 20.04 and now site is down

Unable to Reset Root Password in Ubuntu 18.04 LTS

Need to install php.7.4 on Ubuntu 18. Can't get it in my list to update.

What is the best Linux (or at least ABI-compatible) OS distribution to use for building a custom image for small 1GB 1cpu VMs?

eth0 not getting configured correctly after upgrade.

Cannot upgrade mysql from 5.7 to 8 (Ubunto 18)

Hosting 3 Sites On the Same Droplet using subdomains

Permission Denied (Pubkey) whilst deploying Terragraph

Dashboard shows older version of Ubuntu after several upgrades.

Error during upgrade Ubuntu 18.04 to 22.04

MySQL upgrade issue during migration from Ubuntu 18.04