mariadb update error: Page 2 - Enhance Control Panel

mariadb update error

andreaslindgren

I get the same error so it seems to be a problem with the repo at the moment.

apt-get -o Acquire::ForceIPv4=true upgrade has no effect on this issue.

marowi

I got the same error. Interestingly, it only happened on the older of the three servers running MariaDB databases. The newer one had no issues.

Adam

Some older versions of Enhance used the mariadb official install script to configure the apt repo and this configures the maxscale repo which Enhance does not require. You can remove that line entirely from /etc/apt/sources.list.d/mariadb.list and it will prevent any future errors. I don't know why the error is happening, it could be that mariadb had some kind of mirror sync issue.

marowi

Hi Adam

Thanks for the hint about removing the MaxScale line.

However, comparing the mariadb.list across my servers, I noticed that the affected server has a significantly different configuration than the one that works fine:

Server with the error:

deb [arch=amd64,arm64] https://dlm.mariadb.com/repo/mariadb-server/11.4/repo/ubuntu noble main
deb [arch=amd64,arm64] https://dlm.mariadb.com/repo/mariadb-server/11.4/repo/ubuntu noble main/debug
deb [arch=amd64,arm64] https://dlm.mariadb.com/repo/maxscale/latest/apt noble main

Server without the error:

deb [arch=amd64,arm64 signed-by=/usr/share/keyrings/mariadb-enhance.gpg] https://deb.mariadb.org/11.4/ubuntu noble main

It looks like the affected server was set up using the official MariaDB install script at some point, while the working server uses Enhance's own repo mirror with a dedicated GPG keyring.

Should I just remove the MaxScale line for now, or would it make sense to migrate the entire mariadb.list on the affected server to the Enhance format (using deb.mariadb.org with the signed-by keyring)? And if so, is that something I should do manually, or will Enhance handle that automatically at some point?

Edit: After commenting out the Maxscale line, the update worked.

Adam

marowi Yes that's the old installer vs the new. The reason we switched to deb.mariadb.org is that dlm.mariadb.com seems to block some IP ranges used by our customers. If the config is otherwise working then removing the maxscale line should be enough.

« Previous Page