Ask Your Question
1

Official mirror returning invalid repomd.xml file

asked 2018-07-09 17:56:17 -0600

cpugliese gravatar image

yum update fails intermittently on some Amazon Linux servers with a fresh cache with the following error requested datatype primary not available. The problem is limited to servers in Australia.

I've narrowed the problem down to certain servers that are given https://mirror.realcompute.io/epel/6/x86_64/ as the first result when they query http://mirrors.fedoraproject.org/mirrorlist?repo=epel-6&arch=$basearch for their mirror list. Looking further, this mirror seems to be returning html when metadata is pulled from https://mirror.realcompute.io/epel/6/x86_64/repodata/repomd.xml to generate /var/cache/yum/x86_64/latest/epel/repomd.xml.

Should this mirror be temporarily disabled from the fedoraproject mirror list? If so, where can I file an issue to have this removed?

Also, is there a way to ignore this mirror in the meantime?

Running yum clean all works as a temporary solution, but I would rather avoid the problem altogether if possible.

edit retag flag offensive close merge delete

1 Answer

Sort by ยป oldest newest most voted
2

answered 2018-07-10 03:58:15 -0600

villykruse gravatar image

You might try to report the issue to Bugzilla at https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora%20EPEL.

In the mean time you could edit the repo file /etc/yum.repos.d/ by commenting out the metalink= line and uncommenting the baseurl= line

edit flag offensive delete link more

Comments

Appreciate the bugzilla link, I'll get that filed there.

In the meantime, I'm blocking outgoing connections to that mirror.

cpugliese gravatar imagecpugliese ( 2018-07-10 12:38:32 -0600 )edit

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Question Tools

Stats

Asked: 2018-07-09 17:56:17 -0600

Seen: 55 times

Last updated: Jul 10