Apt-get upgrade mariadb is 404

v3
#1

I’m running the usual update upgrade process and i’ve recently been getting this error:

Err http://sfo1.mirrors.digitalocean.com/mariadb/repo/10.1/ubuntu xenial/main amd64 libmariadbclient18 amd64 10.1.15+maria-1~xenial 404 Not Found [IP: 198.199.99.226 80]

is there an easy way to fix it?

thanks!

#2

I’d love to know if there’s a way to fix this issue, too. The DigitalOcean apt source mirror is added by EasyEngine. Surely it’s not just a case of waiting until there’s another upgrade to MariaDB for the 404 errors to be fixed.

#3

It is weird, but I have 64 VPSs running EasyEngine (not in DigitalOcean), and none of them are showing any misbehavior regarding MariaDB.

Do you want me to share some information from my VPSs, or something?

#4

Looks like I’m in the same boat…

root@ee:~# apt upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following packages will be upgraded:
  mysql-common
1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 8,490 B of archives.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] Y
Err:1 http://sfo1.mirrors.digitalocean.com/mariadb/repo/10.1/ubuntu xenial/main i386 mysql-common all 10.1.15+maria-1~xenial
  404  Not Found [IP: 198.199.99.226 80]
Err:1 http://sfo1.mirrors.digitalocean.com/mariadb/repo/10.1/ubuntu xenial/main i386 mysql-common all 10.1.15+maria-1~xenial
  404  Not Found [IP: 198.199.99.226 80]
E: Failed to fetch http://sfo1.mirrors.digitalocean.com/mariadb/repo/10.1/ubuntu/pool/main/m/mariadb-10.1/mysql-common_10.1.15+maria-1~xenial_all.deb  404  Not Found [IP: 198.199.99.226 80]

E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?
#5

removed

#6

@tyrro Was about to try this and it looks like you’ve removed your post. Was there a problem?

Thanks…

#7

I have checked the server and the paths are correct so it looks like the problem happens duringv the upgrade so these paths are somewhere in the upgrade script not easily accessible to everyone. Need to check where exactly are they located.

#8

I’ve opened a Github issue for this as well, perhaps I’ll find an answer there (I hope). If I do, I’ll be sure to update this thread with my solution.

Anyone have any luck on their own yet? Thanks!

#9

This is an issue with DigitalOcean repositories, please stop complaining as if it was EasyEngine error.

#10

@janiosarmento – I’m not complaining, thank you. I’m simply asking if anyone knows how to fix the issue.

I’ll follow up with DigitalOcean support and update with my findings so that we can stop complaining and bothering people.

Thanks…

#11

@tyrro @purbeckpixels @FalconX1 – I just heard back from DigitalOcean and believe I’ve resolved the issue with their assistance.

rm -rf /var/lib/apt/lists/* 
apt-get clean 
apt-get update
#12