Установка centos 7 ошибка при настройки базового репозитория

I’ve created bootable USB flash drive using recommended LiveUSB Creator using CentOS-7-x86_64-Everything-1503-01.iso.

Now being at Installation Summary screen I’m getting Error setting up base repository. When I click on Verify at Installation Source screen I get This media is not good to install from. Rather cryptic error message…

I’ve also tried switch to On the network and insert http://mirrors.kernel.org/centos/7/os/x86_x64 with no success.

Additional info: Installing on HP EliteBook 8540w

asked Aug 3, 2015 at 16:56

You have an error in the mirror URL (and extra x at x64) it should be http://mirrors.kernel.org/centos/7/os/x86_64.

Do not use LiveUSB creator, it doesn’t work with this release of CentOS.

I had the same problem, I recreated the USB flash drive using dd under Linux ( dd bs=4M if=CentOS-7-x86_64-Everything-1503-01.iso of=/dev/sd[letter of your USB drive] ), and it worked like a charm.

If you do not have access to a Linux machine, you need to report this problem to LiveUSB-Creator developers and/or CentOS developers.

when you install centos 7 on network, you may config installation source.

when you input the url under the label ‘On the network:’, you’ll see the check box already checked that means ‘This URL refers to a mirror list’ , disable that.

answered Aug 2, 2016 at 13:29

I experienced the same problem. It is working after I switch to Win32 Disk Imager.

Please try using another USB ISO burner. It should work. There is a list of working programs for the task.

answered Aug 3, 2016 at 15:53

I downloaded the 32-bit CentOS 7 Netinstall version from http://mirror.centos.org/altarch/7/isos/i386/, and used the http://mirror.centos.org/altarch/7/os/i386/ as the repository during installation in virtualbox (Virtual machine RAM: 770MB, HDD: 8GB). I have already switched on the networks in the installation screen.

Whatever I try I am getting the same error: ‘Error setting up base repository»

• centos
• system-installation

asked Feb 8, 2016 at 9:54

Sorted by:

Reset to default

Sign up or log in

Sign up using Facebook

Sign up using Email and Password

Post as a guest

Name

Hello I have download the minimal release of CENTOS 7 at this url
link download ISO centos 7.x

All work correctly…the PING and the network is OK. I ping to external HOST for example.

But when I digit :

[root@localhost ~]# yum update
Loaded plugins: fastestmirror


 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. Disable the repository, 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>

     4. 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

Cannot find a valid baseurl for repo: base/7/x86_64

Why?

This is another command:


root@localhost ~]# yum repolist all
Loaded plugins: fastestmirror
repo id                           repo name                           status
C7.0.1406-base/x86_64             CentOS-7.0.1406 - Base              disabled
C7.0.1406-centosplus/x86_64       CentOS-7.0.1406 - CentOSPlus        disabled
C7.0.1406-extras/x86_64           CentOS-7.0.1406 - Extras            disabled
C7.0.1406-fasttrack/x86_64        CentOS-7.0.1406 - CentOSPlus        disabled
C7.0.1406-updates/x86_64          CentOS-7.0.1406 - Updates           disabled
base/7/x86_64                     CentOS-7 - Base                     enabled: 0
base-debuginfo/x86_64             CentOS-7 - Debuginfo                disabled
base-source/7                     CentOS-7 - Base Sources             disabled
centosplus/7/x86_64               CentOS-7 - Plus                     disabled
centosplus-source/7               CentOS-7 - Plus Sources             disabled
cr/7/x86_64                       CentOS-7 - cr                       disabled
extras/7/x86_64                   CentOS-7 - Extras                   enabled: 0
extras-source/7                   CentOS-7 - Extras Sources           disabled
fasttrack/7/x86_64                CentOS-7 - fasttrack                disabled
updates/7/x86_64                  CentOS-7 - Updates                  enabled: 0
updates-source/7                  CentOS-7 - Updates Sources          disabled
repolist: 0
[root@localhost ~]#

The content of the file /etc/yum.repos.d/CentOS-Base.repo

[root@localhost ~]# cat /etc/yum.repos.d/CentOS-Base.repo
# CentOS-Base.repo
#
# The mirror system uses the connecting IP address of the client and the
# update status of each mirror to pick mirrors that are updated to and
# geographically close to the client.  You should use this for CentOS updates
# unless you are manually picking other mirrors.
#
# If the mirrorlist= does not work for you, as a fall back you can try the
# remarked out baseurl= line instead.
#
#

[base]
name=CentOS-$releasever - Base
mirrorlist=http://mirrorlist.centos.org/?release=$releasever&arch=$basearch&repo=os&infra=$infra
#baseurl=http://mirror.centos.org/centos/$releasever/os/$basearch/
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-7

#released updates
[updates]
name=CentOS-$releasever - Updates
mirrorlist=http://mirrorlist.centos.org/?release=$releasever&arch=$basearch&repo=updates&infra=$infra
#baseurl=http://mirror.centos.org/centos/$releasever/updates/$basearch/
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-7

