PDA

View Full Version : Cannot retrieve repository metadata



sutra
23rd October 2007, 05:07 AM
I was trying to access yum to see whether an mplayer plugin was available but I can't get in.
It asks me to file a bug, but I suspect that there's a simple solution and I am posting it here in the hope that some of you can spot the problem in an instant. Suggestions much appreciated. I'm running 2.6.22.9-91.fc7.


Component: pirut
Summary: TB8f5a3431 yumRepo.py:749:_getRepoXML:RepoError: Cannot retrieve repository metadata (repomd.xml) for repository: fedora. Please verify its path and try again

Traceback (most recent call last):
File "/usr/sbin/pirut", line 441, in <module>
main()
File "/usr/sbin/pirut", line 434, in main
pm = PackageManager(options.config, options.onlyrepo)
File "/usr/sbin/pirut", line 61, in __init__
GraphicalYumBase.__init__(self, False, config)
File "/usr/lib/python2.5/site-packages/pirut/__init__.py", line 124, in __init__
self.reset()
File "/usr/lib/python2.5/site-packages/pirut/__init__.py", line 223, in reset
self.doTsSetup()
File "/usr/lib/python2.5/site-packages/yum/depsolve.py", line 64, in doTsSetup
return self._getTs()
File "/usr/lib/python2.5/site-packages/yum/depsolve.py", line 78, in _getTs
self._tsInfo.setDatabases(self.rpmdb, self.pkgSack)
File "/usr/lib/python2.5/site-packages/yum/__init__.py", line 521, in <lambda>
pkgSack = property(fget=lambda self: self._getSacks(),
File "/usr/lib/python2.5/site-packages/yum/__init__.py", line 381, in _getSacks
self.repos.populateSack(which=repos)
File "/usr/lib/python2.5/site-packages/yum/repos.py", line 239, in populateSack
sack.populate(repo, mdtype, callback, cacheonly)
File "/usr/lib/python2.5/site-packages/yum/yumRepo.py", line 142, in populate
if self._check_db_version(repo, mydbtype):
File "/usr/lib/python2.5/site-packages/yum/yumRepo.py", line 199, in _check_db_version
if repo.repoXML.repoData.has_key(mdtype):
File "/usr/lib/python2.5/site-packages/yum/yumRepo.py", line 753, in <lambda>
repoXML = property(fget=lambda self: self._getRepoXML(),
File "/usr/lib/python2.5/site-packages/yum/yumRepo.py", line 749, in _getRepoXML
raise Errors.RepoError, (msg)
RepoError: Cannot retrieve repository metadata (repomd.xml) for repository: fedora. Please verify its path and try again

Local variables in innermost frame:
msg: Cannot retrieve repository metadata (repomd.xml) for repository: fedora. Please verify its path and try again
self: fedora
e: Cannot find a valid baseurl for repo: fedora
Just how do I verify the path?

marko
23rd October 2007, 05:22 AM
Look in /etc/yum.repos.d/fedora.repo

and confirm that the "baseurl=" entry is commented in
and points to the valid place for the fedora repository.
my "fedora.repo" has the baseurl at:


baseurl=http://download.fedora.redhat.com/pub/fedora/linux/releases/$releasever/Everything/$basearch/os/


yum repositories are really just web pages, so try the url:

(note I've replaced the releasever and basearch variables with their
respective values: "7" for Fedora 7 and i386 for 386 instead of x86-64
which are my values)

http://download.fedora.redhat.com/pub/fedora/linux/releases/7/Everything/i386/os/

Usually when a yum baseurl makes sense, you will land in a web page
containing a directory called "repodata" that has a file called repomd.xml

Note, if baseurl is used, then mirrorlist should not be used
and vis versa.

Mark

sutra
23rd October 2007, 06:02 AM
Thanks marko - yes, that does get me to the same web page when I specify the variables, so that seems to be in order, no?
The file looks like this:

[fedora]
name=Fedora $releasever - $basearch
#baseurl=http://download.fedora.redhat.com/pub/fedora/linux/releases/$releasever/Everything/$basearch/os/
mirrorlist=http://mirrors.fedoraproject.org/mirrorlist?repo=fedora-$releasever&arch=$basearch
enabled=1
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora file:///etc/pki/rpm-gpg/RPM-GPG-KEY

[fedora-debuginfo]...
[fedora-source]...

marko
23rd October 2007, 02:35 PM
You're using the mirrorlist and not the baseurl, as a test, reverse that and make the file like this:


baseurl=http://download.fedora.redhat.com/pub/fedora/linux/releases/$releasever/Everything/$basearch/os/
#mirrorlist=http://mirrors.fedoraproject.org/mirrorlist?repo=fedora-$releasever&arch=$basearch

then retry the yum command.

Mark

Dangermouse
23rd October 2007, 05:10 PM
Hello unless you have already been messing with files, try 'yum clean all' it usually works.

sutra
23rd October 2007, 07:19 PM
Yes, Mark, that's done it. Many thanks.
Am I right in assuming that the same change is required for the [fedora-debuginfo] and [fedora-source] portions of the same file?
All very curious - I've not been fiddling with that file at all...

Dangermouse - since Mark's suggestion has put things right I haven't tried 'yum clean all' but I appreciate your help all the same.

JakeK23
23rd October 2007, 08:16 PM
I have been having this problem too.

I tried Dangermouse's suggestion and now pirut won't even show.

Dangermouse
23rd October 2007, 08:33 PM
JakeK23 my suggestion just cleans the cache, you will need to provide more information about your problem, when you say wont start, do you mean hang etc, and does yum work ? any error messages etc.

Dangermouse
23rd October 2007, 08:37 PM
sutra glad its fixed, but it does seem very strange since you have not fiddled with any files, and am curious as to what caused it.

JakeK23
23rd October 2007, 10:55 PM
Dangermouse - Beforehand, when I ran pirut, I would get the same error as sutra. The program would give me that error then terminate. I did the 'yum clean all' and now when i run pirut, nothing happens. yum still works.

marko
23rd October 2007, 11:26 PM
Yes, Mark, that's done it. Many thanks.
Am I right in assuming that the same change is required for the [fedora-debuginfo] and [fedora-source] portions of the same file?
All very curious - I've not been fiddling with that file at all...

Dangermouse - since Mark's suggestion has put things right I haven't tried 'yum clean all' but I appreciate your help all the same.

sutra
For general use, you really want to use the mirrorlist for each
repository because it's fairer at distributing the load of
people installing software. I was just suggesting trying the
baseurl because sometimes what happens is they update the
base server and then it takes a good while for the mirrors to sync
up. Until things sync up you can get these metadata errors.
So a quick hack is to point at the base server, just make
sure to switch it back. To answer the question about fedora-debuginfo
and fedora-source, most people don't even really use them.
But unless you have a problem with them, leave them on mirrorlist.

Mark

sutra
24th October 2007, 03:47 AM
I see. Thanks again.
Having put yum to use again I have got mplayer to deal with streaming radio and it now takes over jobs that Real Player is supposed to do. That's the fun with Fedora - the very minute you've figured out one thing, the next issue comes up...

Omnicloud
11th December 2007, 03:12 AM
http://linuxdownload.adobe.com/linux/i386/repodata/repomd.xml: [Errno 4] IOError: <urlopen error (104, 'Connection reset by peer')>
Trying other mirror.
Error: Cannot retrieve repository metadata (repomd.xml) for repository: adobe-linux-i386. Please verify its path and try again
[root@localhost Habibi]#


Ok...this is the error I got when trying to use yum? Fix? and what caused it? I read a few users say there adobe is down as well...is this a bug?

Either way, how to i get my yum to work again?

Also, my Compiz is acting all haywire as well...

nyjetshead
11th December 2007, 03:26 AM
Happen to me this evening.
I think something either changed at Adobe or the server is down
I deselected the Adobe repository in add/ remove software (gui version of yum) after receiving the error.
I then used yum from the comand line and all was fine.
My guess is its their server so I hope to just set it back on when its sorted out.

Seve
11th December 2007, 03:31 AM
http://linuxdownload.adobe.com/linux/i386/repodata/repomd.xml: [Errno 4] IOError: <urlopen error (104, 'Connection reset by peer')>
Trying other mirror.
Error: Cannot retrieve repository metadata (repomd.xml) for repository: adobe-linux-i386. Please verify its path and try again
[root@localhost Habibi]#


Ok...this is the error I got when trying to use yum? Fix? and what caused it? I read a few users say there adobe is down as well...is this a bug?

Either way, how to i get my yum to work again?

Also, my Compiz is acting all haywire as well...
Hello:
Please do not cross / double post.
http://forums.fedoraforum.org/showthread.php?t=174537&page=2

See: FedoraForum.org guidelines (http://www.fedoraforum.org/?view=guide)

Also, you should start a new thread for your topic as it differs from that of the Original thread topic.

Seve

Omnicloud
11th December 2007, 04:24 AM
sry dude--didn't realize this was a wide--spread problem...though i wouldn't get a response till like next week or something;)

szandor
13th January 2008, 06:49 AM
Hello unless you have already been messing with files, try 'yum clean all' it usually works.

this will not work if the baseurl is not reachable. marko's post gave the correct solution. basically, can you get to the site via http? as a side note, if you just need to remove the repo. (i had one from a long time ago for a particular app i no longer needed and the domain expired so no dns) you can remove the whatever.repo from /etc/yum.repos.d/ and the directory from /var/cache/yum/whatever. then run yum again. if it's something like the above poster mentioned about the site, such as adobe, being down you can either set enabled=1 to enabled=0 indefinitely in the whatever.repo or use the --disableexcludes=whatever_the_repo is with yum. yum will then skip the repo.

MaxIsBored
31st July 2008, 02:11 AM
I'm having issues with my ati driver.. and i can't remove the bloody thing. Furthermore, I can't update, access any ad-remove software, or anything like that.

Check this out.


[root@localhost X11]# yum remove fglrx
Loaded plugins: refresh-packagekit
Setting up Remove Process
Error: Cannot retrieve repository metadata (repomd.xml) for repository: fusion. Please verify its path and try again
[root@localhost X11]# yum clean all
Loaded plugins: refresh-packagekit
Cleaning up Everything
[root@localhost X11]# yum remove fglrx
Loaded plugins: refresh-packagekit
Setting up Remove Process
livna | 2.1 kB 00:00
primary.sqlite.bz2 | 186 kB 00:01
fedora | 2.4 kB 00:00
primary.sqlite.bz2 | 7.6 MB 02:15
Error: Cannot retrieve repository metadata (repomd.xml) for repository: fusion. Please verify its path and try again
[root@localhost X11]#


edit; i have never messed with any of the config. this is a new fresh install.

MaxIsBored
31st July 2008, 02:20 AM
Furthermore, when i try use the ad/remove software menu, i get 'problem connecting to software source'

I can't re-install livna, either. getting an 'local install failed - installing teh local file failed. < more details - can't install /tmp/livna-release-9-4.rpm when downloading the RPM and opening with package installer.

kvaml
27th May 2009, 12:17 AM
One other possibility is a problem with the fedora-release package. rpm -qa 'fedora-release*'. After an upgrade failure I had more than one fedora-release package. I used rpm --erase to delete the extra release package.

neelravi
31st July 2010, 02:06 PM
I am having the same problem with yum
"Cannot retrieve repository metadata"
Though It was working fine for months and suddenly stopped working. I had uncommented baseurl and commented mirrors. Also I have added rpmfusion and fedora project in my /etc/hosts file.
What could be the problem?

troyengel
31st July 2010, 02:50 PM
Hey everyone, the problem is that the wildcard SSL certificate for *.fedoraproject.org has expired this morning. Run 'strace yum -v upgrade' and you'll see:


getpeername(7, {sa_family=AF_INET, sin_port=htons(443), sin_addr=inet_addr("152.46.7.222")}, [16]) = 0

Put that in your browser, you'll get the SSL warning about expiration (07/31/2010 12:17:52 GMT).

EDIT: I just emailed webmaster@fedoraproject.org to make sure someone up there knew.

EDIT2: found a confirming mailing list post that there is an outage:
http://www.spinics.net/lists/fedora-announce/msg03522.html
https://fedorahosted.org/fedora-infrastructure/ticket/2300