Issue Error Upgrading Plesk Obsidian 18.0.63 to 18.0.64: HTTPS Error 404 - Not Found (MaxScale Repo)

[Daerik]

Server operating system version

CentOS 7.9

Plesk version and microupdate number

18.0.63 #4

I am encountering an issue while attempting to upgrade from Plesk Obsidian 18.0.63 to 18.0.64 on a CentOS 7 server. During the upgrade, I receive the following error related to the MariaDB MaxScale repository:

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.

The upgrade process is failing due to this, with the following message:

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.

I have tried the suggestions from the CentOS wiki on yum errors (https://wiki.centos.org/yum-errors) without success. Has anyone encountered a similar issue or have suggestions for how to resolve it?

Should I disable the MaxScale repository, or is there an updated repository URL I should be using? Any help would be appreciated!

Thanks in advance.

--

Update: After continuing despite the MaxScale repository issue, I ran into the following error:

Trying to start service mariadb... active
Trying to establish test connection...
/usr/bin/mysql: Deprecated program name. It will be removed in a future release, use '/usr/bin/mariadb' instead
ERROR 2026 (HY000): TLS/SSL error: SSL is required, but the server does not support it
ERROR while trying to establish test connection

In my server mysql is linked to mariadb

[root@plesk ~]# ll /usr/bin/mysql
lrwxrwxrwx 1 root root 7 Sep 23 09:07 /usr/bin/mysql -> mariadb

I think my greatest concern is that we're not ready to make the jump to Alma from our CentOS servers. Should I just accept that 18.0.64 will be unavailable for my OS? I am running into the same error on all 8 of my CentOS servers.

--

My repo used:

[root@plesk ~]# cat /etc/yum.repos.d/mariadb.repo

[mariadb-main]
name = MariaDB Server
baseurl = https://dlm.mariadb.com/repo/mariadb-server/10.11/yum/rhel/7/x86_64
gpgkey = file:///etc/pki/rpm-gpg/MariaDB-Server-GPG-KEY
gpgcheck = 1
enabled = 1

[mariadb-maxscale]
# To use the latest stable release of MaxScale, use "latest" as the version
# To use the latest beta (or stable if no current beta) release of MaxScale, use "beta" as the version
name = MariaDB MaxScale
baseurl = https://dlm.mariadb.com/repo/maxscale/latest/yum/rhel/7/x86_64
gpgkey = file:///etc/pki/rpm-gpg/MariaDB-MaxScale-GPG-KEY
gpgcheck = 1
enabled = 1

[mariadb-tools]
name = MariaDB Tools
baseurl = Tools/rhel/7/x86_64/ - MariaDB
gpgkey = file:///etc/pki/rpm-gpg/MariaDB-Enterprise-GPG-KEY
gpgcheck = 1
enabled = 1

 

[Maarten]

I recommend that you create a new MariaDB repo baseurl using this tool:

Download MariaDB Server - MariaDB.org

REST API Release Schedule Reporting Bugs … Continue reading "Download MariaDB Server"

mariadb.org

 

[Daerik]

I recommend that you create a new MariaDB repo baseurl using this tool:

Download MariaDB Server - MariaDB.org

REST API Release Schedule Reporting Bugs … Continue reading "Download MariaDB Server"

mariadb.org

Thanks for the quick response. I've tried this but it just creates a new repo primarily for the MariaDB Server. Unfortunately my issue is with the MaxScale repo.

This is what the repo looks like built by the suggested tool:

# MariaDB 10.11 CentOS repository list - created 2024-09-23 15:16 UTC
# Download MariaDB Server - MariaDB.org
[mariadb]
name = MariaDB
# rpm.mariadb.org is a dynamic mirror if your preferred mirror goes offline. See A mirror manager system to simplify the distribution of MariaDB binaries and packages - MariaDB.org for details.
# baseurl = https://rpm.mariadb.org/10.11/centos/$releasever/$basearch
baseurl = https://mirror.its.dal.ca/mariadb/yum/10.11/centos/$releasever/$basearch
module_hotfixes = 1
# gpgkey = https://rpm.mariadb.org/RPM-GPG-KEY-MariaDB
gpgkey = https://mirror.its.dal.ca/mariadb/yum/RPM-GPG-KEY-MariaDB
gpgcheck = 1

So not having any issues with the MariaDB repo. Do you know if the MariaDB Foundation has a tool for MaxScale repositories?

 

[Maarten]

I'm not sure if there's a specific tool for MaxScale, but this article provides information to help you get started with MaxScale:

MariaDB Package Repository Setup and Usage

Executing and using a convenient shell script to set up the MariaDB Package Repository.

mariadb.com

 

[Daerik]

I'm not sure if there's a specific tool for MaxScale, but this article provides information to help you get started with MaxScale:

MariaDB Package Repository Setup and Usage

Executing and using a convenient shell script to set up the MariaDB Package Repository.

mariadb.com

Thanks for the resource! I did use the repository builder, which is how I initially set up my current repository. After adjusting MaxScale to maintain the current version instead of the latest, the warning about MaxScale is no longer appearing. However, the issue with MariaDB's TLS/SSL configuration still persists and seems to be the main problem blocking the update.

It looks like this update may be upgrading MariaDB from 10.11 to 11.4, which enforces TLS by default. From what I've gathered, if I hadn’t explicitly configured SSL, the server should have done it automatically.

I’ve come across suggestions to use openssl to generate my own certificates, but that would mean manually maintaining them, which I’d like to avoid. Ideally, I'd like future Plesk updates to be self-contained without requiring intervention each time.

Do you have any recommendations on how I could resolve this without having to manually manage the certificates for every update?

 

[Maarten]

You could create a custom-mysql.cnf in /etc/my.cnf.d/ containing the contents below and restart the MySQL server:

[mysql]
skip-ssl = true

Have you ever thought of migrating to Almalinux 8.*?

 

[Daerik]

You could create a custom-mysql.cnf in /etc/my.cnf.d/ containing the contents below and restart the MySQL server:

[mysql]
skip-ssl = true

Have you ever thought of migrating to Almalinux 8.*?

I tried using the skip-ssl configuration, but the same error occurred during the upgrade. I ended up following the instructions on MariaDB's website to enable TLS for the database server: Securing Connections for Client and Server

I used OpenSSL to self-sign a certificate, and after that, the upgrade completed successfully.

We’re planning to migrate to Alma soon, though our hosting provider won’t allow an in-place OS upgrade. Instead, they’re having us provision new servers and then migrate over.

Thanks again for your help!