#additional packages that may be useful
[extras]
name=CentOS-$releasever - Extras
mirrorlist=http://mirrorlist.centos.org/?release=$releasever&arch=$basearch&repo=extras&infra=$infra
#baseurl=http://mirror.centos.org/centos/$releasever/extras/$basearch/
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-7

#additional packages that extend functionality of existing packages
[centosplus]
name=CentOS-$releasever - Plus
mirrorlist=http://mirrorlist.centos.org/?release=$releasever&arch=$basearch&repo=centosplus&infra=$infra
#baseurl=http://mirror.centos.org/centos/$releasever/centosplus/$basearch/
gpgcheck=1
enabled=0
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-7

[root@localhost ~]#

asked Sep 11, 2015 at 13:27

Check your resolv.conf to see where your name server is pointing. Make sure it’s something legit as mine was pointing to an old DNS server on the network that was wiped out. I updated it with the new IP address et voila!

sudo sed -i 's/https/http/g' /etc/yum.repos.d/epel.repo

answered Jun 24, 2016 at 0:27

I landed here because I had added a bad mirror for a different dependency (passenger, for a Rails app), and solved this problem by just deleting the bad mirror:

rm /etc/yum.repos.d/YOUR-BAD-DEPENDENCY-NAME.repo

e.g.

rm /etc/yum.repos.d/passenger.repo

answered May 30, 2017 at 20:53

I had this problem in a company environment with MITM proxy after adding the EPEL repo with

yum install epel-release

This doesn’t happen before (e.g. on yum update). I checked all answers and none of them fixed my problem.
Figured out that the other repos use http by default, where epel use https:

# grep mirror /etc/yum.repos.d/epel.repo
metalink=https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=$basearch&infra=$infra&content=$contentdir
metalink=https://mirrors.fedoraproject.org/metalink?repo=epel-debug-7&arch=$basearch&infra=$infra&content=$contentdir
metalink=https://mirrors.fedoraproject.org/metalink?repo=epel-source-7&arch=$basearch&infra=$infra&content=$contentdir

So I copied our company root CA in the CentOS trust store and update it:

cp /home/user/my-ca.crt /etc/pki/ca-trust/source/anchors/
update-ca-trust

After adding the cert, updating and installing packages from the EPEL repo works fine!

answered Mar 21, 2020 at 18:47

Red Hat
Guru
1592 points

RS
Community Member
35 points

Pro
456 points

Pro
456 points

I just installed a new Centos 7 on VirtualBox — minimal install. The first thing I did was yum update kernel which worked fine. I rebooted and tried to yum repolist and get this error. Even yum update kernel or any other yum command gets the same result. I’ve done clean all, rebooted, clean all again, etc., etc.

[root@dphdp851 yum.repos.d]# yum repolist
Loaded plugins: fastestmirror
base | 3.6 kB 00:00:00

epel/x86_64/metalink | 5.7 kB 00:00:00
extras | 3.4 kB 00:00:00
updates | 3.4 kB 00:00:00
Loading mirror speeds from cached hostfile
* base: centos.unixheads.org
* epel: ewr.edge.kernel.org
* extras: mirror.oss.ou.edu
* updates: ftpmirror.your.org

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. Disable the repository, 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>

4. 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

file is encrypted or is not a database

Any suggestions?

Thanks. It’s working this morning. This is an interesting problem I hadn’t considered. I have a few questions; please understand that it is just in the interest of understanding and learning what to do.

So I was unable to do anything with yum because one, more, or all mirrors for a repo get corrupted. Does this mean that an upstream repo error can effectively shutdown anything yum related, even on other repos, globally?

What are the standard workarounds?

You answered that this was likely the epel repo. How did you determine that from the error message? I couldn’t figure it out to know which repo to try to disable.

If I did need epel (and I did but I was just doing some home lab stuff — no money was lost, no businesses were shut down and no VMs were harmed) what do experts (I’m not one) do?

This happened abruptly and was fixed fairly quick so is the answer, if you need epel, to just wait? Or maybe have a local copy of the epel repo but keep it behind by a couple of versions?

Thanks for taking the time to help.

CentOS7 at this morning i see:

# yum check-update --verbose
Loading "fastestmirror" plugin
Config time: 0.014
Yum version: 3.4.3
rpmdb time: 0.000
Building updates object
Setting up Package Sacks
base                                                                                                   | 3.6 kB  00:00:00     
epel/x86_64/metalink                                                                                   |  17 kB  00:00:00     
Using older repomd.xml
  Latest: Fri May 11 08:41:21 2018
  Using: Fri May 11 03:14:59 2018
epel                                                                                                   | 4.7 kB  00:00:00     
extras                                                                                                 | 3.4 kB  00:00:00     
influxdb                                                                                               | 2.5 kB  00:00:00     
nginx                                                                                                  | 2.9 kB  00:00:00     
updates                                                                                                | 3.4 kB  00:00:00     
Loading mirror speeds from cached hostfile
 * base: centos.colocall.net
 * epel: epel.besthosting.ua
 * extras: mirror.besthosting.ua
 * updates: centos.colocall.net


 [b]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. [/b]There are a few ways to work "fix" this:

