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
UPDATE: well, how interesting is that. That file referenced in the error above, is actually empty. Wasn't before. What r my options here.? Cheers, again.
I think this may have been discussed on the list before. Looks like it's a transitory error message, possibly caused by load?
http://lists.freshrpms.net/pipermail/freshrpms-list/2005-October/013565.html
I'd switch to using a close mirror rather than the base repo anyway.
http://www.mirrorservice.org/sites/apt.sw.be/redhat/el4/en/i386/dag/
Will.
On 03/11/05, Mark Sargent powderkeg@snow.email.ne.jp wrote:
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
UPDATE: well, how interesting is that. That file referenced in the error above, is actually empty. Wasn't before. What r my options here.? Cheers, again. _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Will McDonald wrote:
I think this may have been discussed on the list before. Looks like it's a transitory error message, possibly caused by load?
http://lists.freshrpms.net/pipermail/freshrpms-list/2005-October/013565.html
I'd switch to using a close mirror rather than the base repo anyway.
http://www.mirrorservice.org/sites/apt.sw.be/redhat/el4/en/i386/dag/
Will.
Hi All,
sorry, confused. Does this finally resolve itself.? Why is the file empty.? Do I need to replace with a completely new 1, or does it finally regenerate itself.? Cheers.
Mark Sargent.
On 03/11/05, Mark Sargent powderkeg@snow.email.ne.jp wrote:
Will McDonald wrote:
I think this may have been discussed on the list before. Looks like it's a transitory error message, possibly caused by load?
http://lists.freshrpms.net/pipermail/freshrpms-list/2005-October/013565.html
I'd switch to using a close mirror rather than the base repo anyway.
http://www.mirrorservice.org/sites/apt.sw.be/redhat/el4/en/i386/dag/
Hi All,
sorry, confused. Does this finally resolve itself.? Why is the file empty.? Do I need to replace with a completely new 1, or does it finally regenerate itself.? Cheers.
It has in the past when I've seen it. I don't know if it's a problem with the file in Dag's repository or something local. I've only seen it occur on a friends system and he was using Dags repo directly rather than a mirror. I've never seen it using the mirrors, though we rsync those to a local repo anyway.
Will.
Mark Sargent wrote:
I'd switch to using a close mirror rather than the base repo anyway.
http://www.mirrorservice.org/sites/apt.sw.be/redhat/el4/en/i386/dag/
Will.
Hi All,
sorry, confused. Does this finally resolve itself.? Why is the file empty.? Do I need to replace with a completely new 1, or does it finally regenerate itself.? Cheers.
its a problem on the remote end, not your side of things. Just shift to using a mirror and the problem will go away, the mirror that was recommended ( mirrorservice.org ) works well for me too.
- K
its a problem on the remote end, not your side of things. Just shift to using a mirror and the problem will go away, the mirror that was recommended ( mirrorservice.org ) works well for me too.
- K
Hi All,
yep, updated the yum.conf to reflect the mirror suggested. Cheers.
Mark Sargent.
On Thu, 2005-11-03 at 20:45 +0900, Mark Sargent wrote:
its a problem on the remote end, not your side of things. Just shift to using a mirror and the problem will go away, the mirror that was recommended ( mirrorservice.org ) works well for me too.
- K
Hi All,
yep, updated the yum.conf to reflect the mirror suggested. Cheers.
Mark Sargent.
Just for the record, dag has commented on this before.
The main site that hosts his repo is also an apache project test site ... so from time to time there are issues on that box.
Johnny Hughes wrote:
On Thu, 2005-11-03 at 20:45 +0900, Mark Sargent wrote:
its a problem on the remote end, not your side of things. Just shift to using a mirror and the problem will go away, the mirror that was recommended ( mirrorservice.org ) works well for me too.
- K
Hi All,
yep, updated the yum.conf to reflect the mirror suggested. Cheers.
Mark Sargent.
Just for the record, dag has commented on this before.
The main site that hosts his repo is also an apache project test site ... so from time to time there are issues on that box.
funny thing is it only seems to affect centos4, I don't get those errors with any of my 3 boxes.
On Fri, 2005-11-04 at 01:09 +1300, Tom wrote:
Johnny Hughes wrote:
On Thu, 2005-11-03 at 20:45 +0900, Mark Sargent wrote:
its a problem on the remote end, not your side of things. Just shift to using a mirror and the problem will go away, the mirror that was recommended ( mirrorservice.org ) works well for me too.
- K
Hi All,
yep, updated the yum.conf to reflect the mirror suggested. Cheers.
Mark Sargent.
Just for the record, dag has commented on this before.
The main site that hosts his repo is also an apache project test site ... so from time to time there are issues on that box.
funny thing is it only seems to affect centos4, I don't get those errors with any of my 3 boxes.
In this particular case, that is because yum 2.0.x (the one in CentOS 3) uses individual headers and a .info file ... and yum 2.2.x/2.3.x/2.4.x (the one in CentOS 4 is now 2.4.x) uses .xml files and repomd data (all the headers in one file).
The xml file generation produces a zero size .xml file on that mirror (intermittently)... which only effects products using yum 2.2.x/2.3.x/2.4.x (so for CentOS, it only effects CentOS-4). It would also effect FC 3 and 4 and RHEL 4 with yum.
Mark Sargent wrote on Thu, 03 Nov 2005 18:30:51 +0900:
sorry, confused. Does this finally resolve itself.?
it comes and goes. It can just go away in a few minutes. Here is a list of the mirrors: http://apt.sw.be/
Kai
Hi,
I have added:
[dag] name=Dag RPM Repository for Red Hat Enterprise Linux baseurl=http://www.mirrorservice.org/sites/apt.sw.be/redhat/el $releasever/en/x86_64/dag/ gpgcheck=1 enabled=1
to yum.repos.d/CentOS-Base.repo. Now yum check-update reports ---------------------------------------------- Setting up repositories dag 100% |=========================| 1.1 kB 00:00 update 100% |=========================| 951 B 00:00 base 100% |=========================| 1.1 kB 00:00 addons 100% |=========================| 951 B 00:00 extras 100% |=========================| 1.1 kB 00:00 Reading repository metadata in from local files
createrepo.noarch 0.4.3-1.2.el4.rf dag freetype.x86_64 2.1.9-1.2.2.el4.rf dag freetype-demos.x86_64 2.1.9-1.2.2.el4.rf dag freetype-devel.x86_64 2.1.9-1.2.2.el4.rf dag freetype-utils.x86_64 2.1.9-1.2.2.el4.rf dag gaim.x86_64 1:1.5.0-0.1.2.el4.rf dag iptraf.x86_64 3.0.0-1.2.el4.rf dag mod_dav_svn.x86_64 1.2.1-0.1.2.el4.rf dag nmap.x86_64 2:3.93-0.2.el4.rf dag nmap-frontend.x86_64 2:3.93-0.2.el4.rf dag rsync.x86_64 2.6.6-1.2.el4.rf dag subversion.x86_64 1.2.1-0.1.2.el4.rf dag subversion-devel.x86_64 1.2.1-0.1.2.el4.rf dag subversion-perl.x86_64 1.2.1-0.1.2.el4.rf dag syslinux.x86_64 3.11-1.2.el4.rf dag xmms.x86_64 1:1.2.10-11.1.2.el4.rf dag xmms-devel.x86_64 1:1.2.10-11.1.2.el4.rf dag xmms-skins.x86_64 1:1.2.10-11.1.2.el4.rf dag xrestop.x86_64 0.3-1.2.el4.rf dag --------------------------------------------
I thought that these were all core rpms. Why should I take the new ones from DAG?
Thanks Rob
On Thu, 2005-11-03 at 14:01 +0100, Kai Schaetzl wrote:
Mark Sargent wrote on Thu, 03 Nov 2005 18:30:51 +0900:
sorry, confused. Does this finally resolve itself.?
it comes and goes. It can just go away in a few minutes. Here is a list of the mirrors: http://apt.sw.be/
Kai
On Thu, 2005-11-03 at 14:14 +0000, Rob wrote:
Hi,
I have added:
[dag] name=Dag RPM Repository for Red Hat Enterprise Linux baseurl=http://www.mirrorservice.org/sites/apt.sw.be/redhat/el $releasever/en/x86_64/dag/ gpgcheck=1 enabled=1
to yum.repos.d/CentOS-Base.repo. Now yum check-update reports
Setting up repositories dag 100% |=========================| 1.1 kB 00:00 update 100% |=========================| 951 B 00:00 base 100% |=========================| 1.1 kB 00:00 addons 100% |=========================| 951 B 00:00 extras 100% |=========================| 1.1 kB 00:00 Reading repository metadata in from local files
createrepo.noarch 0.4.3-1.2.el4.rf dag freetype.x86_64 2.1.9-1.2.2.el4.rf dag freetype-demos.x86_64 2.1.9-1.2.2.el4.rf dag freetype-devel.x86_64 2.1.9-1.2.2.el4.rf dag freetype-utils.x86_64 2.1.9-1.2.2.el4.rf dag gaim.x86_64 1:1.5.0-0.1.2.el4.rf dag iptraf.x86_64 3.0.0-1.2.el4.rf dag mod_dav_svn.x86_64 1.2.1-0.1.2.el4.rf dag nmap.x86_64 2:3.93-0.2.el4.rf dag nmap-frontend.x86_64 2:3.93-0.2.el4.rf dag rsync.x86_64 2.6.6-1.2.el4.rf dag subversion.x86_64 1.2.1-0.1.2.el4.rf dag subversion-devel.x86_64 1.2.1-0.1.2.el4.rf dag subversion-perl.x86_64 1.2.1-0.1.2.el4.rf dag syslinux.x86_64 3.11-1.2.el4.rf dag xmms.x86_64 1:1.2.10-11.1.2.el4.rf dag xmms-devel.x86_64 1:1.2.10-11.1.2.el4.rf dag xmms-skins.x86_64 1:1.2.10-11.1.2.el4.rf dag xrestop.x86_64 0.3-1.2.el4.rf dag
I thought that these were all core rpms. Why should I take the new ones from DAG?
Thanks Rob
Dag's repo (or any other one for that matter) will give you the latest packages that are there for any that you have installed.
If you don't want that behavior, there are things that can be done to prevent that.
What I always do is this (on CentOS-4):
In the file that I have named dag.repo (in /etc/yum.repos.d) I include this line on each server:
includepkgs="package1-name package2-name"
...then only those packages can be used from dags repo ... no others will be updated from there.
Also, you can use the "exclude=" option of yum to prevent some packages from being looked at.
Here is a yum docs page: http://wiki.linux.duke.edu/Yum
On Thu, 2005-11-03 at 14:01 +0100, Kai Schaetzl wrote:
Mark Sargent wrote on Thu, 03 Nov 2005 18:30:51 +0900:
sorry, confused. Does this finally resolve itself.?
it comes and goes. It can just go away in a few minutes. Here is a list of the mirrors: http://apt.sw.be/
Kai
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
On Thu, 2005-11-03 at 10:02 -0600, Johnny Hughes wrote:
In the file that I have named dag.repo (in /etc/yum.repos.d) I include this line on each server:
includepkgs="package1-name package2-name"
...then only those packages can be used from dags repo ... no others will be updated from there.
Does this mean that I will not be able to do "yum search ..." on all those interesting DAG packages?
I'll have a look at the docs to see if I can search and install packages from DAGS. I am worried that if I fiddle with my main yum.conf settings then I could get yum doing an auto-update while pointing at DAG.
Thanks for your help :) Rob
-
Johnny Hughes -
Kai Schaetzl -
Karanbir Singh -
Mark Sargent -
Rob -
Tom -
Will McDonald