Issue Upgrading my MariaDB. Issues.

[Dene Wilby]

Server operating system version

CentOS Linux 7.9.2009 (Core)

Plesk version and microupdate number

18.0.64 Update #1

So i'm trying to upgrade from MariaDB 10.3.39 to 10.11 in Plesk so I can upgrade to Joomla 5 and get the error:

The following package manager configuration files likely contain MariaDB repositories configuration
which is not compatible with this upgrader:
/etc/yum.repos.d/MariaDB.repo

To proceed with the upgrade, comment out or remove these repositories related to MariaDB.

So I go to follow the instructions here:

https://support.plesk.com/hc/en-us/...options-that-may-result-in-an-upgrade-failure

And then get issue on the first step of trying to edit the required files. I'm not well versed in SSH but am usually OK when following step by step instructions. Any help you can throw my way? Thanks.

[root@localhost ~]# yum install vim -y
Loaded plugins: fastestmirror, priorities
Loading mirror speeds from cached hostfile
epel/x86_64/metalink | 5.1 kB 00:00
* epel: d2lzkl7pfhq30w.cloudfront.net
PLESK_17_PHP56 | 2.9 kB 00:00
PLESK_17_PHP70 | 2.9 kB 00:00
PLESK_17_PHP71 | 2.9 kB 00:00
PLESK_17_PHP72 | 2.9 kB 00:00
PLESK_17_PHP73 | 2.9 kB 00:00
PLESK_17_PHP74 | 2.9 kB 00:00
PLESK_17_PHP80 | 2.9 kB 00:00
PLESK_17_PHP82 | 2.9 kB 00:00
PLESK_18_0_64-extras | 2.9 kB 00:00
base | 3.6 kB 00:00
centos7-els | 3.5 kB 00:00
centos7els-rollout-1 | 3.0 kB 00:00
centos7els-rollout-2 | 3.0 kB 00:00
centos7els-rollout-3 | 3.0 kB 00:00
centos7els-rollout-4 | 3.0 kB 00:00
centos7els-rollout-5 | 3.0 kB 00:00
centos7els-rollout-6 | 3.0 kB 00:00
extras | 2.9 kB 00:00
kolab-16 | 1.6 kB 00:00
http://yum.mariadb.org/10.3/centos7-amd64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below wiki article

yum-errors - CentOS Wiki

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



One of the configured repositories failed (MariaDB),
and yum doesn't have enough cached data to continue. At this point the only
safe thing yum can do is fail. There are a few ways to work "fix" this:

1. Contact the upstream for the repository and get them to fix the problem.

2. Reconfigure the baseurl/etc. for the repository, to point to a working
upstream. This is most often useful if you are using a newer
distribution release than is supported by the repository (and the
packages for the previous distribution release still work).

3. Run the command with the repository temporarily disabled
yum --disablerepo=mariadb ...

4. Disable the repository permanently, so yum won't use it by default. Yum
will then just ignore the repository until you permanently enable it
again or use --enablerepo for temporary usage:

yum-config-manager --disable mariadb
or
subscription-manager repos --disable=mariadb

5. Configure the failing repository to be skipped, if it is unavailable.
Note that yum will try to contact the repo. when it runs most commands,
so will have to try and fail each time (and thus. yum will be be much
slower). If it is a very temporary problem though, this is often a nice
compromise:

yum-config-manager --save --setopt=mariadb.skip_if_unavailable=true

failure: repodata/repomd.xml from mariadb: [Errno 256] No more mirrors to try.
http://yum.mariadb.org/10.3/centos7-amd64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
[root@localhost ~]#

 

[Sebahat.hadzhi]

Hello, @Dene Wilby. The repository mentioned in the error is now no longer shown as enabled in YUM. The one for MariaDB 10.11 should be /etc/yum.repos.d/mariadb.repo. Please try running the following command:

grep "http://yum.mariadb.org/10.3/" /etc/yum.repos.d/*

If grep returns an entry similar to /etc/yum.repos.d/MariaDB.repo:baseurl = http://yum.mariadb.org/10.3/centos7-amd64, please move the repository as follow:

mv /etc/yum.repos.d/MariaDB.repo /root/

I hope that helps.

 

[Dene Wilby]

AMAZING! This is all witchcraft to me but that worked

Thanks so much @Sebahat.hadzhi

 

[Dene Wilby]

One more question if I may. I am currently in the process of upgrading but I seem to be stuck at:

Upgrading the structure of all tables.

It flew through most of the tables but seems to be stuck on one of them with a progress bar just rotating.

 

[Sebahat.hadzhi]

I am glad to hear it worked. The process might be still running, so I would recommend allow it some more time. Alternatively, you may try running:

MYSQL_PWD=`cat /etc/psa/.psa.shadow` mysql_upgrade -uadmin

 

[Dene Wilby]

Thanks. It's still stuck at the same place. However, all my websites are working and reporting that they are using 10.11.

Should I close the dialog and use the command you've given me?

 

[Dene Wilby]

It's actually timed out. I've logged back in and it says i'm on 10.11.9 and everything seems to be running OK.

Do you think it's safe to say that all went OK even though the last step didn't seem to have been taken?