Skip to main content

CPANEL-40434 - Cannot upgrade mariadb 10.0 to 10.1, repo is not found

Comments

11 comments

  • akhand
    I am trying to update mariadb from 10.0 to 10.2 on a centos7 with cpanel/whm, but with no success. The problem seems to be that there is no yum repo anymore for mariadb 10.1 and the wizard is trying to do a step by step upgrade from 10.0 to 10.2, by first doing the 10.0 to 10.1 upgrade. The error is: The following error occurred while attempting to install the requested packages with yum:
    0
  • cPRex Jurassic Moderator
    Running "yum clean all" along with "yum makecache" would be a good starting point for this issue, as that would ensure there are no issues with Yum itself on the system. Can you do that and see if that gets things working?
    0
  • cPRex Jurassic Moderator
    Update -
    0
  • timmit
    We have an fix, but cPanel preventing the the fix: Edit /etc/yum.repos.d/MariaDB101.repo to: [MariaDB101] name = MariaDB101 baseurl = https://archive.mariadb.org/mariadb-10.1.48/yum/centos6-amd64/ gpgkey=https://yum.mariadb.org/RPM-GPG-KEY-MariaDB gpgcheck=1
    But mysql-upgrade of cPanel is writing over every time the file... An chattr +i gives the error that the MariaDB101.repo is immutible. We can do the mysql upgrade by hand, but we don't know if that will work correctly. (And yes it is wrong to upgrade to an EOL version, but if you are on an old mysql version you need to take this path...)
    0
  • timmit
    Ok the fix is to bypass the broken generated cPanel repo: put the above to the end of the /etc/yum.conf so you get: # This is the default, if you make this bigger yum won't see if the metadata # is newer on the remote and so you'll "gain" the bandwidth of not having to # download the new metadata and "pay" for it by yum not having correct # information. # It is esp. important, to have correct metadata, for distributions like # Fedora which don't keep old packages around. If you don't like this checking # interupting your command line usage, it's much better to have something # manually check the metadata once an hour (yum-updatesd will do this). # metadata_expire=90m # PUT YOUR REPOS HERE OR IN separate files named file.repo # in /etc/yum.repos.d [MariaDB101] name = MariaDB101 baseurl = https://archive.mariadb.org/mariadb-10.1.48/yum/centos6-amd64/ gpgkey=https://yum.mariadb.org/RPM-GPG-KEY-MariaDB gpgcheck=1
    PS the bbcode editor is broken I you want to use the code tag....
    0
  • chalupa
    Update -
    0
  • cPRex Jurassic Moderator
    You can move from MySQL 5.7 to higher versions of MariaDB. You can't move from MySQL 8 to MariaDB.
    0
  • baronn
    Having a similar issue on multiple boxes this morning. Already on mariadb 10.3 and when daily cron ran this morning for multiple boxes it came with the error:
    0
  • matt1206
    Having a similar issue on multiple boxes this morning. Already on mariadb 10.3 and when daily cron ran this morning for multiple boxes it came with the error:
    0
  • baronn
    0
  • cPRex Jurassic Moderator
    We're watching on our end and I'll be updating the main thread at with more details once I have them. I'm sure MariaDB will get to this one quickly.
    0

Please sign in to leave a comment.