[Yum] failure: repodata/repomd.xml from updates-released: [Errno 256] No more mirrors to try

Lorin B Pino ljpino at grundyec.net
Thu Mar 9 00:34:36 UTC 2006


antonio montagnani wrote:

>2006/3/8, siddharth seth <sidharth.seth at gmail.com>:
>  
>
>>Hi all
>>
>>I continue getting this error with all the repos (livna, freshrpms, dries,
>>fedora-updates etc.), most of the time.
>>
>>Cannot open/read repomd.xml file for repository: <repo-name>
>>failure: repodata/repomd.xml from <repo-name>: [Errno 256] No more mirrors
>>to try.
>>Error: failure: repodata/repomd.xml from <repo-name>: [Errno 256] No more
>>mirrors to try.
>>
>>I am using FC4 (i386) and yum version 2.4.1
>>
>>I have tried googling on this but couldnt get a solution any where.
>>
>>I am not using any proxy and connect directly to internet and have disabled
>>iptables and SElinux. I use an external router (DLink DSL 502 T), which is
>>not blocking any ports.
>>
>>The base URLs given in the repo files are correct and I can open them up in
>>firefox. All URLs invariably have repodata folder with a repomd.xml file
>>which is accesible and downloadable via firefox. Having said that why doesnt
>>yum open/read this file. Sadly its the same story for all the repos most of
>>the time.  Sometimes I am able to do check-update  but then cannot update
>>... yum  goes into suspension while downloading the headers for selected
>>packages.
>>
>>I have also set up high time out times (90sec instead of 30 sec) and have
>>also set  "keep alive" option in yum.conf to accomodate any slowness in the
>>internet connection. Still no sucess.
>>
>>Help needed urgently.
>>
>>Thanks beforehands.
>>
>>--
>>Siddharth Seth
>>_______________________________________________
>>Yum mailing list
>>Yum at lists.dulug.duke.edu
>>https://lists.dulug.duke.edu/mailman/listinfo/yum
>>
>>
>>
>>    
>>
>Have a look to your nsswitch.conf file.
>I guess that you cannot get same file also by wget...please confirm.
>There is a thread some days ago here and I solved same problem!!! Please report
>
>--
>Antonio Montagnani
>Skype : antoniomontag
>_______________________________________________
>Yum mailing list
>Yum at lists.dulug.duke.edu
>https://lists.dulug.duke.edu/mailman/listinfo/yum
>
>  
>
This sounds like the problem I had.  Have you read the yum and yum.conf 
man files?  There is a time setting that you can specify.  The default 
is 30sec.  If yum can't get the whole file within the 30sec, then it 
times out and gives that error.  I am on dial up, and had to give 300 
sec for mine to work.  On mine, the timeout option had to be manually 
added to yum.conf.  The man files will tell you how.  Good luck.
~Lorin



More information about the Yum mailing list