My first notebook upgrade:
I repaired my old HP nc4010 (bought a new hinge on ebay) and realized this was the perfect way to test out the upgrade to 5.2 before doing it on my production notebook.
First I updated to 'current' 5.1 (by current I mean I have not synced my 5.1 local repo since building my 5.2 repo). I had not used my nc4010 for a while and the kernel was at 2.6.18-53.1.13 (update took it to 1.21). Rebooted and system still working.
I then pointed my CentOS-Base.repo to my 5.2 repo. I did a yum clean all then a yum update yum* rpm and below is what happened:
======================================================= [root@nc4010 yum.repos.d]# yum clean all Loading "installonlyn" plugin Cleaning up Everything
[root@nc4010 yum.repos.d]# yum update yum* rpm Loading "installonlyn" plugin Setting up Update Process Setting up repositories http://linuxdownload.adobe.com/linux/i386/repodata/repomd.xml: [Errno 4] IOError: <urlopen error (-3, 'Temporary failure in name resolution')> Trying other mirror. Error: Cannot open/read repomd.xml file for repository: adobe-linux-i386 [root@nc4010 yum.repos.d]# /etc/sysconfig/network-scripts/ifup-eth eth0 [root@nc4010 yum.repos.d]# yum update yum* rpm Loading "installonlyn" plugin Setting up Update Process Setting up repositories adobe-linux-i386 100% |=========================| 951 B 00:00 kbs-CentOS-Extras 100% |=========================| 951 B 00:00 base 100% |=========================| 1.3 kB 00:00 updates 100% |=========================| 951 B 00:00 addons 100% |=========================| 951 B 00:00 extras 100% |=========================| 1.1 kB 00:00 Reading repository metadata in from local files primary.xml.gz 100% |=========================| 10 kB 00:00 ################################################## 17/17 primary.xml.gz 100% |=========================| 157 B 00:00 primary.xml.gz 100% |=========================| 821 kB 00:00 ################################################## 2453/2453 primary.xml.gz 100% |=========================| 91 kB 00:00 ################################################## 165/165 primary.xml.gz 100% |=========================| 157 B 00:00 primary.xml.gz 100% |=========================| 74 kB 00:00 ################################################## 244/244 Resolving Dependencies --> Populating transaction set with selected packages. Please wait. ---> Downloading header for yum-metadata-parser to pack into transaction set. media://1213888991.267240%231/CentOS/yum-metadata-parser-1.1.2-2.el5.i386.rpm: [Errno 4] IOError: <urlopen error unknown url type: media> Trying other mirror. Error: failed to retrieve CentOS/yum-metadata-parser-1.1.2-2.el5.i386.rpm from base error was [Errno 4] IOError: <urlopen error unknown url type: media> =======================================================
I rebooted my local repo server. No change.
I downloaded a new copy of yum-metadata-parser-1.1.2-2.el5.i386.rpm from mirror.centos.org/centos/5.2/os/i386/CentOS/. No change. (dated Jun 14, mine was dated Jun 24, the day I built my repo. but file sizes are identical).
What am I missing here?
Robert Moskowitz wrote on Thu, 3 Jul 2008 08:46:12 -0400:
[Errno 4] IOError: <urlopen error unknown url type: media>
Searching the local folder of this list reveals two older postings from you about this (one from December, one a few days ago). It seems to indicate that your repo is not completely in sync. Either a new sync or clean all got you going last time ;-)
Kai
Kai Schaetzl wrote:
Robert Moskowitz wrote on Thu, 3 Jul 2008 08:46:12 -0400:
[Errno 4] IOError: <urlopen error unknown url type: media>
Searching the local folder of this list reveals two older postings from you about this (one from December, one a few days ago). It seems to indicate that your repo is not completely in sync. Either a new sync or clean all got you going last time ;-)
The other times a
yum clean all
did the job. Problems with old metadata, it would seem.
This time I did the clean first and still got the error.
I ran a rsync and did not get any updates to base.
Robert Moskowitz wrote:
Kai Schaetzl wrote:
Robert Moskowitz wrote on Thu, 3 Jul 2008 08:46:12 -0400:
[Errno 4] IOError: <urlopen error unknown url type: media>
Searching the local folder of this list reveals two older postings from you about this (one from December, one a few days ago). It seems to indicate that your repo is not completely in sync. Either a new sync or clean all got you going last time ;-)
The other times a
yum clean all
did the job. Problems with old metadata, it would seem.
This time I did the clean first and still got the error.
I ran a rsync and did not get any updates to base.
I should also mention that right now, I have a fresh install foranother system running off this repo.
Robert Moskowitz wrote:
Robert Moskowitz wrote:
Kai Schaetzl wrote:
Robert Moskowitz wrote on Thu, 3 Jul 2008 08:46:12 -0400:
[Errno 4] IOError: <urlopen error unknown url type: media>
Searching the local folder of this list reveals two older postings from you about this (one from December, one a few days ago). It seems to indicate that your repo is not completely in sync. Either a new sync or clean all got you going last time ;-)
The other times a
yum clean all
did the job. Problems with old metadata, it would seem.
This time I did the clean first and still got the error.
I ran a rsync and did not get any updates to base.
I should also mention that right now, I have a fresh install foranother system running off this repo.
Just some guesses here . . .
Maybe something's buggered in /etc/yum.repos.d. Try comparing the broken with the working. If the broken still looks right, try making a backup of the broken & copy in the working - there may be some overlooked typo or a character that's invisible to the editor program - like dos file ^M. Could also clear out all non Centos specific repos just to reduce the noise.
On Thu, 2008-07-03 at 11:14 -0400, Toby Bluhm wrote:
<snip>
Just some guesses here . . .
Maybe something's buggered in /etc/yum.repos.d. Try comparing the broken with the working. If the broken still looks right, try making a backup of the broken & copy in the working - there may be some overlooked typo or a character that's invisible to the editor program - like dos file ^M. Could also clear out all non Centos specific repos just to reduce the noise.
Just an FYI, in VI, the "l" command will show "hidden" characters in an unambiguous way. Also, a diff between the two files would catch some overlooked typo.
HTH
William L. Maltby wrote:
On Thu, 2008-07-03 at 11:14 -0400, Toby Bluhm wrote:
<snip>
Just some guesses here . . .
Maybe something's buggered in /etc/yum.repos.d. Try comparing the broken with the working. If the broken still looks right, try making a backup of the broken & copy in the working - there may be some overlooked typo or a character that's invisible to the editor program - like dos file ^M. Could also clear out all non Centos specific repos just to reduce the noise.
Just an FYI, in VI, the "l" command will show "hidden" characters in an unambiguous way. Also, a diff between the two files would catch some overlooked typo.
The problem is deeper than this. I know that my local repo is being hit for the 5.2 files. See that in the log. I just completed doing a yum update on the system I just did an install.
I get the message with different rpms based on what I want to update. yum update yum gets the parser as noted. yum update rpm gets the message for the rpm rpm. yum upgrade gets it on chkconfig.
So there is something that got on this system from one of the 3rd party repos that is causing the problem. Perhaps some MIME lib that I picked up from rpmforge, jpackage, or kbsingh....
Robert Moskowitz wrote on Thu, 3 Jul 2008 10:49:47 -0400:
I should also mention that right now, I have a fresh install foranother system running off this repo.
Then, as Toby says, there might be something wrong with your local yum/repo config. If I recall right you have a few (5.1, 5.2) repos "flying around" and also installed from DVD in the past, so, you may simply be using the wrong Base.repo file or the wrong line in it.
Kai
Kai Schaetzl wrote:
Robert Moskowitz wrote on Thu, 3 Jul 2008 10:49:47 -0400:
I should also mention that right now, I have a fresh install foranother system running off this repo.
Then, as Toby says, there might be something wrong with your local yum/repo config. If I recall right you have a few (5.1, 5.2) repos "flying around" and also installed from DVD in the past, so, you may simply be using the wrong Base.repo file or the wrong line in it.
http access log on my repo server says otherwise.
Yes, I have lots of installs, updates, and upgrades running here. Lots to bring up to snuff. And a hand full of problems.
This system was my workhorse from the start of 5.0 until back in January. So it has rpms from all over I suspect there is something there that is causing this.
Oh, I have run yum -d 5 -e 1 --noplugins
and this does not help or show where things are wrong.
And both repos are synced and correct version, base and updates? I would check their content (including repodata.xml etc.) against the CentOS mirrors for 5. I would expect an error like this when the repodata.xml contains the file, but it isn't on the repo (which could happen if one excludes files from the sync) - that's not the case?
Kai
-
Kai Schaetzl -
Robert Moskowitz -
Toby Bluhm -
William L. Maltby