☰

Problem mit Yum: [Errno -1] Fehler beim Importieren von repomd.xml

tag-icon • tag-icon centos package-management yum
Problem mit Yum: [Errno -1] Fehler beim Importieren von repomd.xml

Wie der Betreff des Beitrags schon andeutet, habe ich einige Probleme mit Yum.

Durch das Deaktivieren des Basis-Repos wird das Problem nur auf das nächste Repo verlagert; es tritt bei allen Repos auf.

Bei Verwendung von curl wird das XML als gültiges XML zurückgegeben.

Was habe ich bisher getan (ohne Ergebnisse):

  1. lecker sauber
  2. Entfernen der Mirror-Liste aus dem CentOS-Base.repo
  3. Überprüfen Sie, ob Curl ein gültiges XML zurückgibt
  4. Überprüfen Sie, ob die Spiegelliste eine gültige Antwort zurückgibt
  5. Fügen Sie in der CentOS-Base.repo-Konfiguration einen Proxy hinzu
  6. der Proxy wurde in der CentOS-Base.repo-Konfiguration entfernt
  7. Yum und Plugins über lokales RPM neu installiert
  8. deaktivierte Plugins

Es sieht so aus, als ob mir die Optionen ausgehen. Ich wäre für Hilfe dankbar.

Fehler

cento7:[~]: sudo yum update
Not loading "fastestmirror" plugin, as it is disabled
Not loading "langpacks" plugin, as it is disabled
Config time: 0.009
Yum version: 3.4.3
rpmdb time: 0.000
Updating Everything
Building updates object
Setting up Package Sacks
base                                                                                                       | 104 kB  00:00:00
http://mirror.centos.org/centos/7/os/x86_64/repodata/repomd.xml: [Errno -1] Error importing repomd.xml for base: Damaged repomd.xml file
Trying other mirror.

 One of the configured repositories failed (CentOS-7 - Base),
 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=base ...

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

     5. Configure the failing repository to be skipped, if it is unavailable.
        Note
that yum will try to contact the repository 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=base.skip_if_unavailable=true

failure: repodata/repomd.xml from base: [Errno 256] No more mirrors to try.
http://mirror.centos.org/centos/7/os/x86_64/repodata/repomd.xml: [Errno -1] Error importing repomd.xml for base: Damaged repomd.xml file

/etc/yum.conf:

[main]
cachedir=/var/cache/yum/$basearch/$releasever
keepcache=0
debuglevel=10
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
#proxy=http://localhost:8888

CentOS-Base.repo:

[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

Antwort1

Offenbar wurde das Problem durch Filterregeln in der Unternehmens-Firewall verursacht.

verwandte Informationen