PDA

View Full Version : Yum not finding repos



dougal.s
6th April 2006, 12:04 AM
I installed FC5 on my server today, all went fine and dandy till this evening. Anytime I try and run a yum command (search, update, update ****) I get the following error:


[root@pageclerk ~]# yum -y update
Loading "installonlyn" plugin
Setting up Update Process
Setting up repositories
core [1/3]
Cannot find a valid baseurl for repo: core
Error: Cannot find a valid baseurl for repo: core

I thought I might have to reinstall the fedora-release rpm again, but when I tried I got this:


[root@pageclerk ~]# rpm -ivh fedora-release-5-5.noarch.rpm
warning: fedora-release-5-5.noarch.rpm: Header V3 DSA signature: NOKEY, key ID 4f2a6fd2
error: Failed dependencies:
/bin/sh is needed by fedora-release-5-5.noarch

I have no idea what is wrong, but basically it means my server currently has no GD support till I get it sorted out.

Any help much appreciated.

Dougal.

Jman
6th April 2006, 06:53 AM
Try getting more debug output, by running yum with "-d 5" option or so.

dougal.s
6th April 2006, 12:03 PM
Here's all the extra I get with detailed output:

[root@pageclerk ~]# yum update -y -d 5 -e 5
Loading "installonlyn" plugin
Running "config" handler for "installonlyn" plugin
Yum Version: 2.6.0
COMMAND: yum -d 5 -e 5
Installroot: /
Setting up Update Process
Setting up repositories
core [1/3]
Cannot find a valid baseurl for repo: core
Error: Cannot find a valid baseurl for repo: core

I discovered that the baseurl in /etc/yum.repos.d/fedora-core.repo was commented out. I uncommented it, but now I get a rather different error:


[root@pageclerk yum.repos.d]# yum update -y -d 5 -e 5
Loading "installonlyn" plugin
Running "config" handler for "installonlyn" plugin
Yum Version: 2.6.0
COMMAND: yum -d 5 -e 5
Installroot: /
Setting up Update Process
Setting up repositories
core [1/3]
Baseurl(s) for repo: ['http://download.fedora.redhat.com/pub/fedora/linux/core/Null/i386/os/']
http://download.fedora.redhat.com/pub/fedora/linux/core/Null/i386/os/repodata/repomd.xml: [Errno 14] HTTP Error 404: Date: Thu, 06 Apr 2006 10:56:39 GMT
Server: Apache
Last-Modified: Thu, 06 Apr 2006 10:45:34 GMT
Accept-Ranges: bytes
Content-Length: 4170
Content-Type: text/html; charset=UTF-8
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.
Error: failure: repodata/repomd.xml from core: [Errno 256] No more mirrors to try.

Notice the 'Null' values that I've highlighted? These are supposed to be '5' which is taken from the $releasever variable in the repos files. When I change every instance of '$releasever' in fedora-core.repo to '5' it works for the core repo, but stops on the same error as before for the extras repo.

So how come the $releasever variable is returning null instead of 5? Where is this propagated from?

Again help is appreciated.

Dougal.

[EDIT]
I changed $releasever to 5 in core,extras and updates .repo files, which allows yum to run. I would still like to know the cause of this problem though, is rather annoying.

xorp
6th April 2006, 06:18 PM
There seem to be more than a half-dozen threads regarding this same issue.

What I have found out so far, is that yum does not even generate any network traffic, no wonder it can't find any mirrors.

An earlier thread.

http://forums.fedoraforum.org/forum/showthread.php?t=102394

pfanwick
7th April 2006, 05:01 PM
Had the same problem with yum and also rpm and wget. Replaced the file /etc/nsswitch.conf from a working machine and name servcie and the programs work fine. The file now reads:

# /etc/nsswitch.conf
#
# An example Name Service Switch config file. This file should be
# sorted with the most-used services at the beginning.
#
# The entry '[NOTFOUND=return]' means that the search for an
# entry should stop if the search in the previous entry turned
# up nothing. Note that if the search failed due to some other reason
# (like no NIS server responding) then the search continues with the
# next entry.
#
# Legal entries are:
#
# nisplus or nis+ Use NIS+ (NIS version 3)
# nis or yp Use NIS (NIS version 2), also called YP
# dns Use DNS (Domain Name Service)
# files Use the local files
# db Use the local database (.db) files
# compat Use NIS on compat mode
# hesiod Use Hesiod for user lookups
# [NOTFOUND=return] Stop searching if not found so far
#

# To use db, put the "db" in front of "files" for entries you want to be
# looked up first in the databases
#
# Example:
#passwd: db files nisplus nis
#shadow: db files nisplus nis
#group: db files nisplus nis

passwd: files
shadow: files
group: files

#hosts: db files nisplus nis dns
hosts: files dns

# Example - obey only what nisplus tells us...
#services: nisplus [NOTFOUND=return] files
#networks: nisplus [NOTFOUND=return] files
#protocols: nisplus [NOTFOUND=return] files
#rpc: nisplus [NOTFOUND=return] files
#ethers: nisplus [NOTFOUND=return] files
#netmasks: nisplus [NOTFOUND=return] files

bootparams: nisplus [NOTFOUND=return] files

ethers: files
netmasks: files
networks: files
protocols: files
rpc: files
services: files

netgroup: nisplus

publickey: nisplus

automount: files nisplus
aliases: files nisplus

awillard69
17th May 2006, 07:41 PM
This fixed my yum problem. Thanks for the input guys.