Update & upgrade error due to mariadb repo issue

Hi guys, I had an issue today with a server and this is how I solved it, to be honest I don’t know if was correct solution though.

I have 3 production server 2 mines and 1 of a client, mines are on Hostinger (main) and 2nd on Contabo, my client’s VPS is on contabo too, yesterday (May 9th) I have updated and upgraded both contabo servers and clean them, I left main Hostinger server for today due to more work after apt update all ok, but after apt upgrade got errors:

Err:1 https://dlm.mariadb.com/repo/mariadb-server/11.4/repo/debian bookworm/main amd64 mysql-common all 1:11.4.6+maria~deb12
404 Not Found [IP: 104.17.191.14 443]
Err:2 https://dlm.mariadb.com/repo/mariadb-server/11.4/repo/debian bookworm/main amd64 mariadb-common all 1:11.4.6+maria~deb12
404 Not Found [IP: 104.17.191.14 443]
Err:3 https://dlm.mariadb.com/repo/mariadb-server/11.4/repo/debian bookworm/main amd64 mariadb-server amd64 1:11.4.6+maria~deb12
404 Not Found [IP: 104.17.191.14 443]
Err:4 https://dlm.mariadb.com/repo/mariadb-server/11.4/repo/debian bookworm/main amd64 mariadb-server-core amd64 1:11.4.6+maria~deb12
404 Not Found [IP: 104.17.191.14 443]
Err:5 https://dlm.mariadb.com/repo/mariadb-server/11.4/repo/debian bookworm/main amd64 mariadb-client amd64 1:11.4.6+maria~deb12
404 Not Found [IP: 104.17.191.14 443]
Err:6 https://dlm.mariadb.com/repo/mariadb-server/11.4/repo/debian bookworm/main amd64 mariadb-client-core amd64 1:11.4.6+maria~deb12
404 Not Found

I have edited then file: nano /etc/apt/sources.list.d/mariadb.list

and I have only changed URL from https://dlm.mariadb.com/repo/mariadb-server/11.4/repo/debian TO https://deb.mariadb.org/11.4/debian

After that server updated and upgraded ok, looks everything is working normal, but, it was like the correct solution for it ?

My contabo server was able to upgrade today due to only php packages to update, nothing related to mariadb, but still on old URL, should I update that too ?

and another question, how can this error 404 affect to new Hestia installations?

Hi @luisedofon

It looks like a temporary connection issue. I have no problems with the current official repository:

❯ cat /etc/apt/sources.list.d/mariadb.list
deb [arch=amd64 signed-by=/usr/share/keyrings/mariadb-keyring.gpg] https://dlm.mariadb.com/repo/mariadb-server/11.4/repo/debian bookworm main
❯ apt update
[...]
Hit:14 https://dlm.mariadb.com/repo/mariadb-server/11.4/repo/debian
[...]
Debian_12  InRelease
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done

As far as I know, dlm.mariadb.com is the official repository managed directly by MariaDB, while deb.mariadb.org points to mirrors maintained by external providers such as hosting companies, universities, etc.

That said, there shouldn’t be any problem using https://deb.mariadb.org/11.4/debian.

1 Like

Thanks again @sahsanu , I will set back official URL to main server, I usually do maintenance every weekend, so will check it back next weekend :grin:

You’re welcome :hugs:

There’s no need to wait, you can run apt update and if there are no errors, the repository is working fine. You don’t need to upgrade anything unless you want to.

That’s the weird thing… hehe, I never got issues after running apt update, no matter what repo was on the file, after apt update, the command line confirmed eveything was ok and there was like 67 packages to upgrade in my case, the errors were shown directly after apt upgrade -y :thinking:

