mariadb update error

MrBeef

Hello you all, I am new to Enhance en to Ubuntu and today I did a manual update and was receiving the next message (see after this) Did someone else also get this message or is it a problem only on my server?
E: The repository 'https://dlm.mariadb.com/repo/mariadb-server/11.4/repo/ubuntu noble Release' no longer has a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.

Thanks in advance, Dennis

GoSuccess

rm /var/lib/apt/lists/*mariadb*
apt update
apt upgrade

See: https://enhance.com/docs/getting-started/upgrading-from-v12.html

xyzulu

This repo is giving a 404: https://dlm.mariadb.com/repo/mariadb-server/11.4/repo/ubuntu
Enhance is aware of this mariadb repo issue.. I'm sure once they investigate they will let us all know.

PS GoSuccess while that command does clear the apt repo cache, it would not resolve the issue with a repo listed in the sources files giving a 404.

MrBeef

Thank you very much for your response.
I did it but now it can't find the mariadb server so it lookslike no Enhance side problem.
Ign:2 https://dlm.mariadb.com/repo/mariadb-server/11.4/repo/ubuntu noble InRelease
Hit:4 http://security.ubuntu.com/ubuntu noble-security InRelease
Hit:5 https://apt.enhance.com noble InRelease
Hit:6 http://archive.ubuntu.com/ubuntu noble InRelease
Hit:1 https://downloads.mariadb.com/Tools/ubuntu noble InRelease
Hit:7 http://archive.ubuntu.com/ubuntu noble-updates InRelease
Hit:3 https://dlm.mariadb.com/repo/maxscale/latest/apt noble InRelease
Err:8 https://dlm.mariadb.com/repo/mariadb-server/11.4/repo/ubuntu noble Release
404 Not Found [IP: 104.18.135.24 443]
Hit:9 http://archive.ubuntu.com/ubuntu noble-backports InRelease
Hit:10 https://esm.ubuntu.com/apps/ubuntu noble-apps-security InRelease
Hit:11 https://esm.ubuntu.com/apps/ubuntu noble-apps-updates InRelease
Hit:12 https://esm.ubuntu.com/infra/ubuntu noble-infra-security InRelease
Hit:13 https://esm.ubuntu.com/infra/ubuntu noble-infra-updates InRelease
Reading package lists... Done
E: The repository 'https://dlm.mariadb.com/repo/mariadb-server/11.4/repo/ubuntu noble Release' does not have a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.

Adam

We think that mariadb have some kind of mirror sync issue because even the official install script is failing. Hopefully it should be fixed soon. We will try to get in contact with someone.

rdbf

Similar issue here, but happened when adding a new server to the estate, so now it's stuck with the database role "installed" as per the interface, but no actual database installed, and removing the role errors out. Ticket is submitted already, so will update here if anything changes.

MrBeef

problem no longer exist. Updates are without problems

rdbf

Indeed it's fixed. Had to manually copy the mariadb GPG key before it would do apt-update, and manually install mariadb-server before the Enhance interface was happy with it again, but it's working now.

cPFence

The upgrade went smoothly on all servers with no changes or tweaks. Several repos have had IPv6 connectivity issues lately, especially MariaDB, GoAccess, and a few others. If you run into this, try forcing IPv4 in your repo configs - that usually fixes it.

xyzulu

cPFence Several repos have had IPv6 connectivity issues lately

This wasn't the issue this time.. plus Enhance not restricts mariadb repo to IPv4 I believe.

cPFence

xyzulu This wasn't the issue this time.. plus Enhance not restricts mariadb repo to IPv4 I believe.

Can’t comment on the issue this time, the upgrade went smoothly for us. But we’ve had problems before with some repos like MariaDB and GoAccess, which turned out to be temporary IPv6 connectivity issues. If that’s the case, you can force IPv4 with:

sudo apt -o Acquire::ForceIPv4=true update && sudo apt -o Acquire::ForceIPv4=true upgrade -y

MrBeef

cPFence

404 Not Found [IP: 104.18.135.24 443
Lookslike a little IPv4 problem ?

cPFence

MrBeef

The first thing I’d try if I see that error is the opposite, force IPv6:

sudo apt -o Acquire::ForceIPv6=true update && sudo apt -o Acquire::ForceIPv6=true upgrade -y

If both IPv4 and IPv6 fail, then the repo is likely down and you’ll need to reach out to the maintainer.