Facebook
TwitterSorry, I cannot. Again, there's no "conversion" per se. Mostly just removal of incompatible settings.
Question Try our new tool to upgrade your old MariaDB server from Plesk UI
- Thread starter dash
- Start date
@VNick,
I believe that we - in a far away past - did a similar thing in order to facilitate dbase upgrades.
If and when I have some time, I will have a look at the old development files and try to find the solution that we implemented back then.
It worked like a charm, so it cannot do harm to update it and share it.
I will contact you by personal message if and when I am able to do something.
Kind regards...
Hi to all
Maybe this the wrong site to post this, so feel free to change the post or delete it.
I've tried to update MariaDB from 10.11.15 to 11.4 using this tool.
Something has changed in a fewer days, because I do the process some days ago and it worked w/o issues.
Seems like MariaDB has changed their repo files, url or whatever like this.
Now the tool report that was unable to contact with
This error comes from CloudFlare and it means that the backed server doesn't retrun a response.
MariaDB repositories are working, if you modify the
Maybe this the wrong site to post this, so feel free to change the post or delete it.
I've tried to update MariaDB from 10.11.15 to 11.4 using this tool.
Something has changed in a fewer days, because I do the process some days ago and it worked w/o issues.
Seems like MariaDB has changed their repo files, url or whatever like this.
Now the tool report that was unable to contact with
https://downloads.mariadb.com/MariaDB/ because it returns a 521 error.This error comes from CloudFlare and it means that the backed server doesn't retrun a response.
MariaDB repositories are working, if you modify the
/etc/yum.repo.d/mariadb.repo and change 10.11 to 11.4 it is able to list the packages (and I suppose to install it)@Longi,
There is a general answer to the "521 error question", being that something is wrong on the Cloudflare side.
That is the central assumption that one has to use when being confronted with a 521 error from Cloudflare.
In this case (and most other cases), one can simply check the "erroneous" URL in a browser, since Cloudflare will then provide some additional information.
At this moment, opening the URL
will give you an indication that something is wrong at "Cloudflare Location : Amsterdam".
This is not new, it happens a lot since 18 November.
In essence, the statement
is not a good workaround, for the reasons that :
1 - any change of repo configs might work if there is some re-routing on the Cloudflare side, but that is not a guarantee that all we be working fine : issues on the Cloudflare side seem to persist and some of these issues are / have been resolved with some effects on "network continuity"
2 - any change of repo configs that involve version updates are not wise if you want to run an upgrade : the upgrade itself needs to adjust all config files
Stated differently, one has to sit out the situation until Cloudflare has resolved issues and/or finalized "network maintenance" (as they call it, it is probably a very nice definition for "bug resolution") or until MariaDB repos are available without interference of Cloudflare.
In summary, I can only recommend to be cautious and to have some patience.
After all, messing around with the beating heart of your system (the database) can cause heart attacks.
Kind regards.....
There is a general answer to the "521 error question", being that something is wrong on the Cloudflare side.
That is the central assumption that one has to use when being confronted with a 521 error from Cloudflare.
In this case (and most other cases), one can simply check the "erroneous" URL in a browser, since Cloudflare will then provide some additional information.
At this moment, opening the URL
will give you an indication that something is wrong at "Cloudflare Location : Amsterdam".
This is not new, it happens a lot since 18 November.
In essence, the statement
is not a good workaround, for the reasons that :
1 - any change of repo configs might work if there is some re-routing on the Cloudflare side, but that is not a guarantee that all we be working fine : issues on the Cloudflare side seem to persist and some of these issues are / have been resolved with some effects on "network continuity"
2 - any change of repo configs that involve version updates are not wise if you want to run an upgrade : the upgrade itself needs to adjust all config files
Stated differently, one has to sit out the situation until Cloudflare has resolved issues and/or finalized "network maintenance" (as they call it, it is probably a very nice definition for "bug resolution") or until MariaDB repos are available without interference of Cloudflare.
In summary, I can only recommend to be cautious and to have some patience.
After all, messing around with the beating heart of your system (the database) can cause heart attacks.
Kind regards.....
mahmut ozdemir
Basic Pleskian
@mahmut ozdemir
It is very likely that there is a Cloudflare related issue.
However, a "web server" is something different than a "repo server" - you are trying to reach a "mirror", a repo server containing data to download.
MariaDB mirrors (with the exception of one that you should not be bothered by) are working fine.
So, for some reason, you cannot - properly - access the mirrors of MariaDB and, since there is a CloudFlare issue (maintenance or issue), it cannot be excluded that your issues are related to the Cloudflare issues.
Please check your firewall and make sure that you do not have the IPs of the MariaDB mirrors blocked.
Kind regards.....
It is very likely that there is a Cloudflare related issue.
However, a "web server" is something different than a "repo server" - you are trying to reach a "mirror", a repo server containing data to download.
MariaDB mirrors (with the exception of one that you should not be bothered by) are working fine.
So, for some reason, you cannot - properly - access the mirrors of MariaDB and, since there is a CloudFlare issue (maintenance or issue), it cannot be excluded that your issues are related to the Cloudflare issues.
Please check your firewall and make sure that you do not have the IPs of the MariaDB mirrors blocked.
Kind regards.....
mahmut ozdemir
Basic Pleskian
Thanks for the reply, I checked all security but could not find the problem.
I did these
systemctl stop firewalld
systemctl disable firewalld
systemctl disable iptables
systemctl mask firewalld
chkconfig iptables off
@trialotto
Thanks for your response, time and patience.
I'm aware about these changes in the repo files, and that the changes doesn't work whith the Plesk tool to upgrade the DB.
I only checked if the repo servers and files are still "here with us" and if the problem are the repo servers itself or any other cause (CloudFale, for example).
The bad news are that Almalinux 9.6 version can't be upgraded to the 9.7 until the DB get upgraded, due incompatiblities between the installed packages and some of the new one.
Thanks.
Thanks for your response, time and patience.
I'm aware about these changes in the repo files, and that the changes doesn't work whith the Plesk tool to upgrade the DB.
I only checked if the repo servers and files are still "here with us" and if the problem are the repo servers itself or any other cause (CloudFale, for example).
The bad news are that Almalinux 9.6 version can't be upgraded to the 9.7 until the DB get upgraded, due incompatiblities between the installed packages and some of the new one.
Thanks.
Hi, everyone. I just want to add that our team reviewed this matter and, unfortunately, there is no way to change the repository used to obtain MariaDB packages within the scope of the MariaDB update tool. Thus, apart from the manual upgrade option, the only other alternative is to wait until the MariaDB repository is fixed.
egyklikkcom
New Pleskian
it works now!
