Hello.
I build a local centos repo server, I am able to deploy systems from this centos repo server and I have also updated the etc/yum.repos.d directory The base and update files are changed to the new repo server ip adress.
I am able to do yum clean all and yum update to my new installed client deployed servers from my new local repo server My local deployed servers build from this local reposerver are updated correctly.
If I have a pc running with centos which I updated from centos 5.2 to 5.3 with yum update some weeks ago, and I use the same repo config files from the local deployed repo server . But I get now evrytime an url error. And the error is telling me that the url can't be found.
If I copy the url' into a' browser I get the correct file. It looks like to me' that all centos machines which are upgrade from 5.2' to 5.3 have the same problem. Initial build machines with 5.3 don't have this problem.
Who can help me
Met vriendelijke groet/With kind regards,
Rob Morrien
EDS, an HP company ABN AMRO account IE NL Gondel 1 1186 MJ Amstelveen The Netherlands Tel: +31 887 503052 Mobile: +31 6 51300616 E-mail: rob.morrien@eds.com -->>> ( On Friday i am not in the office ) <<< -----
We deliver on our commitments so you can deliver on yours
Hi
"Morrien, Rob" rob.morrien@eds.com schrieb am 26.08.2009 15:00:31:
If I copy the url' into a' browser I get the correct file. It looks like to me' that all centos machines which are upgrade from 5. 2' to 5.3 have the same problem. Initial build machines with 5.3 don't have this problem. Who can help me
Nice... same problem here. yum upgrade probably sets a new /etc/yum.repos.d/CentOS-Base.repo in place, which most probably will bite you in the ass right now. At least it did here at my site, so go check your yum.repos.d/ ;-)
Frank.
I did' an test , using the yum.repoes files from the new initialled systems which are working, I' copied those to the upgraded systems and there they are not working. Still the url problem
Met vriendelijke groet/With kind regards,
Rob Morrien
EDS, an HP company ABN AMRO account IE NL Gondel 1 1186 MJ Amstelveen The Netherlands Tel: +31 887 503052 Mobile: +31 6 51300616 E-mail: rob.morrien@eds.com -->>> ( On Friday i am not in the office ) <<< -----
We deliver on our commitments so you can deliver on yours
-----Original Message----- From: centos-bounces@centos.org [mailto:centos-bounces@centos.org] On Behalf Of Frank.Brodbeck@klingel.de Sent: Wednesday, August 26, 2009 3:26 PM To: CentOS mailing list Subject: [CentOS] Antwort: Yum update from repo server
Hi
"Morrien, Rob" rob.morrien@eds.com schrieb am 26.08.2009 15:00:31:
If I copy the url' into a' browser I get the correct file. It looks like to me' that all centos machines which are upgrade from 5. 2' to 5.3 have the same problem. Initial build machines with 5.3 don't have this problem. Who can help me
Nice... same problem here. yum upgrade probably sets a new /etc/yum.repos.d/CentOS-Base.repo in place, which most probably will bite you in the ass right now. At least it did here at my site, so go check your yum.repos.d/ ;-)
Frank. _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
"Morrien, Rob" rob.morrien@eds.com schrieb am 26.08.2009 15:30:10:
I did' an test , using the yum.repoes files from the new initialled systems which are working, I' copied those to the upgraded systems and there they are not working. Still the url problem
Can you share the error message from yum with us? Have you looked at the logs of your provisioning software?
Have you tried to do
*) telnet your.reposerver.tld 80
and
*) curl -O your.reposerver.tld/yourpackage.rpm
Frank.
On 08/26/2009 02:25 PM, Frank.Brodbeck@klingel.de wrote:
Nice... same problem here. yum upgrade probably sets a new /etc/yum.repos.d/CentOS-Base.repo in place,
That should not happen, if you have edited or changes the .repo file yourself. A yum update should leave you with a .rpmnew file to handle as you wish. If this is not the case, and you have a situation where the .repo file is being replaced by the yum update - please file an issue report at bugs.centos.org.
The only place where this might be acceptable is if you have a yum plugin like mergeconf that is trying to but failing at doing the right thing. An issue report for that, if that is indeed the case.
Karanbir Singh wrote:
On 08/26/2009 02:25 PM, Frank.Brodbeck@klingel.de wrote:
Nice... same problem here. yum upgrade probably sets a new /etc/yum.repos.d/CentOS-Base.repo in place,
That should not happen, if you have edited or changes the .repo file yourself. A yum update should leave you with a .rpmnew file to handle as you wish. If this is not the case, and you have a situation where the .repo file is being replaced by the yum update - please file an issue report at bugs.centos.org.
The only place where this might be acceptable is if you have a yum plugin like mergeconf that is trying to but failing at doing the right thing. An issue report for that, if that is indeed the case.
One important thing is NOT to change the NAME of the .repo file ... Or, if you do change the name, make sure that you put a CentOS-Base.repo file there so that a new one is not placed in your yum.repos.d directory (as KB said, if there is a modified file, it will not be replaced ... if there is no file with that name, a new one will be put there).
You said you upgraded ... are you sure you have your path is correct now?
Johnny Hughes johnny@centos.org schrieb am 26.08.2009 15:56:08:
Karanbir Singh wrote:
On 08/26/2009 02:25 PM, Frank.Brodbeck@klingel.de wrote:
Nice... same problem here. yum upgrade probably sets a new /etc/yum.repos.d/CentOS-Base.repo in place,
That should not happen, if you have edited or changes the .repo file yourself. A yum update should leave you with a .rpmnew file to handle
as you wish. If this is not the case, and you have a situation where
the
.repo file is being replaced by the yum update - please file an issue report at bugs.centos.org.
The only place where this might be acceptable is if you have a yum plugin like mergeconf that is trying to but failing at doing the right
thing. An issue report for that, if that is indeed the case.
One important thing is NOT to change the NAME of the .repo file ... Or, if you do change the name, make sure that you put a CentOS-Base.repo file there so that a new one is not placed in your yum.repos.d directory (as KB said, if there is a modified file, it will not be replaced ... if there is no file with that name, a new one will be put there).
Boy, now that's kinda embarrasing. While provisioning I really do mv the CentOS-Base.repo out of the way, no wonder a new .repo showed up after my upgrade. Sorry for the noise.
Frank.
From: "Morrien, Rob" rob.morrien@eds.com
If I have a pc running with centos which I updated from centos 5.2 to 5.3 with yum update some weeks ago, and I use the same repo config files from the local deployed repo server . But I get now evrytime an url error. And the error is telling me that the url can't be found. If I copy the url' into a' browser I get the correct file. It looks like to me' that all centos machines which are upgrade from 5.2' to 5.3 have the same problem.
I also have a local repo with a 5.2->5.3 pc and I have no problems... Did you check the repo apache logs for url errors?
I use these:
baseurl=http://192.168.16.23/$releasever/os/$basearch/ baseurl=http://192.168.16.23/$releasever/updates/$basearch/
And my apache DocumentRoot containes:
4/os 4/updates 5/os 5/updates RPM-GPG-KEY-CentOS-4 RPM-GPG-KEY-CentOS-5
JD
-
Frank.Brodbeck＠klingel.de -
John Doe -
Johnny Hughes -
Karanbir Singh -
Morrien, Rob