Tag Archives: yum

One of the configured repositories failed (Unknown), and yum doesn’t have enough cached data to cont

The Esaote installation dependency report error message is as follows
One of the configured repositories failed (unknown).
and yum doesn’t have enough cached data to continue. At this point, the only thing yum can do is
The safe thing to do is to fail. There are ways to “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>
    or
        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
    compromise:

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

Solution
can start by configuring yum sources

    1. is generally a network problem, check whether the network is unobvious. Secondly, if you use the company’s internal network, there will be restrictions, it is recommended to change the agent (there may be several agents in the company, but one happens to be limited, so you need to change the agent), you can ask colleagues to. Proxy parameter name error: yum’s proxy should use

proxy

    1. , instead of

http_proxy</code b> or https_proxy, but it is recommended to write all three, which must be correct.

For example: yum install-y XXX –proxy IP –http_proxy IP –https_proxy

Alicloud centos8 reports an error “error: failed to synchronize cache for repo ‘EPEL modular'”

ali cloud has been online centos8 system, the 8 series is relatively new, ali cloud bug is still there, use yum unexpectedly can not, the system default did not install git, want to install yum install git directly Error “Error: Failed to synchronize cache for repo ‘epel-modular'”, extend source Error, baidu has no solution, it can only solve by itself!

the solution is simple:

scheme 1: directly delete /etc/yum.repos. D (first backup)

directory epel beginning file

would be yum.

scheme 2:

yum succeeded but the prompt program does not exist and cannot install

do not delete /etc/yum.repos. D inside the file

edit

vi /etc/resolv.conf

and

nameserver 114.114.114.114

save

and then execute yum successfully

ali cloud recently launched centos8 can’t yum, DNS can’t resolve the extended library domain name. Hey, their family is a little careless about their operation and maintenance