Skip to content

KMS install error: mirro not found #8

@jamesaq12wsx

Description

@jamesaq12wsx

I have installed kms on centOS and now I want to change to RHEL.
And I saw this issue have installed on RHEL so I follow his step.
But when I run
yum install kurento-release epel-release -y
I got error about could not found mirror as this issue's second problem
This is full error message

epel/x86_64/metalink                                                                   | 4.9 kB  00:00:00
epel                                                                                   | 3.2 kB  00:00:00
pkgs.cloud                                                                             | 3.0 kB  00:00:00
https://rpm.nodesource.com/pub_7.x/el/7Server/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 404 - Not Found
Trying other mirror.
To address this issue please refer to the below knowledge base article

https://access.redhat.com/articles/1320623

If above article doesn't help to resolve this issue please open a ticket with Red Hat Support.



 One of the configured repositories failed (Node.js 7.x Packages for RHEL - x86_64),
 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=pkgs.cloud-nodejs-7.x ...

     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 pkgs.cloud-nodejs-7.x
        or
            subscription-manager repos --disable=pkgs.cloud-nodejs-7.x

     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=pkgs.cloud-nodejs-7.x.skip_if_unavailable=true

failure: repodata/repomd.xml from pkgs.cloud-nodejs-7.x: [Errno 256] No more mirrors to try.
https://rpm.nodesource.com/pub_7.x/el/7Server/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 404 - Not Found

I just follow his step but still not work. Did I do something wrong?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions