FedoraThis forum is for the discussion of the Fedora Project.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
i have seen that there are a lot of people having issues with yum saying "[Errno 14] curl#7 - "Couldn't connect"" ... i tried searching for it and found that instead of searching for the location "ftp://os.nchc.org.tw/dists/Fedora/linux/releases/15/Everything/x86_64/os/repodata/37db48e8e696e39f1aec5a3a566b30a4d2d328625a3a1f6f6bfb60e2362fbc42-prestodelta.xml.gz" the yum command is actually searching "ftp://os.nchc.org.tw/dists/Fedora/linux/releases/15/Everything/x86_64/os/repodata/37db48e8e696e39f1aec5a3a566b30a4d2d328625a3a1f6f6bfb60e2362fbc42-prestodelta.xml.gz:" and ain't getting any result as there ain't anything there (note the extra : in the end of the link).
hos should i solve it! any help would be highly appreciated!! as this might solve others problem also!
from your massage it looks like presto is being used
it is a yum plugin that can cause no end of trouble .
when it works it is nice but it fails all the time .
wait a day or two and see if it self resolves
that said
90% of yum problems are related to a bad database file and can be solved this way
# This is the default, if you make this bigger yum won't see if the metadata
# is newer on the remote and so you'll "gain" the bandwidth of not having to
# download the new metadata and "pay" for it by yum not having correct
# information.
# It is esp. important, to have correct metadata, for distributions like
# Fedora which don't keep old packages around. If you don't like this checking
# interupting your command line usage, it's much better to have something
# manually check the metadata once an hour (yum-updatesd will do this).
# metadata_expire=90m
# PUT YOUR REPOS HERE OR IN separate files named file.repo
# in /etc/yum.repos.d
i am not using rhel i am using fedora 15 x86_64 bit edition . can i still contact'em for issues???
once again , thanks !
Apologies that I didnt realize that you are using Fedora. Naa, you cannot contact Redhat to get support :-)
I have seen this issue sometimes happens due to bad gateway configured in your route. Type the following command in the terminal and let use know the output:
Apologies that I didnt realize that you are using Fedora. Naa, you cannot contact Redhat to get support :-)
I have seen this issue sometimes happens due to bad gateway configured in your route. Type the following command in the terminal and let use know the output:
Code:
route
Quote:
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
default 10.1.35.1 0.0.0.0 UG 0 0 0 eth0
10.1.35.0 * 255.255.255.0 U 1 0 0 eth0
192.168.122.0 * 255.255.255.0 U 0 0 0 virbr0
Route command output looks fine. Could you please paste the output of the following command:
Code:
/var/log/yum.log
Yes, you were right that it is looking for repomd.xml with an extra :
Could you please paste the contents of the files which are under:
/etc/yum.repos.d/
It appears to me as the link mentioned in one of the yum configuration file is incorrect.
yes you are right, i don't know how but the solution said above to delete and rebuild the repositories i.e. rpmdb worked now and everything is working fine! thanks a lot for your help, but still i wanted to know that if the problem had been what i said earlier how could i've done it myself without applying the above mentioned sequence of commands and understanding no part of it! i meant how could i've changed my repository metadata to do what i wanted!
then most likely the reason is
1) you are behind a router
2) the system ( but NOT yum ) updated to changes in ip's
3) yum / rpm location database dose not auto update to router changes
hence the yum program can become out of sync with the os
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.