I have Fedora Core 3. And I can't update it from shell (command line)
using yum or up2date. If anyone can fix this problem, 15 dollars is
yours. But you have to tell me how you fixed it, so I can use it in
the future.

Here's the error

here's my yum.conf

=========================================
[main]
cachedir=/var/cache/yum
debuglevel=2
logfile=/var/log/yum.log
pkgpolicy=newest
distroverpkg=redhat-release
tolerant=1
exactarch=1
retries=20
obsoletes=1

[core]
name=Fedora Linux $releasever - $basearch - core
baseurl=http://ayo.freshrpms.net/fedora/linux/$releasever/$basearch/core

[updates]
name=Fedora Linux $releasever - $basearch - updates
baseurl=http://ayo.freshrpms.net/fedora/linux/$releasever/$basearch/updates

[freshrpms]
name=Fedora Linux $releasever - $basearch - freshrpms
baseurl=http://ayo.freshrpms.net/fedora/linux/$releasever/$basearch/freshrpms
==========================================

here's what i get when i run yum update & yum list. I also have tried
5 different mirrors, but it's always the same error. I run as root.

[root@localhost yum]# yum update
Setting up Update Process
Setting up Repo: core
http://ayo.freshrpms.net/fedora/lin...ata/repomd.xml: [Errno 4]
IOError: <urlopen error (-3, 'Temporary failure in name resolution')>
Trying other mirror.
Cannot open/read repomd.xml file for repository: core
failure: repodata/repomd.xml from core: [Errno 256] No more mirrors to try.
[root@localhost yum]# yum list
Setting up Repo: core
http://ayo.freshrpms.net/fedora/lin...ata/repomd.xml: [Errno 4]
IOError: <urlopen error (-3, 'Temporary failure in name resolution')>
Trying other mirror.
Cannot open/read repomd.xml file for repository: core
failure: repodata/repomd.xml from core: [Errno 256] No more mirrors to try.

---

Clarification of Question by shivesh-ga on 09 May 2005 13:52 PDT

I think I just found out that my server rather has a problem with
resolving DSN. For example, it shows when I tried to use yum. Try to
use yum to update FC3 or install some RPM (like vsftpd) it wouldnt
work.
 
I also tried traceroute program for example. the server can traceroute
any IP addresses, but it cannot traceroute whatever.com . It's the
same problem with yum (try running "yum -y update")
 
If possible, I would really appreciate it if you could help me fix
this problem. I've been trying to fix it, and got no luck.

when i tried to go to the baseurls listed in the yum.conf file. i got
a page cannot be found page. you may want to try to switching them to
the ftp sites:

under core:
baseurl=ftp://ftp.freshrpms.net/pub/freshrpms/ayo/fedora/linux/$releasever/$basearch/core

under updates:
baseurl=ftp://ftp.freshrpms.net/pub/freshrpms/ayo/fedora/linux/$releasever/$basearch/updates/

under freshrpms:
baseurl=ftp://ftp.freshrpms.net/pub/freshrpms/ayo/fedora/linux/$releasever/$basearch/updates/

and in your case $releasever=3 and $basearch=i386

--jeff

Hello there,

can you try the following ?

1) All you need to do is to look down the fedora mirrors list
([url]http://fedora.redhat.com/download/mirrors.html[/url]), pick out
a mirror you like and use the appropriate urls in yum.conf. For
example, if you were to pick the first mirror in France:

[base]
name=Fedora Core $releasever - $basearch - Base
baseurl=http://ftp.crihan.fr/mirrors/fedora.redhat.com/fedora/linux/core/$releasever/$basearch/os/

[updates-released]
name=Fedora Core $releasever - $basearch - Released Updates
baseurl=http://ftp.crihan.fr/mirrors/fedora.redhat.com/fedora/linux/core/updates//$releasever/$basearch/


2) Or you could use the standard fedora setup which selects a mirror for you:

[base]
name=Fedora Core $releasever - $basearch - Base
#baseurl=http://download.fedora.redhat.com/pub/fedora/linux/core/$releasever/$basearch/os/
mirrorlist=http://fedora.redhat.com/download/mirrors/fedora-core-$releasever

[updates-released]
name=Fedora Core $releasever - $basearch - Released Updates
#baseurl=http://download.fedora.redhat.com/pub/fedora/linux/core/updates/$releasever/$basearch/
mirrorlist=http://fedora.redhat.com/download/mirrors/updates-released-fc$releasever


3) Or you could just try deleting everything in yum.conf below
?obsoletes=1". You should already have properly configured repos files
in /etc/yum.repos.d/ to support normal updates. All the extra
freshrpms stuff in yum.conf is basically garbage that is messing up
the works.

Let me know if this was of any help or your problem still exists.

Best regards

Nils Valentin

Hello there,

Are you still interested in a answer ?


Best regards

NIls Valentin

Hi, the problem has been solved. The problem lies in the fact that my
server cannot resolve DNS names. i.e. it cannot change www.google.com
to IP address.