Re: headbeating continues

[email protected]
Newsgroups gmane.linux.rpm.yum
Message-ID <100820072136.18633.470AA2E9000BFF3A000048C92209229927020A04040ED29B9B0A9D9D0E09@comcast.net>
alas, my lab is not the same as production.  in the lab it was a prepending urls and removing that from the client conf resolved the problem.  not so in production.  i did what i did in the lab but results are different.  i have researched the problem and will contiue to try various combos, but i've fairly exhausted the obvious.

thanks.

 -------------- Original message ----------------------
From: seth vidal <[email protected]>
> 
> On Mon, 2007-10-08 at 21:09 +0000, [email protected] wrote:
> > well, in the production environment, which is fairly chaotic, i seem to have a 
> difficulty getting the repomd.xml file read.  what i get back is:
> > 
> > 0001# yum -y -c /etc/yum.repos.d/local-updates.repo check-update
> > Repository local-mods already added, not adding again
> > Setting up repositories
> > Cannot open/read repomd.xml file for repository: local-mods
> > failure: repodata/repomd.xml from local-mods: [Errno 256] No more mirrors to 
> try.
> > 0001# 
> > 
> > i had an apache conf file (a yum-vhost.conf one) but that broke basic http 
> connections and it resulted in a 404 for the request on the repomd.xml file.  
> removing it and going straight to the ip address in the client config yields the 
> above.  the client is very simple config:
> > 
> > [local-mods]
> > name=local-mods
> > baseurl=http://x.y.124.179/var/www/html/yum/rel001
> > enabled=1
> > 
> > the file is on the web server under /var/www/html/yum/rel001/repodata
> > 
> > any thoughts / suggestions / help would be appreciated.  this one has me 
> puzzled.
> > 
> 
> I thought you already solved this before?
> 
> remove /var/www/html/ from the baseurl and see if it starts working.
> 
> -sv
> 
> 
> _______________________________________________
> Yum mailing list
> [email protected]
> https://lists.dulug.duke.edu/mailman/listinfo/yum
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.