I'm trying to run "yum update" on "CentOS release 3.4 (final)":
But I'm getting an error:
<snip> Package mod_ssl needs httpd = 2.0.46-44.ent.centos.2, this is not available. </snip>
However:
</snip>
[root@dev1 root]# rpm -qa | grep httpd httpd-devel-2.0.46-44.ent.centos.2 httpd-2.0.46-44.ent.centos.2 </snip>
It's installed.
So I try yum update httpd and get the same error message.
Any ideas?
Thanks.
Jeff
On 1/9/06, Jeff Lasman blists@nobaloney.net wrote:
I'm trying to run "yum update" on "CentOS release 3.4 (final)":
This is pretty out of date. 3.6 is out now, and 3.7 is in beta.
But I'm getting an error:
<snip> Package mod_ssl needs httpd = 2.0.46-44.ent.centos.2, this is not available. </snip>
You may have some version mismatch issues, or you may not have a properly configured repo for centos. Add "%_query_all_fmt %%{name}-%%{version}-%%{release}.%%{arch}" to root's .rpmmacros, and run 'yum list mod_ssl' and 'yum list httpd'
It's installed.
So I try yum update httpd and get the same error message.
Any ideas?
What do you have in your repo sections for centos? This is mostly a distribution question, not a specific yum issue. This should probably be on the centos list. Since I'd most likely answer you there in the same manner, all of the above still stands.
-- Jim Perrin System Architect - UIT Ft Gordon & US Army Signal Center
What do you have in your repo sections for centos? This is mostly a distribution question, not a specific yum issue. This should probably be on the centos list. Since I'd most likely answer you there in the same manner, all of the above still stands.
Yeah.. ignore the last section of that.. I need to not read two mailing lists at the same time. Thought this was on the yum list.... I'm an illiterate bastard... sorry.
-- Jim Perrin System Architect - UIT Ft Gordon & US Army Signal Center
On Monday 09 January 2006 07:15 pm, Jim Perrin wrote:
Yeah.. ignore the last section of that.. I need to not read two mailing lists at the same time. Thought this was on the yum list.... I'm an illiterate bastard... sorry.
Jim, thanks very much...
On Monday 09 January 2006 07:14 pm, Jim Perrin wrote:
This is pretty out of date. 3.6 is out now, and 3.7 is in beta.
Yep. Caused by not being able to run that pesky "yum update"...
You may have some version mismatch issues, or you may not have a properly configured repo for centos.
What we had was a mod_ssl installed from RPM (not from yum) by the box-owner, who then hired us to figure out why it didn't work.
Here's what I did, in order, to fix the problem, once I figured out that we had a version mismatch:
<snip> rpm -e mod_ssl yum update cd /etc cp yum.conf yum.conf.orig cp yum.conf.rpmnew yum.conf yum install mod_ssl yum update </snip>
and all is now good.
Add "%_query_all_fmt %%{name}-%%{version}-%%{release}.%%{arch}" to root's .rpmmacros, and run 'yum list mod_ssl' and 'yum list httpd'
I didn't know about the macros. Thanks! I don't have an .rpmmacros file; I presume I can just add it with the contents from above?
What do you have in your repo sections for centos?
We don't have a repo section in our /etc/yum.config file. Should we?
Again thanks!
Jeff
What we had was a mod_ssl installed from RPM (not from yum) by the box-owner, who then hired us to figure out why it didn't work.
Sounds about right. You might also consider hunting for conflicting software installed via source build as well. The two have a tendency to go together...
Here's what I did, in order, to fix the problem, once I figured out that we had a version mismatch:
<snip> rpm -e mod_ssl yum update cd /etc cp yum.conf yum.conf.orig cp yum.conf.rpmnew yum.conf yum install mod_ssl yum update </snip>
and all is now good.
I didn't know about the macros. Thanks! I don't have an .rpmmacros file; I presume I can just add it with the contents from above?
Yep.
What do you have in your repo sections for centos?
We don't have a repo section in our /etc/yum.config file. Should we?
Yeah, you have to, or yum would fail. the repo section can be in /etc/yum.conf, or for newer yums in /etc/yum.repos.d. Basically it's the section with the [repo-id] name=foo baseurl=somepath, etc. Sometimes when people have trouble updating it's because they're either not using the updates repository, they've hardcoded something that doesn't exist anymore, or something is otherwise fouled up. Good work in fixing it.
-- Jim Perrin System Architect - UIT Ft Gordon & US Army Signal Center
On Monday 09 January 2006 08:25 pm, Jim Perrin wrote:
Yeah, you have to, or yum would fail. the repo section can be in /etc/yum.conf, or for newer yums in /etc/yum.repos.d.
But we don't have it <frown>:
Look here:
<snip> [root@dev1 etc]# locate yum | grep repo /usr/share/rhn/up2date_client/repoBackends/yumRepo.py /usr/share/rhn/up2date_client/repoBackends/yumRepo.pyc /usr/share/rhn/up2date_client/repoBackends/yumBaseRepo.py /usr/share/rhn/up2date_client/repoBackends/yumBaseRepo.pyc /var/cache/yum/base/packages/sysreport-1.3.7.2-2.noarch.rpm /var/cache/yum/base/packages/sysreport-1.3.7.2-9.noarch.rpm /var/cache/yum/base/headers/sysreport-0-1.3.7.2-2.noarch.hdr /var/cache/yum/base/headers/sysreport-0-1.3.7.2-9.noarch.hdr /var/cache/yum/update/headers/sysreport-0-1.3.7.2-6.noarch.hdr /var/cache/yum/update/headers/sysreport-0-1.3.7.2-9.noarch.hdr [root@dev1 etc]# grep repo yum.conf </snip>
Any ideas?
Thanks.
Jeff
On Tue, 2006-01-10 at 19:10 -0800, Jeff Lasman wrote:
On Monday 09 January 2006 08:25 pm, Jim Perrin wrote:
Yeah, you have to, or yum would fail. the repo section can be in /etc/yum.conf, or for newer yums in /etc/yum.repos.d.
But we don't have it <frown>:
Look here:
<snip> [root@dev1 etc]# locate yum | grep repo /usr/share/rhn/up2date_client/repoBackends/yumRepo.py /usr/share/rhn/up2date_client/repoBackends/yumRepo.pyc /usr/share/rhn/up2date_client/repoBackends/yumBaseRepo.py /usr/share/rhn/up2date_client/repoBackends/yumBaseRepo.pyc /var/cache/yum/base/packages/sysreport-1.3.7.2-2.noarch.rpm /var/cache/yum/base/packages/sysreport-1.3.7.2-9.noarch.rpm /var/cache/yum/base/headers/sysreport-0-1.3.7.2-2.noarch.hdr /var/cache/yum/base/headers/sysreport-0-1.3.7.2-9.noarch.hdr /var/cache/yum/update/headers/sysreport-0-1.3.7.2-6.noarch.hdr /var/cache/yum/update/headers/sysreport-0-1.3.7.2-9.noarch.hdr [root@dev1 etc]# grep repo yum.conf </snip>
Any ideas?
For centos-3.x, look in /etc/yum.conf
If you don't have /etc/yum.conf, then you don't have a normally installed CentOS-3 or CentOS-4 system.
On 1/10/06, Jeff Lasman blists@nobaloney.net wrote:
On Monday 09 January 2006 08:25 pm, Jim Perrin wrote:
Yeah, you have to, or yum would fail. the repo section can be in /etc/yum.conf, or for newer yums in /etc/yum.repos.d.
But we don't have it <frown>:
Sure you do. You have to or yum wouldn't work. as Johnny says, it's probably in /etc/yum.conf. Seeing as how updating your /etc/yum.conf fixed your problem, I'd say it's in there.
-- Jim Perrin System Architect - UIT Ft Gordon & US Army Signal Center
On Tuesday 10 January 2006 07:51 pm, Jim Perrin wrote:
But we don't have it <frown>:
Sure you do. You have to or yum wouldn't work. as Johnny says, it's probably in /etc/yum.conf. Seeing as how updating your /etc/yum.conf fixed your problem, I'd say it's in there.
But it's not:
<snip> [root@dev1 root]# grep repo /etc/yum.conf [root@dev1 root]# </snip>
I'm turning the servers (two of 'em, web1 & dev1) back over to the client tonight. yum update definitely works.
Weird.
Jeff
Jeff Lasman wrote:
On Tuesday 10 January 2006 07:51 pm, Jim Perrin wrote:
But we don't have it <frown>:
Sure you do. You have to or yum wouldn't work. as Johnny says, it's probably in /etc/yum.conf. Seeing as how updating your /etc/yum.conf fixed your problem, I'd say it's in there.
But it's not:
<snip> [root@dev1 root]# grep repo /etc/yum.conf [root@dev1 root]# </snip>
"repo section" doesn't mean literally the word "repo" is in the file. By default (as you've shown) it isn't.
Jim is referring to the sections in the yum.conf file that set up the repos. For example "[base]", "[update]", etc.
On Wednesday 11 January 2006 02:48 am, William Hooper wrote:
"repo section" doesn't mean literally the word "repo" is in the file. By default (as you've shown) it isn't.
Jim is referring to the sections in the yum.conf file that set up the repos. For example "[base]", "[update]", etc.
Thank you. Sincerely.
I shall bang my head against the wall...
<bang> <bang> <bang>
And apologize profusely to Jim.
Again thanks!
Jeff
On Wed, 2006-01-11 at 16:45 -0500, Jim Perrin wrote:
And apologize profusely to Jim.
I'm glad you got it fixed, and no problem, I'm usually a very patient person.
**** Note. Anyone stating otherwise will be verbally abused and shot on site. :-P
Uh... can you shoot me off-site? I don't think I can get over there. ;-)
-- Jim Perrin System Architect - UIT Ft Gordon & US Army Signal Center _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
-
Jeff Lasman -
Jim Perrin -
Johnny Hughes -
William Hooper -
William L. Maltby