Yum Update Failing

(Michael Asher) #1

I am not able to run Yum Update. Here is the error I am receiving. Any thoughts?

yum update
Loaded plugins: auto-update-debuginfo, fastestmirror, versionlock
Loading mirror speeds from cached hostfile
Could not retrieve mirrorlist http://mirrorlist.sangoma.net/?release=$releasever&arch=x86_64&repo=os&dist=$dist&staging=$staging error was
14: HTTP Error 500 - Internal Server Error

One of the configured repositories failed (Unknown),
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=<repoid> ...

 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 <repoid>
        subscription-manager repos --disable=<repoid>

 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

        yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: sng-base/$releasever/x86_64

(Matteo Bignotti) #2

Hi there @masher81,

it’s possible that you tried executing the update exactly when the repository was regenerating itself. as I was working on it around that time :slight_smile:

(Michael Asher) #3

OK. It did start working again on it’s own. Thank you for the response.

(system) closed #4

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.