Please whitelist cPanel in your adblocker so that you’re able to see our version release promotions, thanks!

The Community Forums

Interact with an entire community of cPanel & WHM users!

Upgrade MySQL 5.6 to MariaDB 10.3 fails due to repo problem

Discussion in 'Database Discussion' started by SamSpade, Mar 3, 2019.

  1. SamSpade

    SamSpade Member

    Joined:
    May 18, 2013
    Messages:
    6
    Likes Received:
    0
    Trophy Points:
    1
    cPanel Access Level:
    Root Administrator
    As MySQL ran out of date I decided to upgrade from MySQL 5.6 to MariaDB 10.3.

    Unfortunately the migration wizard quits quite early while
    with the following error
    I therefore checked where to find the MariaDB-Client package

    Code:
    yum list all maria*
    Loaded plugins: fastestmirror, priorities, universal-hooks
    Loading mirror speeds from cached hostfile
     * EA4: 185.53.12.144
     * cpanel-addons-production-feed: 185.53.12.144
     * cpanel-plugins: 185.53.12.144
     * base: centosmirror.netcup.net
     * extras: centosmirror.netcup.net
     * updates: centosmirror.netcup.net
    11739 packages excluded due to repository priority protections
    Available Packages
    MariaDB-cassandra-engine.x86_64                                            10.0.38-1.el7.centos                                             MariaDB100                                 
    MariaDB-common.x86_64                                                      10.0.38-1.el7.centos                                             MariaDB100                                 
    MariaDB-compat.x86_64                                                      10.0.38-1.el7.centos                                             MariaDB100                                 
    MariaDB-connect-engine.x86_64                                              10.0.38-1.el7.centos                                             MariaDB100                                 
    MariaDB-oqgraph-engine.x86_64                                              10.0.38-1.el7.centos                                             MariaDB100                                 
    mariadb.x86_64                                                             1:5.5.60-1.el7_5                                                 centosmirror.netcup.net_centos_7_os_x86_64_
    mariadb-bench.x86_64                                                       1:5.5.60-1.el7_5                                                 centosmirror.netcup.net_centos_7_os_x86_64_
    mariadb-devel.i686                                                         1:5.5.60-1.el7_5                                                 centosmirror.netcup.net_centos_7_os_x86_64_
    mariadb-devel.x86_64                                                       1:5.5.60-1.el7_5                                                 centosmirror.netcup.net_centos_7_os_x86_64_
    mariadb-embedded.i686                                                      1:5.5.60-1.el7_5                                                 centosmirror.netcup.net_centos_7_os_x86_64_
    mariadb-embedded.x86_64                                                    1:5.5.60-1.el7_5                                                 centosmirror.netcup.net_centos_7_os_x86_64_
    mariadb-embedded-devel.i686                                                1:5.5.60-1.el7_5                                                 centosmirror.netcup.net_centos_7_os_x86_64_
    mariadb-embedded-devel.x86_64                                              1:5.5.60-1.el7_5                                                 centosmirror.netcup.net_centos_7_os_x86_64_
    mariadb-libs.i686                                                          1:5.5.60-1.el7_5                                                 centosmirror.netcup.net_centos_7_os_x86_64_
    mariadb-libs.x86_64                                                        1:5.5.60-1.el7_5                                                 centosmirror.netcup.net_centos_7_os_x86_64_
    mariadb-server.x86_64                                                      1:5.5.60-1.el7_5                                                 centosmirror.netcup.net_centos_7_os_x86_64_
    mariadb-test.x86_64                                                        1:5.5.60-1.el7_5                                                 centosmirror.netcup.net_centos_7_os_x86_64_
    
    As you can see there is no package MariaDB_client available.

    Double-checked that with the MariaDB repo only et voilá

    Code:
    yum --disablerepo="*" --enablerepo="MariaDB100" list available
    Loaded plugins: fastestmirror, priorities, universal-hooks
    Loading mirror speeds from cached hostfile
    Available Packages
    MariaDB-Galera-server.x86_64                                                             10.0.38-1.el7.centos                                                                MariaDB100
    MariaDB-Galera-test.x86_64                                                               10.0.38-1.el7.centos                                                                MariaDB100
    MariaDB-cassandra-engine.x86_64                                                          10.0.38-1.el7.centos                                                                MariaDB100
    MariaDB-client.x86_64                                                                    10.0.38-1.el7.centos                                                                MariaDB100
    MariaDB-common.x86_64                                                                    10.0.38-1.el7.centos                                                                MariaDB100
    MariaDB-compat.x86_64                                                                    10.0.38-1.el7.centos                                                                MariaDB100
    MariaDB-connect-engine.x86_64                                                            10.0.38-1.el7.centos                                                                MariaDB100
    MariaDB-devel.x86_64                                                                     10.0.38-1.el7.centos                                                                MariaDB100
    MariaDB-oqgraph-engine.x86_64                                                            10.0.38-1.el7.centos                                                                MariaDB100
    MariaDB-server.x86_64                                                                    10.0.38-1.el7.centos                                                                MariaDB100
    MariaDB-shared.x86_64                                                                    10.0.38-1.el7.centos                                                                MariaDB100
    MariaDB-test.x86_64                                                                      10.0.38-1.el7.centos                                                                MariaDB100
    galera.x86_64                                                                            25.3.25-1.rhel7.el7.centos                                                          MariaDB100
    jemalloc.x86_64                                                                          3.6.0-1.el7                                                                         MariaDB100
    jemalloc-devel.x86_64                                                                    3.6.0-1.el7                                                                         MariaDB100
    libzstd.x86_64                                                                           1.3.4-1.el7                                                                         MariaDB100
    The netcup mirror repo has a "priority=1" option enabled.

    Completely disabling the netcup mirror seems to be no good idea. Inserting a "priority=1" into the MariaDB100 repo seems to be useless as the upgrade wizard re-writes the repo each time.

    As the upgrade process iterates through the MariaDB versions what is the safest way to ensure that in every single migration step the actual needed MariaDB repo is used?
     
    #1 SamSpade, Mar 3, 2019
    Last edited by a moderator: Mar 3, 2019
  2. GOT

    GOT Get Proactive! PartnerNOC

    Joined:
    Apr 8, 2003
    Messages:
    1,366
    Likes Received:
    151
    Trophy Points:
    193
    Location:
    Chesapeake, VA
    cPanel Access Level:
    DataCenter Provider
    cpanel doesn't yet support MariaDB 10.3 and trying to install it outside of cpanel is not advisable.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  3. SamSpade

    SamSpade Member

    Joined:
    May 18, 2013
    Messages:
    6
    Likes Received:
    0
    Trophy Points:
    1
    cPanel Access Level:
    Root Administrator
    Running the release tier (v78.0.13), MariaDB 10.3 is the 'recommended' version.
     
  4. GOT

    GOT Get Proactive! PartnerNOC

    Joined:
    Apr 8, 2003
    Messages:
    1,366
    Likes Received:
    151
    Trophy Points:
    193
    Location:
    Chesapeake, VA
    cPanel Access Level:
    DataCenter Provider
    Oh ha I must have been checking a 76 server Sorry about that!

    Best bet would probably be a ticket then.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  5. cPanelMichael

    cPanelMichael Technical Support Community Manager Staff Member

    Joined:
    Apr 11, 2011
    Messages:
    47,009
    Likes Received:
    2,123
    Trophy Points:
    363
    cPanel Access Level:
    Root Administrator
    Twitter:
    Hello @SamSpade,

    Can you open a support ticket so we can take a closer look at the affected system? You can post the ticket number here and I'll link this thread to it.

    Thank you.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  6. SamSpade

    SamSpade Member

    Joined:
    May 18, 2013
    Messages:
    6
    Likes Received:
    0
    Trophy Points:
    1
    cPanel Access Level:
    Root Administrator
    Hello Michael,

    meanwhile I resolved that issue.

    When installing CentOS I chose the image provided by my hoster. During installation three additional repos created by the hoster pointing to the local CentOS mirror have been installed (well-intentioned to save bandwith). Each of these repos contains the "priority=1" option which has caused that problem. As the original CentOS repos were still in place I moved the three hoster repos from /etc/yum.repos.d/ and after updating and cleaning the yum repo re-run the upgrade succesfully.
     
  7. cPanelMichael

    cPanelMichael Technical Support Community Manager Staff Member

    Joined:
    Apr 11, 2011
    Messages:
    47,009
    Likes Received:
    2,123
    Trophy Points:
    363
    cPanel Access Level:
    Root Administrator
    Twitter:
    Hello @SamSpade,

    I'm glad to see you were able to solve the issue. Can you send me a private message with the name of your hosting provider? I'd like to reach out to them to provide details about this issue in an effort to reduce the number of systems affected by the same issue.

    Thanks!
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
Loading...

Share This Page

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice