yum problem (//var/cache/yum/base/primary.xml.gz:1: parser error : Document is empty)

[ice99]

I have a little problem here, and i hope that someone will help me to resolve this issue. When i run 'yum update' i got the following error.

[root@host2 /]# yum update
Repository updates-released already added, not adding again
Repository base already added, not adding again
Setting up Update Process
Setting up Repos
base 100% |=========================| 1.1 kB 00:00
updates-released 100% |=========================| 951 B 00:00
Reading repository metadata in from local files
//var/cache/yum/base/primary.xml.gz:1: parser error : Document is empty
^¿½

I try removing it
rm -vf /var/cache/yum/base/primary.*

I have also remove the whole /var/cache/yum/ directory and still nothing. I have also try to reinstall yum, and still the problem is here.

Also try :

# rpm –rebuilddb
# yum clean all
# yum update

And still nothing. The problem i still here.

Can someone tell me what is the problem and how can i fix it?

Thanks in advance.

[bytesniper]

Repository updates-released already added, not adding again
Repository base already added, not adding again

just a stab in the dark here, but this indicates a problem with your repo files. you didn't modify yum with any command line options so you've got something in /etc/yum.repos.d that is trying to add multiples of the same repository. it ignored them so that specifically shouldnt be a problem, but it does mean that they have been changed from their original states.

i would go through all of the .repo files inidvidually and find out where the dupe is coming from, eliminate the un-needed files and make sure the syntax was correct in the ones that are left. short of that i would empty out /etc/yum.repos.d completely and copy back over the default repo files from the fedora CD's, but off habd i am not sure where they would be on the install cd's.

hth,
joseph

[ice99]

thanks for your help but i also try to do that and still nothing.

[bytesniper]

well, if its a problem with the yum binaries themselves (which i doubt) you can try reinstalling yum. since nothing is dependent on yum it's pretty easy.

1) download the yum rpm from here.

2) execute: rpm -e `rpm -qa | grep yum` which will remove yum.

3) remove a) /etc/yum.conf b) /etc/yum.repos.d/* c) /var/cache/yum. i dont know how much of that uninstalling yum will remove, but i would make sure they are gone nontheless.

4) cd into the dir you saved the downloaded yum rpm into and type rpm -ivh yum-2.4.1-1.fc4.noarch.rpm

try to yum update and see what happens.

[ice99]

Thank you for your reply. About 20 minutes ago, I found the problem. We
had upgraded libxml2 from 2.6.16 to 2.6.22 some time back for our compile of
PHP5. This seem to have caused python (and subsequently yum) to be unable
to read from an XML file (which yum's repository is stored in). There
appears to be a known "issue" in yum (based on the code comments I found)
that throw yum into an infinite loop when the repository XML cannot be read.
This is what caused the CPU to get pegged.

I've reinstalled libxml2 version 2.6.16 on one of our servers and yum seems
to be working now. Of course, I can't recompile PHP, but I can deal with
that

Thanks,

Originally Posted by bytesniper

well, if its a problem with the yum binaries themselves (which i doubt) you can try reinstalling yum. since nothing is dependent on yum it's pretty easy.

1) download the yum rpm from here.

2) execute: rpm -e `rpm -qa | grep yum` which will remove yum.

3) remove a) /etc/yum.conf b) /etc/yum.repos.d/* c) /var/cache/yum. i dont know how much of that uninstalling yum will remove, but i would make sure they are gone nontheless.

4) cd into the dir you saved the downloaded yum rpm into and type rpm -ivh yum-2.4.1-1.fc4.noarch.rpm

try to yum update and see what happens.