Please someone help me to solve the following problem with yum

asked 2014-09-07 11:50:03 -0600

This post is a wiki. Anyone with karma >750 is welcome to improve it.

I am a student and don't have enough knowledge about yum command. I am facing the following problem please any one tell about the following problem and tell the way to recover from it. Here I just tried to install fedy and the problem arises and it goes on till I disconnected the internet connection.

[root@localhost sdas]# yum install fedy
Loaded plugins: langpacks, refresh-packagekit
Could not get metalink https://mirrors.fedoraproject.org/metalink?repo=fedora-20&arch=x86_64 error was
14: curl#35 - "I/O operation timed out"
updates/20/x86_64/metalink                                                                                                     | 6.7 kB  00:00:00     
updates/20/x86_64/primary_db   FAILED                                          
http://ftp.jaist.ac.jp/pub/Linux/Fedora/updates/20/x86_64/repodata/1b6078ef1d4e7a85d90fd2980b11a37254ace05639eebda04c3028ae5e309c01-primary.sqlite.bz2: [Errno 14] curl#7 - "Failed connect to ftp.jaist.ac.jp:80; Operation now in progress"
Trying other mirror.
updates/20/x86_64/primary_db   FAILED                                          
http://opensource.nchc.org.tw/fedora/linux/updates/20/x86_64/repodata/1b6078ef1d4e7a85d90fd2980b11a37254ace05639eebda04c3028ae5e309c01-primary.sqlite.bz2: [Errno 12] Timeout on http://opensource.nchc.org.tw/fedora/linux/updates/20/x86_64/repodata/1b6078ef1d4e7a85d90fd2980b11a37254ace05639eebda04c3028ae5e309c01-primary.sqlite.bz2: (28, 'Resolving timed out after 30541 milliseconds')
Trying other mirror.
updates/20/x86_64/primary_db   FAILED                                                                               ]   39 B/s | 738 kB  80:41:30 ETA 
http://ftp.riken.jp/Linux/fedora/updates/20/x86_64/repodata/1b6078ef1d4e7a85d90fd2980b11a37254ace05639eebda04c3028ae5e309c01-primary.sqlite.bz2: [Errno 12] Timeout on http://ftp.riken.jp/Linux/fedora/updates/20/x86_64/repodata/1b6078ef1d4e7a85d90fd2980b11a37254ace05639eebda04c3028ae5e309c01-primary.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.
updates/20/x86_64/primary_db   FAILED                                          
http://mirrors.hustunique.com/fedora/updates/20/x86_64/repodata/1b6078ef1d4e7a85d90fd2980b11a37254ace05639eebda04c3028ae5e309c01-primary.sqlite.bz2: [Errno 12] Timeout on http://mirrors.hustunique.com/fedora/updates/20/x86_64/repodata/1b6078ef1d4e7a85d90fd2980b11a37254ace05639eebda04c3028ae5e309c01-primary.sqlite.bz2: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
Trying other mirror.

edit retag flag offensive close merge delete

Comments

yum clean metadata

yum -y update

davidva ( 2014-09-13 21:58:01 -0600 )edit

add a comment

2 Answers

Sort by » oldest newest most voted

answered 2014-09-11 21:55:56 -0600

topaussie
11 ●1

Your yum retrieves may be hitting a slow repo mirror(s), relative to where you are. Try installing the "yum-plugin-fastestmirror" package, it will time the connection each available mirror then sort by the fastest ones.

edit flag offensive delete link

add a comment

answered 2014-09-07 12:21:15 -0600

Jomoos

979 ●6 ●21 ●29 http://www.tecnooc.com/

updated 2014-09-07 12:24:02 -0600

If you take a good look at the output, and you can get some pointers as to what is the problem:

...
curl#35 - "I/O operation timed out"
....
Failed connect to ftp.jaist.ac.jp:80;
....
Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds
....

So, what we can summarize from the above is that the problem is with your internet connection. yum can't connect to the repository, or that your internet connection is too slow so that the connection to remote repository timed out. So, the solution is to get a better internet connection.

edit flag offensive delete link

Comments

Not necessarily. yum could have connected to some slow mirrors even if the connection itself is fast. The usual recovery is to do yum clean expire-cache and try again.

mether ( 2014-09-07 13:39:27 -0600 )edit

nothing improved

SDas ( 2014-09-08 08:37:22 -0600 )edit

How about yum clean all?

cobra ( 2014-09-12 08:17:30 -0600 )edit

add a comment

Please someone help me to solve the following problem with yum

Comments

2 Answers

Comments

Question Tools

Stats

Related questions

Please someone help me to solve the following problem with yum edit

Comments

2 Answers

Comments

Question Tools

Stats

Related questions

Please someone help me to solve the following problem with yum