Timeouts setting up repositories in Yum
 

Hi hope someone can help, I'm having real problems getting Yum to update on my machine (FC6 x86_64). I keep getting 'connection timed out' when its trying to retrieve the mirrorlist. Occasionally it'll work on one or two of the repositories (core and \ or updates)ie. I get the little 100% bar appear, but then it fails on extras (or updates). I've tried adding timeout=300 (with various values) to the conf files, I've tried using yum clean all and yum clean headers, i've upgraded yum manually to the latest version. I can ping the repositories and access the URLs in my browser with no problems. I'm in the UK so I was hoping maybe someone has streamlined their files to work here. If anyone has, if you could post your yum.conf and core, updates, and extras repo files, I'd really appreciate it. I'd also be greatful for any other suggestions. Thanks.

Note: when I say getting yum to update, I mean update anything e.g Yum update, yum install yum, etc.

You could try adding some mirrors to the baseurls of your repo files in /etc/yum.repos.d. I was having similar issues until I specified a set of mirros from France, Germany, the Netherlands and the UK; now it's been months since yum last let me down.

Cheers Jay, I set the base urls to mirrors in the uk and ireland and also hardcoded the paths rather than using variables. I'm now getting my first ever Fedora update :D Thanks very much for you help.

Glad to hear it made a difference. Hardcoding the paths wouldn't make any difference, though. In fact, the variables are quite handy when you decide to do a full system upgrade (Fedora 7 is only a month or two away) - you don't have to change anything in that case. But it isn't as if you are going to see any other disadvantages so you can really do as you like.

Thanks. I am intending to revert back to using the variables for exactly that reason, but I just wanted to make sure there were no 'wildcards' that might have been interfering with the update. Ironically, after all that work getting the updates running, everything downloaded fine and began installing and there was a powercut :rolleyes: When the power came back on and I ran yum update again, I got a bunch of confilct errors. I've done a yum clean all and kicked off the update and it seems to be running ok again. Out of interest, was there any other way I could have done it, ie. is there some kind of resume command to resume the update from the point it was at when the powercut occured? Irritatingly I was also in the middle of cooking dinner and I have an electric oven :D I don't think even yum could have helped me there though ;)