Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-36052

MariaDB Repos are Down 500 Error

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • 10.6.19
    • N/A
    • Repositories
    • CentOS 7

    Description

      I'm attempting to run yum update

      [root@darwin ~]# yum update
      Loaded plugins: fastestmirror, priorities, universal-hooks
      Loading mirror speeds from cached hostfile
      epel/x86_64/metalink                                  | 5.1 kB     00:00     
       * EA4: 185.125.185.32
       * EA4-experimental-c7: 185.125.185.32
       * cpanel-addons-production-feed: 185.125.185.32
       * cpanel-plugins: 185.125.185.32
       * epel: d2lzkl7pfhq30w.cloudfront.net
      EA4                                                   | 2.9 kB     00:00     
      EA4-experimental-c7                                   | 2.9 kB     00:00     
      cpanel-addons-production-feed                         | 2.9 kB     00:00     
      cpanel-plugins                                        | 2.9 kB     00:00     
      https://archive.mariadb.org/mariadb-10.6/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 500 - Internal Server Error
      Trying other mirror.
       
       
       One of the configured repositories failed (MariaDB106),
       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=MariaDB106 ...
       
           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 MariaDB106
              or
                  subscription-manager repos --disable=MariaDB106
       
           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=MariaDB106.skip_if_unavailable=true
       
      failure: repodata/repomd.xml from MariaDB106: [Errno 256] No more mirrors to try.
      https://archive.mariadb.org/mariadb-10.6/yum/centos/7/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 500 - Internal Server Error
      

      Also, when I go to this page it also shows a 500 error
      https://archive.mariadb.org/yum/

      Attachments

        Activity

          People

            Unassigned Unassigned
            blazingraptor Brian Corson
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Git Integration

                Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.