CentOS 7 Impossibile trovare un baseurl valido per il repository: base / 7 / x86_64 Quando si aggiorna yum


0

Questo errore mi sta facendo impazzire, ho provato tutto ciò che è stato pubblicato nei forum e niente funziona.

Quando scrivo:

# yum update

Ottengo il seguente errore:

[root @ www yum.repos.d] # yum update Complementos cargados: fastestmirror   Caricamento delle velocità del mirror dal file host memorizzato nella cache Impossibile recuperare   mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was 14: curl # 56 - "Recv failure: connessione ripristinata da remoto   macchina"

Uno dei repository configurati ha avuto esito negativo (Sconosciuto) e yum no   avere abbastanza dati nella cache per continuare. A questo punto l'unica cassaforte   cosa può fare yum è fallire. Ci sono alcuni modi per lavorare "aggiustare" questo:

 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

Impossibile trovare un baseurl valido per il repository: base / 7 / x86_64

È un server di produzione con un proprio IP, quindi non ho provato DHCP e ONBOOT = no (lo ho in si), ecc.

Se scrivo:

# curl -v 'http://mirrorlist.centos.org/?repo=os&arch=x86_64&release=7'

Questo è quello che ottengo:

[root@www yum.repos.d]# curl -v 'http://mirrorlist.centos.org/?repo=os&arch=x86_64&release=7'
* About to connect() to mirrorlist.centos.org port 80 (#0)
*   Trying 2001:1b48:203::4:10...
* Connected to mirrorlist.centos.org (2001:1b48:203::4:10) port 80 (#0)
> GET /?repo=os&arch=x86_64&release=7 HTTP/1.1
> User-Agent: curl/7.29.0
> Host: mirrorlist.centos.org
> Accept: */*
>
* Recv failure: Connection reset by remote machine
* Closing connection 0
curl: (56) Recv failure: Connection reset by remote machine

Contenuto del mio CentOS-Base.repo siamo:

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

E i contenuti di /etc/yum.conf siamo:

[main]
cachedir=/var/cache/yum/$basearch/$releasever
keepcache=0
debuglevel=2
logfile=/var/log/yum.log
exactarch=1
obsoletes=1
gpgcheck=1
plugins=1
installonly_limit=5
bugtracker_url=http://bugs.centos.org/set_project.php?project_id=23&ref=http://bugs.centos.org/bug_report_page.php?category=yum
distroverpkg=centos-release


#  This is the default, if you make this bigger yum won't see if the metadata
# is newer on the remote and so you'll "gain" the bandwidth of not having to
# download the new metadata and "pay" for it by yum not having correct
# information.
#  It is esp. important, to have correct metadata, for distributions like
# Fedora which don't keep old packages around. If you don't like this checking
# interupting your command line usage, it's much better to have something
# manually check the metadata once an hour (yum-updatesd will do this).
# metadata_expire=90m

# PUT YOUR REPOS HERE OR IN separate files named file.repo
# in /etc/yum.repos.d

Come posso fare yum update lavorare di nuovo ???


forse proverai a impostare un server di repository specifico, Vedere qui
Zina

Sembra che potrebbe essere una sorta di problema di rete locale. Sono in grado di accedere http://mirrorlist.centos.org/?repo=os&arch=x86_64&release=7 senza problemi Ti imbatti nello stesso problema con qualsiasi altra macchina sulla stessa rete?
larsks

@Pathros Trying 2001:1b48:203::4:10... hai intenzione di connetterti tramite IPv6?
user3788685
Utilizzando il nostro sito, riconosci di aver letto e compreso le nostre Informativa sui cookie e Informativa sulla privacy.
Licensed under cc by-sa 3.0 with attribution required.