|This forum is proudly powered by Scientific Linux 6||SL website Download SL Help Search Members|
|Welcome Guest ( Log In | Register )||Resend Validation Email|
Posted: May 1 2012, 08:55 PM
Member No.: 1502
Joined: 1-May 12
I have reproduced this on two machines now. These were both brand new installs of SL 6.2 (x64), set up as basic servers. Once the install process had completed (and I set up a non-root user, configured networking) I went to see if there were any updates. The result looked like this:
I did a yum-clean all and tried to update again but I got the same errors. I was able to reproduce this on another machine, again a fresh install. I also ran yum-clean all on an existing SL 6.2 box...and now IT can't update either. I'm stumped. Is something just amiss with the repos?
I started putting one of these boxes together at home and was able to run the initial round of updates. I can't see how the repos would be getting filtered here at work...and even if they were, wouldn't I be getting a different kind of error message? Like a connection error and not a "metadata file does not match checksum" error? I have a few Ubuntu VM's left that have no trouble connecting to their repos.
How would I go about testing to see if the SL repos are being filtered or otherwise blocked? I can browse the various repo directories in a Web browser...and I can ping external IP addresses from the problem boxes. Not sure what to try next.
Posted: May 1 2012, 10:26 PM
Member No.: 224
Joined: 28-May 11
I'd guess it's related to this:
Try again once the scheduled outage is over.