On 03 May 2008, Kai Schaetzl <maillists AT conactive.com> wrote:
Message: 9
?Date: Sat, 03 May 2008 16:31:50 +0200
Message-ID: VA.000031c9.0166573a@news.conactive.com
Lanny Marcus wrote on Sat, 3 May 2008 07:28:10 -0500: Linux compaq1300.HOMELAN 2.6.18-8.el5
Ok. I just asked because you never mentioned you had actually checked. Just a kernel missing when you update is not proof ;-) I see that you have priority protections in place. Disable all your extra repos, then disable the protections (basically go back to your inital repo setup) and then do a check-update. You are using the mirrorlist and not a specific CentOS mirror, do you?
Kai: This is a follow on to my prior reply to this. I removed the plugins=1 line in /etc/yum.conf and I removed 6 repositories. Then, I did "yum clean all" and got "Cleaning up Everything". Then, I did "yum update" and got, "No packages marked for update/obsoletion". Then, "yum update kernel" and got "No Packages marked for Update/Obsoletion". Then the yum.conf file type is shown as Cisco VPN Settings, so I couldn't open/view it with a text editor.
The last thing I did was to copy these files on my box and replace the files on my wife's box with my files: (a) etc/yum/folder (b) etc/yum.repos.d (c) /etc/yum.conf file
Same problem.
It is as if there is a YUM or RPM database, somewhere, that believes the Kernel has been updated, and it has not been updated?
I find it very hard to believe that the Kernel was in fact updated, but that it is still shown as the original Kernel that was on the CentOS5 Install DVD.
So, this continues to be a an unsolved mystery, but not like the ReiserFS guy. :-)
BTW: I notice that your mail is missing any threading information, so that it doesn't thread at all. I see that other people who use Gmail do get the threading information, so there's probably some option not activated in your Gmail account.
I changed the setting for my subscription to the CentOS Mailing list, from the Daily Digest to Individual messages. This reply is to your message that was in the Digest I received Sunday morning. In the future, I will be replying to individual messages (using Gmail on the web or with Evolution), so, hopefully, the threading will be better, if not perfect. Gmail doesn't use Folders, they use Labels, and I don't have that working on the web yet, but I can move the CentOS messages into the CentOS Label in Evolution and because it's IMAP, they get moved into the CentOS Label on the web too. Something else for me to check out, but that's on the Gmail web site somewhere and will be much easier to cure than this mystery about the kernel update on one box.
All of your ideas about the problem updating the Kernel in my wife's box are very much appreciated! I believe now that when I updated the Kernel (and 2 other packages) on my box and on my daughter's box, it was with PUP and then later, I did a "yum update" to update everything else on those boxes.
If there is some place I can check in a yum database or RPM database on her box, to verify the kernel version that's really installed (probably the original one), please let me know where that is. Thanks much! Lanny
Lanny Marcus wrote:
If there is some place I can check in a yum database or RPM database on her box, to verify the kernel version that's really installed (probably the original one), please let me know where that is. Thanks much! Lanny
rpm -qa kernel*
And: pup is a frontend to yum is a frontend to rpm which holds the package database.
Ralph
On Tue, 2008-05-06 at 16:11 +0200, Ralph Angenendt wrote:
Lanny Marcus wrote:
If there is some place I can check in a yum database or RPM database on her box, to verify the kernel version that's really installed (probably the original one), please let me know where that is. Thanks much! Lanny
rpm -qa kernel*
And: pup is a frontend to yum is a frontend to rpm which holds the package database.
Ralph: Thank you for the above! I need to leave now, but I will check that out, ASAP! Lanny
On Tue, 2008-05-06 at 09:25 -0500, Lanny Marcus wrote:
On Tue, 2008-05-06 at 16:11 +0200, Ralph Angenendt wrote:
Lanny Marcus wrote:
If there is some place I can check in a yum database or RPM database on her box, to verify the kernel version that's really installed (probably the original one), please let me know where that is. Thanks much! Lanny
rpm -qa kernel*
And: pup is a frontend to yum is a frontend to rpm which holds the package database.
Ralph: Thank you for the above! I need to leave now, but I will check that out, ASAP! Lanny
Have you looked at the file /etc/rpm/platform? If it has been changed you will not get any kernel updates.
On 5/6/08, Ralph Angenendt <ra+centos AT br-online.de> wrote:
Lanny Marcus wrote:
If there is some place I can check in a yum database or RPM database on her box, to verify the kernel version that's really installed (probably the original one), please let me know where that is. Thanks much! Lanny
rpm -qa kernel*
[lanny@compaq1300 ~]$ rpm -qa kernel* kernel-headers-2.6.18-53.1.14.el5 kernel-2.6.18-8.el5 kernel-2.6.18-53.1.14.el5 [lanny@compaq1300 ~]$ uname -a Linux compaq1300.HOMELAN 2.6.18-8.el5 #1 SMP Thu Mar 15 19:57:35 EDT 2007 i686 i686 i386 GNU/Linux [lanny@compaq1300 ~]$
Ralph: Thank you for the rpm command and the syntax! That confirms what I have been seeing the past few days, that no updates are available! The kernel-headers for the latest kernel is there, along with the latest kernel. However, it is not shown in the GRUB menu when I boot the box, and, the box boots the old kernel. My knowledge of Linux, obviously, is very limited. How can I correct this, so the box will boot the latest kernel? TIA! Lanny
And: pup is a frontend to yum is a frontend to rpm which holds the package database.
Much better than multiple databases!
on 5-6-2008 2:49 PM lannyma@gmail.com spake the following:
On 5/6/08, Ralph Angenendt <ra+centos AT br-online.de> wrote:
Lanny Marcus wrote:
If there is some place I can check in a yum database or RPM database on her box, to verify the kernel version that's really installed (probably the original one), please let me know where that is. Thanks much! Lanny
rpm -qa kernel*
[lanny@compaq1300 ~]$ rpm -qa kernel* kernel-headers-2.6.18-53.1.14.el5 kernel-2.6.18-8.el5 kernel-2.6.18-53.1.14.el5 [lanny@compaq1300 ~]$ uname -a Linux compaq1300.HOMELAN 2.6.18-8.el5 #1 SMP Thu Mar 15 19:57:35 EDT 2007 i686 i686 i386 GNU/Linux [lanny@compaq1300 ~]$
Ralph: Thank you for the rpm command and the syntax! That confirms what I have been seeing the past few days, that no updates are available! The kernel-headers for the latest kernel is there, along with the latest kernel. However, it is not shown in the GRUB menu when I boot the box, and, the box boots the old kernel. My knowledge of Linux, obviously, is very limited. How can I correct this, so the box will boot the latest kernel? TIA! Lanny
It sounds like the last kernel upgrade didn't finish the %post% scripts. The easiest thing to try would be to rpm -e the new kernel and try a yum upgrade again. Another thing to check... Is there a symlink from /boot/grub/menu.lst to /boot/grub/grub.conf? I have had that on my systems since time began and maybe it is a requirement for things to work right. Just a guess.
On Tue, 2008-05-06 at 15:41 -0700, Scott Silva wrote:
on 5-6-2008 2:49 PM lannyma@gmail.com spake the following:
<snip>
[lanny@compaq1300 ~]$ rpm -qa kernel* kernel-headers-2.6.18-53.1.14.el5 kernel-2.6.18-8.el5 kernel-2.6.18-53.1.14.el5 [lanny@compaq1300 ~]$ uname -a Linux compaq1300.HOMELAN 2.6.18-8.el5 #1 SMP Thu Mar 15 19:57:35 EDT 2007 i686 i686 i386 GNU/Linux [lanny@compaq1300 ~]$
<snip>
It sounds like the last kernel upgrade didn't finish the %post% scripts. The easiest thing to try would be to rpm -e the new kernel and try a yum upgrade again. Another thing to check... Is there a symlink from /boot/grub/menu.lst to /boot/grub/grub.conf? I have had that on my systems since time began and maybe it is a requirement for things to work right. Just a guess.
Scott: Great! If I can locate kernel-headers-2.6.18-53.1.14.el5 and kernel-2.6.18-53.1.14.el5 I can use the rpm -e command to remove them and then yum update again and that should update the kernel in her box. How do I locate them? Practicing on my box (wife is using her box) and rpm -qi shows a lot of information about the files but doesn't show where they are located. TIA, Lanny
Lanny Marcus wrote:
Scott: Great! If I can locate kernel-headers-2.6.18-53.1.14.el5 and kernel-2.6.18-53.1.14.el5 I can use the rpm -e command to remove them and then yum update again and that should update the kernel in her box. How do I locate them?
Why locate them? rpm -e takes the package *name*, not the package itself.
Ralph
On Tue, May 6, 2008 at 2:49 PM, lannyma@gmail.com wrote:
[lanny@compaq1300 ~]$ rpm -qa kernel* kernel-headers-2.6.18-53.1.14.el5 kernel-2.6.18-8.el5 kernel-2.6.18-53.1.14.el5
How can I correct this, so the box will boot the latest kernel? TIA! Lanny
As root, go to the directory where the rpms are located (you can use 'find' for this if you don't alreayd know) and run:
rpm -ivh kernel-headers-2.6.18-53.1.14.el5 kernel-2.6.18-8.el5 kernel-2.6.18-53.1.14.el5
mhr
On Tue, 2008-05-06 at 15:48 -0700, MHR wrote: <snip>
As root, go to the directory where the rpms are located (you can use 'find' for this if you don't alreayd know) and run:
rpm -ivh kernel-headers-2.6.18-53.1.14.el5 kernel-2.6.18-8.el5 kernel-2.6.18-53.1.14.el5
Mark: Syntax for the find command so I can locate those 2 packages? If I can find them, then I think this will be solved quickly. TIA, Lanny
On Tue, May 6, 2008 at 6:32 PM, Lanny Marcus lannyma@gmail.com wrote:
On Tue, 2008-05-06 at 15:48 -0700, MHR wrote:
<snip>
As root, go to the directory where the rpms are located (you can use 'find' for this if you don't alreayd know) and run:
rpm -ivh kernel-headers-2.6.18-53.1.14.el5 kernel-2.6.18-8.el5 kernel-2.6.18-53.1.14.el5
Mark: Syntax for the find command so I can locate those 2 packages? If I can find them, then I think this will be solved quickly. TIA, Lanny
Either 'man find' or 'find --help' would give you faster and more accurate results.
Best wishes!
mhr
MHR wrote:
On Tue, May 6, 2008 at 6:32 PM, Lanny Marcus lannyma@gmail.com wrote:
On Tue, 2008-05-06 at 15:48 -0700, MHR wrote:
<snip>
As root, go to the directory where the rpms are located (you can use 'find' for this if you don't alreayd know) and run:
Mark: Syntax for the find command so I can locate those 2 packages? If I can find them, then I think this will be solved quickly. TIA, Lanny
Either 'man find' or 'find --help' would give you faster and more accurate results.
Erm. "man find" is one of the most hideous manual pages on a linux system (man tar comes close) - so a bit help from your side would have been nice.
a) use locate whereever you can b) find / -type f-name "kernel*.rpm" -- this recursively (from / downwards) finds file which begin with "kernel" and end with "rpm" c) This is not needed anyway, as those packages are ALREADY installed.
Cheers,
Ralph
On Wed, May 7, 2008 at 12:32 AM, Ralph Angenendt ra+centos@br-online.de wrote:
Erm. "man find" is one of the most hideous manual pages on a linux system (man tar comes close) - so a bit help from your side would have been nice.
Beauty is in the eye of the beholder. I have never found this particular man page to be bad enough not to consult when needed, even for the first time (like I did, lo these many eons ago, when it was even harder to read than now) and the effort pays off big time in future uses.
I could have just said RTFM in so many letters, but I /was/ trying to be nice(r).
a) use locate whereever you can
That should work, too, if you know how to use it (I'm not too fond of the man page for this one, either).
b) find / -type f-name "kernel*.rpm" -- this recursively (from / downwards) finds file which begin with "kernel" and end with "rpm"
Actually, the "-type f" is not needed, unless a system has enitities on it that are not files but masquerade as them with names like kernel-headers-2.6.18-53.1.14.el5.i686.rpm.
c) This is not needed anyway, as those packages are ALREADY installed.
The problem Lanny cited was that the packages were installed but the kernel did not appear in /boot, and the suggested solution was to remove them and then reinstall them. Yes, if they are properly installed, you don't need to know where they are. Yes, you do not need to know where they are to remove them (your previous email this subject). But you're going to have a real problem reinstalling them if you don't know where they are. Hence, the "find" suggestion.
'Find' is your friend.
mhr
Mhr wrote on Wed, 7 May 2008 09:53:23 -0700:
Beauty is in the eye of the beholder. I have never found this particular man page to be bad enough not to consult when needed, even for the first time (like I did, lo these many eons ago, when it was even harder to read than now) and the effort pays off big time in future uses.
I agree with Ralph. It's one of the programs with so many options and thus quite intimidating and you easily overlook the one you want. The only program that is worse is rpm.
'Find' is your friend.
I would always use locate for that task, much faster, much easier.
Kai
On Wed, May 7, 2008 at 12:38 PM, Kai Schaetzl maillists@conactive.com wrote:
I would always use locate for that task, much faster, much easier.
Not being familiar with 'locate,' I found its man page rather intimidating at first glance. I'll have to study it a little more carefully, but I should also note that I ran locate to find my kernel rpms and was unsuccessful (whereas, though slow, I did find them with 'find').
All else aside, I can't count the number of times I've had my head handed to me right here on this list for failing to look something up before asking about it. I'll admit that 'find' can be hard to get used to, but if you don't look, you can't tell how much good it can do (or how complex a man page can get :-). 'Man rpm' is ugly, but it's one you just have to get to learn about. (Info is not much better, and it's harder to use.)
Just my $0.02....
mhr
mail.gmail.com> X-Rcpt-To: centos@centos.org
Mhr wrote on Wed, 7 May 2008 14:04:55 -0700:
Not being familiar with 'locate,' I found its man page rather intimidating at first glance. I'll have to study it a little more carefully, but I should also note that I ran locate to find my kernel rpms and was unsuccessful (whereas, though slow, I did find them with 'find').
The locate db is skipping only /tmp I think. It makes use of an index, that's why it's so fast. updatedb is run by cron.daily to update the db. If you get something in in-between it won't be able to find it, of course. In such a case you run it manually. Then "locate whatever". Note, that locate doesn't know any wildcards, you can only search for literals. For searching for your kernel rpms you could either use locate kernel (which will find a lot ...) locate .rpm (which will find all rpm files, which is much less) and then: locate .rpm|grep kernel /var/cache/yum/updates/packages/kernel-headers-2.6.18-53.1.14.el5.i386.rpm /var/cache/yum/updates/packages/kernel-xen-2.6.18-53.1.14.el5.i686.rpm /var/cache/yum/updates/packages/kernel-xen-devel-2.6.18- 53.1.14.el5.i686.rpm
All else aside, I can't count the number of times I've had my head handed to me right here on this list for failing to look something up before asking about it.
One should at least try that, yes. I think your answers were all fine, I just wanted to say that I agree with Ralph about the find options and the usability of that page ;-)
Kai
MHR wrote:
On Tue, May 6, 2008 at 2:49 PM, lannyma@gmail.com wrote:
[lanny@compaq1300 ~]$ rpm -qa kernel* kernel-headers-2.6.18-53.1.14.el5 kernel-2.6.18-8.el5 kernel-2.6.18-53.1.14.el5
How can I correct this, so the box will boot the latest kernel? TIA! Lanny
As root, go to the directory where the rpms are located (you can use 'find' for this if you don't alreayd know) and run:
rpm -ivh kernel-headers-2.6.18-53.1.14.el5 kernel-2.6.18-8.el5 kernel-2.6.18-53.1.14.el5
Ermm. The packages *are* already installed, otherwise rpm -qa wouldn't show them.
Ralph
-
Bob Taylor -
Kai Schaetzl -
Lanny Marcus -
lannyma＠gmail.com
-
MHR -
Ralph Angenendt -
Scott Silva