About current version:

# cat /etc/*elease
CentOS Linux release 7.4.1708 (Core) 
NAME="CentOS Linux"
VERSION="7 (Core)"
ID="centos"
ID_LIKE="rhel fedora"
VERSION_ID="7"
PRETTY_NAME="CentOS Linux 7 (Core)"
ANSI_COLOR="0;31"
CPE_NAME="cpe:/o:centos:centos:7"
HOME_URL="https://www.centos.org/"
BUG_REPORT_URL="https://bugs.centos.org/"

CENTOS_MANTISBT_PROJECT="CentOS-7"
CENTOS_MANTISBT_PROJECT_VERSION="7"
REDHAT_SUPPORT_PRODUCT="centos"
REDHAT_SUPPORT_PRODUCT_VERSION="7"

CentOS Linux release 7.4.1708 (Core) 
CentOS Linux release 7.4.1708 (Core) 

Please, help me.

Serg

[edit/avij: merged these two topics]

Some mirrors still have issues.
what worked for me was commenting the «metalink», and un-commenting the «baseurl» in /etc/yum.repos.d/epel.repo

specifically

> date
Fri May 11 10:01:49 EDT 2018

> yum clean all
Loaded plugins: fastestmirror, langpacks
Cleaning repos: base epel extras nux-dextop updates
Cleaning up everything
Maybe you want: rm -rf /var/cache/yum, to also free up space taken by orphaned data from disabled or removed repos
Cleaning up list of fastest mirrors

> yum -y upgrade
Loaded plugins: fastestmirror, langpacks
base                                                                                                              | 3.6 kB  00:00:00     
epel/x86_64/metalink                                                                                              | 7.6 kB  00:00:00     
epel                                                                                                              | 4.7 kB  00:00:00     
extras                                                                                                            | 3.4 kB  00:00:00     
nux-dextop                                                                                                        | 2.9 kB  00:00:00     
updates                                                                                                           | 3.4 kB  00:00:00     
(1/8): base/7/x86_64/group_gz                                                                                     | 166 kB  00:00:00     
(2/8): base/7/x86_64/primary_db                                                                                   | 5.9 MB  00:00:00     
(3/8): epel/x86_64/group_gz                                                                                       |  84 kB  00:00:00     
(4/8): epel/x86_64/updateinfo                                                                                     | 921 kB  00:00:00     
(5/8): extras/7/x86_64/primary_db                                                                                 | 104 kB  00:00:00     
(6/8): epel/x86_64/primary_db                                                                                     | 1.6 MB  00:00:00     
(7/8): nux-dextop/x86_64/primary_db                                                                               | 1.7 MB  00:00:01     
(8/8): updates/7/x86_64/primary_db                                                                                | 1.0 MB  00:00:15     
Determining fastest mirrors
 * base: ftpmirror.your.org
 * epel: mirror.steadfast.net
 * extras: ftpmirror.your.org
 * nux-dextop: li.nux.ro
 * updates: ftpmirror.your.org


 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>
        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

file is encrypted or is not a database

> find /var/cache/yum/x86_64/7/ -iname '*.sqlite' | xargs file
/var/cache/yum/x86_64/7/base/gen/primary_db.sqlite:       SQLite 3.x database
/var/cache/yum/x86_64/7/nux-dextop/gen/primary_db.sqlite: SQLite 3.x database
/var/cache/yum/x86_64/7/updates/gen/primary_db.sqlite:    SQLite 3.x database
/var/cache/yum/x86_64/7/epel/gen/primary_db.sqlite:       data
/var/cache/yum/x86_64/7/extras/gen/primary_db.sqlite:     SQLite 3.x database

> grep epel /var/cache/yum/x86_64/7/timedhosts* 
fedora-epel.mirrors.tds.net 5280347 0 1507522651
epel.mirror.constant.com 0.0208718776703

And on an identical working server that happened to get different ping times;

> grep epel /var/cache/yum/x86_64/7/timedhosts*
fedora-epel.mirror.lstn.net 8886731 0 1514869786
fedora-epel.mirror.lstn.net 0.0246088504791
fedora-epel.mirrors.tds.net 0.0198471546173

It’s true that yum’s output could have been clearer in this case. Perhaps there is already a related bug entry at bugzilla.redhat.com, I haven’t looked. This would need to be fixed in RHEL first.

I happened to be on Freenode channel #epel when someone complained about this issue, but if this had happened to me, I could have enabled one repository at a time (with —disablerepo=* and —enablerepo=somerepo) to find which repo caused the trouble.

skip_if_unavailable=1 for non-critical repos sounds like a good idea.

Many people need only a few packages from EPEL. One option would be to import the EPEL packages you need to some locally controlled repository and use that instead. createrepo is related to this.