Operating System & Version
CentOS v7.9.2009
cPanel & WHM Version
104.0.5

mencargo

Member
Jul 30, 2013
16
2
53
Mexico
cPanel Access Level
Root Administrator
I cannot upgrade cPanel / EasyPHP / MariaDB because of an issue with the following mirror:

Repo file:
/etc/yum.repos.d/MariaDB101.repo

Code:
[MariaDB101]
name = MariaDB101
baseurl = https://yum.mariadb.org/10.1/centos7-amd64
gpgkey=https://yum.mariadb.org/RPM-GPG-KEY-MariaDB
gpgcheck=1
The update log states:

https://yum.mariadb.org/10.1/centos7-amd64/repodata/repomd.xml: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
Indeed the 10.1 does not exist, although other versions do:

How should I resolve this?
 

cPRex

Jurassic Moderator
Staff member
Oct 19, 2014
17,470
2,843
363
cPanel Access Level
Root Administrator
Hey there! It's important to note that cPanel doesn't manage those mirrors, as those get configured straight from the MariaDB repositories without our intervention.

We had a similar issue with MariaDB 10.0 when they removed that from the repositories, which you can read about here:


so I would expect the same workaround to apply here. Can you try upgrading to MySQL 5.7 and then moving on from there?
 

mencargo

Member
Jul 30, 2013
16
2
53
Mexico
cPanel Access Level
Root Administrator
Yep, seems to be that same issue.
I cannot upgrade to MySQL because it's currently in MariaDB 10.0 and I believe there's no way to go back to MySQL, right?
Besides migrating to a new server.
 

mencargo

Member
Jul 30, 2013
16
2
53
Mexico
cPanel Access Level
Root Administrator
cPanel & WHM v104.0.5 (STANDARD)
CentOS v7.9.2009
MariaDB 10.0

The upgrade options for MariaDB are 10.1, 10.2, 10.3, 10.5 and 10.6 but cannot complete them.
EasyApache fails to show options, so it's stuck with the current PHP version
 

cPRex

Jurassic Moderator
Staff member
Oct 19, 2014
17,470
2,843
363
cPanel Access Level
Root Administrator
Thanks for that - I'm personally not sure of an appropriate workaround at this time, that wouldn't cause issues with the packages on the server.

Could you open a support ticket with our team so we can check this situation more in-depth?