Err:1 https://dlm.mariadb.com/repo/mariadb-server/11.4/repo/debian bookworm/main amd64 mysql-common all 1:11.4.6+maria~deb12
404 Not Found [IP: 104.17.191.14 443]
Err:2 https://dlm.mariadb.com/repo/mariadb-server/11.4/repo/debian bookworm/main amd64 mariadb-common all 1:11.4.6+maria~deb12
404 Not Found [IP: 104.17.191.14 443]
Err:3 https://dlm.mariadb.com/repo/mariadb-server/11.4/repo/debian bookworm/main amd64 mariadb-server amd64 1:11.4.6+maria~deb12
404 Not Found [IP: 104.17.191.14 443]
Err:4 https://dlm.mariadb.com/repo/mariadb-server/11.4/repo/debian bookworm/main amd64 mariadb-server-core amd64 1:11.4.6+maria~deb12
404 Not Found [IP: 104.17.191.14 443]
Err:5 https://dlm.mariadb.com/repo/mariadb-server/11.4/repo/debian bookworm/main amd64 mariadb-client amd64 1:11.4.6+maria~deb12
404 Not Found [IP: 104.17.191.14 443]
Err:6 https://dlm.mariadb.com/repo/mariadb-server/11.4/repo/debian bookworm/main amd64 mariadb-client-core amd64 1:11.4.6+maria~deb12
404 Not Found```

You are right, I’ve tested it trying to install a new package on an Ubuntu VM and I also get the 404 error:

❯ apt install mariadb-plugin-provider-lzo
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following NEW packages will be installed:
  mariadb-plugin-provider-lzo
0 upgraded, 1 newly installed, 0 to remove and 4 not upgraded.
Need to get 4,678 B of archives.
After this operation, 36.9 kB of additional disk space will be used.
Err:1 https://dlm.mariadb.com/repo/mariadb-server/11.4/repo/ubuntu noble/main amd64 mariadb-plugin-provider-lzo amd64 1:11.4.6+maria~ubu2404
  404  Not Found [IP: 104.18.135.24 443]
E: Failed to fetch https://dlm.mariadb.com/repo/mariadb-server/11.4/repo/ubuntu/pool/main/m/mariadb/mariadb-plugin-provider-lzo_11.4.6%2bmaria%7eubu2404_amd64.deb  404  Not Found [IP: 104.18.135.24 443]
E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?

I’ll try to check what’s going on, maybe they restricted the access to this repo only for paid customers…

1 Like

Hello!
I also confirm the issue exists on my side :frowning:

2 Likes

I have also encountered this issue on multiple Ubuntu versions.

1 Like

You can try as temporal solution what I did by editing MariaDB sources file in order to complete all server upgrades, my main server looks to be working ok in regards databases due to multiple wordpress sites there, but not sure about exactly issue is.

In my case is under Debian, so I guess we can confirmed issue is related with repo then.

1 Like

You are right!
I’ve changed
deb [arch=amd64 signed-by=/usr/share/keyrings/mariadb-keyring.gpg] https://dlm.mariadb.com/repo/mariadb-server/11.4/repo/debian bookworm main

to

deb [arch=amd64 signed-by=/usr/share/keyrings/mariadb-keyring.gpg] https://dlm.mariadb.com/repo/mariadb-server/11.8/repo/debian bookworm main
And it seems issue fixed for now :slight_smile:

Not an expert, but just in case on mariadb.com what I can see about versions is that 11.8 still under development (non-production), not sure if this will upgrade your database version then and could cause issues as is not an stable version yet, will check this on a test server, in my case I decided to use mariadb.org for same 11.4 version.

Update: Just tested on VM server and confirmed, MariaDB upgraded to 11.8.1, we need to take this in consideration on production servers hehe.

2 Likes

I didn’t find a straight answer but I did see this JIRA ticket opened on May 9th:

And last answer:

So it looks like version 11.4.6 has a bug affecting performance, and since the official repo works for other versions; 10.6, 10.11, 11.8, etc. Maybe they’ve removed 11.4.6 from their repos until a new version is available. I’m just guessing here. :wink:

2 Likes

Seems it’s working again BUT they have removed version 11.4.6 from their repo (right now only versions 11.4.4 and 11.4.5 are available).

2 Likes

Great news @sahsanu , thanks for keeping us updated :grinning_face_with_smiling_eyes: , I was checking my VPS today and notice that even with repo change on main server and the Contabo ones I was able to upgrade on May 9th before issue, all of them are running under 11.4.5

2 Likes

Was broken for me just now, but I ran their repo setup tool from here

And it fixed things.
However it did upgrade me without asking, essentially changing.

deb [arch=amd64 signed-by=/usr/share/keyrings/mariadb-keyring.gpg] https://dlm.mariadb.com/repo/mariadb-server/10.11/repo/ubuntu jammy main
to
deb [arch=amd64,arm64] https://dlm.mariadb.com/repo/mariadb-server/11.rolling/repo/ubuntu jammy main

Because you changed the version to 11.rolling, I don’t recommend using the rolling release in a production server.

Well I didn’t change that, the automatic tool did. Now trying to roll back to 10.11 where I was.

Oh nice, it also deleted the gpg key.

And rolling back to 11.4 it decides it will copy all your databases to a different folder and initialize a new one.

Jeez, people, please don’t touch that automatic script. Its a nightmare. Anyway, back up and running now. I was forced up from 10.11 to 11.4, but all seems good now

1 Like

OK, got this solved on one server. Seems the index files are pointing to non-existant files. So clear out the old indexes, and re-run apt update

rm /var/lib/apt/lists/dlm.mariadb.com*
apt update 
apt upgrade 

And suddenly mariadb-server doesn’t need to upgrade any more.

2 Likes

FYI

Today, MariaDB has released new versions, 10.11.13 and 11.4.7 to fix the regressions introduced in versions 10.11.12 and 11.4.6.

4 Likes