YUM Parse Error

[Mark Sargent]

Hi All,

please, what is causing this error.? Cheers.

Mark Sargent.


Setting up Install Process
Setting up Repos
addons                    100% |=========================|  951 B    00:00
dag                       100% |=========================|    0 B    00:00
//var/cache/yum/dag/repomd.xml:1: parser error : Document is empty

^
//var/cache/yum/dag/repomd.xml:1: parser error : Start tag expected, '<' 
not found

^
Cannot open/read repomd.xml file for repository: dag
Error importing repomd.xml from dag: Error: could not parse file 
//var/cache/yum/dag/repomd.xml

[Mark Sargent]

Hi All,

well, how interesting is that. That file referenced in the error, is 
actually empty. Wasn't before. What r my options here.? Cheers.

Mark Sargent.

[Andy Green]

Mark Sargent wrote:

>  well, how interesting is that. That file referenced in the error, is
>  actually empty. Wasn't before. What r my options here.? Cheers. 
Temporarily disable the dag repo by setting

enabled=0

in the /etc/yum.repos.d/ dag repo file.

-Andy

[Mark Sargent]

> Temporarily disable the dag repo by setting
>
> enabled=0
>
> in the /etc/yum.repos.d/ dag repo file.
>
> -Andy
>
>
>   
>  
Hi All,

that file is non-existent in that dir. OMG, how stupid of me, I forgot, 
this is my CentOS box, not my Fedora box. Ooops, sincere apologies for 
wasting your time. Heading to the appropriate list. Cheers.

Mark Sargent.

[Andy Green]

Mark Sargent wrote:
>  
> > Temporarily disable the dag repo by setting
> >
> > enabled=0
> >
> > in the /etc/yum.repos.d/ dag repo file. 
>  that file is non-existent in that dir. OMG, how stupid of me, I
> forgot,
>  this is my CentOS box, not my Fedora box. Ooops, sincere apologies for
>  wasting your time. Heading to the appropriate list. Cheers. 
The answer will be the same on CentOS I think... if you are not using
that config dir (it's better to use the dir IMHO), examine /etc/yum.conf
and disable the dag repo in there the same way.

-Andy

[Mark Sargent]

> The answer will be the same on CentOS I think... if you are not using
> that config dir (it's better to use the dir IMHO), examine /etc/yum.conf
> and disable the dag repo in there the same way.
>
> -Andy
>   
>  
Hi All,

I now get the following error, sporadically, after commenting out the 
DAG entry in /etc/yum.conf

Setting up Install Process
Setting up Repos
http://mirror.centos.org/centos/4/addons/i386/repodata/repomd.xml: 
[Errno 4] IOError: <urlopen error (113, 'No route to host')>
Trying other mirror.
Cannot open/read repomd.xml file for repository: addons
failure: repodata/repomd.xml from addons: [Errno 256] No more mirrors to 
try.

Cheers.

Mark Sargent.

[Andy Green]

Mark Sargent wrote:

>  I now get the following error, sporadically, after commenting out
> the
>  DAG entry in /etc/yum.conf
>  [Errno 4] IOError: <urlopen error (113, 'No route to host')> 
This seems to reflect the reality:

$ dig mirror.centos.org
...
;; ANSWER SECTION:
mirror.centos.org.      246     IN      A       131.211.85.52
mirror.centos.org.      246     IN      A       205.209.141.148
mirror.centos.org.      246     IN      A       206.51.236.66
mirror.centos.org.      246     IN      A       64.34.175.102
mirror.centos.org.      246     IN      A       64.38.239.200
mirror.centos.org.      246     IN      A       64.92.174.74
mirror.centos.org.      246     IN      A       66.147.238.146
mirror.centos.org.      246     IN      A       72.21.40.10
mirror.centos.org.      246     IN      A       83.149.120.9
mirror.centos.org.      246     IN      A       131.211.85.22
mirror.centos.org.      246     IN      A       131.211.85.43

$ telnet 64.34.175.102
Trying 64.34.175.102...
telnet: connect to address 64.34.175.102: No route to host

$ telnet 205.209.141.148
Trying 205.209.141.148...
telnet: connect to address 205.209.141.148: No route to host

>  Cannot open/read repomd.xml file for repository: addons
>  failure: repodata/repomd.xml from addons: [Errno 256] No more mirrors to 
This is a separate error.

-Andy

[Jeroen Lankheet]

>  Hi All,
>
>  please, what is causing this error.? Cheers.
>
>  Mark Sargent.
>
>
>  Setting up Install Process
>  Setting up Repos
>  addons                    100% |=========================|  951 B    00:00
>  dag                       100% |=========================|    0 B    00:00
>  //var/cache/yum/dag/repomd.xml:1: parser error : Document is empty
>
>  ^
>  //var/cache/yum/dag/repomd.xml:1: parser error : Start tag expected, '<'
>  not found
>
>  ^
>  Cannot open/read repomd.xml file for repository: dag
>  Error importing repomd.xml from dag: Error: could not parse file
>  //var/cache/yum/dag/repomd.xml
>
>  --
>  fedora-list mailing list
>  fedora-list(a)redhat.com
>  To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
>  
Hi, I also experience the same problems, not every day though.
Looks like some network problem?
See also
http://lists.freshrpms.net/pipermail/freshrpms-list/2005-October/013576.html
His explanation was not very clear to me, but maybe Dag Wieers can shine a
light on this one.

Regards,
Jeroen.

[Timothy Murphy]

Mark Sargent wrote:

>  please, what is causing this error.? Cheers.
>  
>  Setting up Install Process
>  Setting up Repos
>  addons                    100% |=========================|  951 B    00:00
>  dag                       100% |=========================|    0 B    00:00
>  //var/cache/yum/dag/repomd.xml:1: parser error : Document is empty
>  
>  ^
>  //var/cache/yum/dag/repomd.xml:1: parser error : Start tag expected, '<'
>  not found
>  
>  ^
>  Cannot open/read repomd.xml file for repository: dag
>  Error importing repomd.xml from dag: Error: could not parse file
>  //var/cache/yum/dag/repomd.xml 
I'm no yum expert,
but I've occasionally had the above error message (about an empty document)
and I came to the conclusion that it is slightly misleading..

As far as I can see, yum itself creates this file in /var/cache,
and the reason it is empty is that something went wrong earlier.

In my case, I think I got things working by running "yum clean all",
though I may have tried this, which I read about on the net -
there have been quite a few postings about problems
with the dag repository -
=====================================
The fix that worked for me was the flush the up stream proxies (I am
assuming my ISPs), using wget I ran:

wget --cache=off 
http://apt.sw.be/fedora/4/en/i386/dag/repodata/filelists.xml.gz
wget --cache=off
http://apt.sw.be/fedora/4/en/i386/dag/repodata/primary.xml.gz
wget --cache=off http://apt.sw.be/fedora/4/en/i386/dag/repodata/repomd.xml
=====================================
(The first 2 wget lines have been split -
there should be just 3 wget commands.
Also I'm not sure if I had to change those URLs.)














-- 
Timothy Murphy  
e-mail (<80k only): tim /at/ birdsnest.maths.tcd.ie
tel: [phone]
s-mail: School of Mathematics, Trinity College, Dublin 2, Ireland