• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

Issue Cannot upgrade Plesk, error with mariadb-maxscale in installer

abanico

New Pleskian
Server operating system version
CentOS Linux 7.9.2009
Plesk version and microupdate number
Plesk Obsidian 18.0.66, update 2
Hi all,

I have a server with CentOS 7 (I plan to migrate to a server with Almalinux during the summer) that I cannot upgrade from version 18.0.62 #2 because when I run the installer, it gives me this error

Enabled repositories check

https://dlm.mariadb.com/repo/maxscale/latest/yum/rhel/7/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article

https://wiki.centos.org/yum-errors

If above article doesn't help to resolve this issue please use https://bugs.centos.org/.

Unable to create yum cache for 'mariadb-maxscale' OS repository.
Make sure the repository is available, otherwise either disable it or fix its configuration, then try again.

The problem is that the error comes up even if I try to add a Plesk component (for example a PHP version).

I have searched the forum and I see that there are some people who have the same failure but I see nothing conclusive, and I fear that if I ignore the error (it gives me the option to ignore it) when I upgrade Plesk stops working and then I am in a major mess.

If someone has had this problem and knows how to solve it (or directly, there is no possibility to solve it and you have to move to Almalinux) I would be very grateful.

Cheers!
 
Disable the repository. Yum doesn't complete any actions because one of the repositories (the MariaDB one) no longer exists.
The repositories are in /etc/yum.repos.d/. Find the file that contains the MariaDB URL and change enabled from 1 to 0.
 
Hi Raul A. and alvarezcruz!

The main fear I have with disabling / ignoring the MariaDB repository, is that when upgrading from Plesk Obsidian 18.0.66 update 2 to the latest version of Plesk (18.0.69), the upgrade will fail, or not start the database engine after the upgrade, as mentioned in this thread:


MariaDB version 10.11.9 is installed on the system right now. Will I have problems upgrading if I disable the repository and max-scale is not installed?

Thanks!
 
That repository no longer exists. The upgrade fails because your package manager has a broken repository configured. If you disable the broken repository, the Plesk upgrade will work.

Plesk still supports CentOS 7. I don't see any issues with using MariaDB 10.11. MariaDB 11.4 is supported since Plesk 18.0.64.
 
Back
Top