Hello,
Earlier this week I installed a test server with CentOS 5.6 with Virtualization enabled during the installer. Today I installed another server using the same method (they are identical servers). I just did a yum update and I found something curious. Both servers have a different kernel. Server 1 is at 9.1 version and server 2 at 5.1. How can this be? How to I get the latest version on server 2? If I run yum update there are none available.
If I input xm info I get this one server 1:
host : server1 release : 2.6.18-238.9.1.el5xen version : #1 SMP Tue Apr 12 18:53:56 EDT 2011 machine : x86_64 nr_cpus : 4 nr_nodes : 1 sockets_per_node : 1 cores_per_socket : 4 threads_per_core : 1 cpu_mhz : 2400 hw_caps : bfebfbff:20100800:00000000:00000940:0000e3bd:00000000:00000001 total_memory : 4095 free_memory : 383 node_to_cpu : node0:0-3 xen_major : 3 xen_minor : 1 xen_extra : .2-238.9.1.el5 xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64 xen_pagesize : 4096 platform_params : virt_start=0xffff800000000000 xen_changeset : unavailable cc_compiler : gcc version 4.1.2 20080704 (Red Hat 4.1.2-50) cc_compile_by : mockbuild cc_compile_domain : centos.org cc_compile_date : Tue Apr 12 18:01:03 EDT 2011 xend_config_format : 2
And on server 2 it is this:
host : server2 release : 2.6.18-238.5.1.el5xen version : #1 SMP Fri Apr 1 19:35:13 EDT 2011 machine : x86_64 nr_cpus : 4 nr_nodes : 1 sockets_per_node : 1 cores_per_socket : 4 threads_per_core : 1 cpu_mhz : 2400 hw_caps : bfebfbff:20100800:00000000:00000940:0000e3bd:00000000:00000001 total_memory : 4095 free_memory : 383 node_to_cpu : node0:0-3 xen_major : 3 xen_minor : 1 xen_extra : .2-238.5.1.el5 xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64 xen_pagesize : 4096 platform_params : virt_start=0xffff800000000000 xen_changeset : unavailable cc_compiler : gcc version 4.1.2 20080704 (Red Hat 4.1.2-50) cc_compile_by : mockbuild cc_compile_domain : centos.org cc_compile_date : Fri Apr 1 18:30:53 EDT 2011 xend_config_format : 2
It's possible that your #2 server has not rebooted or had problems with the latest kernel or just has the default set to something other than "0" in grub.conf.
What's the output of:
egrep 'default|title' /etc/grub.conf
yum list kernel | grep kernel
./Cal
On Fri, 2011-04-15 at 16:18 +0200, Hans Vos wrote:
Hello,
Earlier this week I installed a test server with CentOS 5.6 with Virtualization enabled during the installer. Today I installed another server using the same method (they are identical servers). I just did a yum update and I found something curious. Both servers have a different kernel. Server 1 is at 9.1 version and server 2 at 5.1. How can this be? How to I get the latest version on server 2? If I run yum update there are none available.
If I input xm info I get this one server 1:
host : server1 release : 2.6.18-238.9.1.el5xen version : #1 SMP Tue Apr 12 18:53:56 EDT 2011 machine : x86_64 nr_cpus : 4 nr_nodes : 1 sockets_per_node : 1 cores_per_socket : 4 threads_per_core : 1 cpu_mhz : 2400 hw_caps : bfebfbff:20100800:00000000:00000940:0000e3bd:00000000:00000001 total_memory : 4095 free_memory : 383 node_to_cpu : node0:0-3 xen_major : 3 xen_minor : 1 xen_extra : .2-238.9.1.el5 xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64 xen_pagesize : 4096 platform_params : virt_start=0xffff800000000000 xen_changeset : unavailable cc_compiler : gcc version 4.1.2 20080704 (Red Hat 4.1.2-50) cc_compile_by : mockbuild cc_compile_domain : centos.org cc_compile_date : Tue Apr 12 18:01:03 EDT 2011 xend_config_format : 2
And on server 2 it is this:
host : server2 release : 2.6.18-238.5.1.el5xen version : #1 SMP Fri Apr 1 19:35:13 EDT 2011 machine : x86_64 nr_cpus : 4 nr_nodes : 1 sockets_per_node : 1 cores_per_socket : 4 threads_per_core : 1 cpu_mhz : 2400 hw_caps : bfebfbff:20100800:00000000:00000940:0000e3bd:00000000:00000001 total_memory : 4095 free_memory : 383 node_to_cpu : node0:0-3 xen_major : 3 xen_minor : 1 xen_extra : .2-238.5.1.el5 xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64 xen_pagesize : 4096 platform_params : virt_start=0xffff800000000000 xen_changeset : unavailable cc_compiler : gcc version 4.1.2 20080704 (Red Hat 4.1.2-50) cc_compile_by : mockbuild cc_compile_domain : centos.org cc_compile_date : Fri Apr 1 18:30:53 EDT 2011 xend_config_format : 2
Hello Cal,
Thank you for your reply.
It's possible that your #2 server has not rebooted or had problems with the latest kernel or just has the default set to something other than "0" in grub.conf.
I did a reboot and checked the grub.conf. Should have mentioned that.
What's the output of:
egrep 'default|title' /etc/grub.conf
# egrep 'default|title' /etc/grub.conf default=0 title CentOS (2.6.18-238.5.1.el5xen) title CentOS (2.6.18-238.el5xen)
yum list kernel | grep kernel
yum list kernel | grep kernel kernel.x86_64 2.6.18-238.5.1.el5 updates
Also if I do "yum info kernel-xen" I get this on server 1:
Name : kernel-xen Arch : x86_64 Version : 2.6.18 Release : 238.9.1.el5 Size : 95 M Repo : installed Summary : The Linux kernel compiled for Xen VM operations URL : http://www.kernel.org/ License : GPLv2 Description: This package includes a version of the Linux kernel which : runs in Xen VM. It works for both priviledged and unpriviledged guests.
And this on server 2:
Name : kernel-xen Arch : x86_64 Version : 2.6.18 Release : 238.5.1.el5 Size : 95 M Repo : installed Summary : The Linux kernel compiled for Xen VM operations URL : http://www.kernel.org/ License : GPLv2 Description: This package includes a version of the Linux kernel which : runs in Xen VM. It works for both priviledged and unpriviledged guests.
On Fri, 2011-04-15 at 16:37 +0200, Hans Vos wrote:
Hello Cal,
Thank you for your reply.
It's possible that your #2 server has not rebooted or had problems with the latest kernel or just has the default set to something other than "0" in grub.conf.
I did a reboot and checked the grub.conf. Should have mentioned that.
What's the output of:
egrep 'default|title' /etc/grub.conf
# egrep 'default|title' /etc/grub.conf default=0 title CentOS (2.6.18-238.5.1.el5xen) title CentOS (2.6.18-238.el5xen)
yum list kernel | grep kernel
yum list kernel | grep kernel kernel.x86_64 2.6.18-238.5.1.el5 updates
Ryan is right. The mirrors need to sync up. That's most likely the cause. Still, it's curious why you have two kernels listed in grub.conf and only one listed from yum. You should also see the 2.6.18-238.el5xen kernel listed.
./Cal
Hello,
Ryan is right. The mirrors need to sync up. That's most likely the cause. Still, it's curious why you have two kernels listed in grub.conf and only one listed from yum. You should also see the 2.6.18-238.el5xen kernel listed.
Well, I copied the /var/cache/yum/timedhosts.txt file from server 1 to server 2. Then run yum update and all kinds of errors came flying at me. So I just SCP'ed the whole /var/cache/yum directory of server 1 to server 2. Ran yum update and there were the updates I was missing including the new kernel-xen. I don't know if this was the *proper* way of fixing it but it did the job :P.
On Fri, Apr 15, 2011 at 11:00 AM, Hans Vos hans@laissezfaire.nl wrote:
Well, I copied the /var/cache/yum/timedhosts.txt file from server 1 to server 2. Then run yum update and all kinds of errors came flying at me. So I just SCP'ed the whole /var/cache/yum directory of server 1 to server 2. Ran yum update and there were the updates I was missing including the new kernel-xen. I don't know if this was the *proper* way of fixing it but it did the job :P.
Not sure the outcome of copying the yum directory. I would have just run yum clean all then yum update.
Ryan
On Fri, 2011-04-15 at 11:07 -0400, Ryan Wagoner wrote:
On Fri, Apr 15, 2011 at 11:00 AM, Hans Vos hans@laissezfaire.nl wrote:
Well, I copied the /var/cache/yum/timedhosts.txt file from server 1 to server 2. Then run yum update and all kinds of errors came flying at me. So I just SCP'ed the whole /var/cache/yum directory of server 1 to server 2. Ran yum update and there were the updates I was missing including the new kernel-xen. I don't know if this was the *proper* way of fixing it but it did the job :P.
Not sure the outcome of copying the yum directory. I would have just run yum clean all then yum update.
Ryan
+1
On Fri, 2011-04-15 at 17:00 +0200, Hans Vos wrote:
Hello,
Ryan is right. The mirrors need to sync up. That's most likely the cause. Still, it's curious why you have two kernels listed in grub.conf and only one listed from yum. You should also see the 2.6.18-238.el5xen kernel listed.
Well, I copied the /var/cache/yum/timedhosts.txt file from server 1 to server 2. Then run yum update and all kinds of errors came flying at me. So I just SCP'ed the whole /var/cache/yum directory of server 1 to server 2. Ran yum update and there were the updates I was missing including the new kernel-xen. I don't know if this was the *proper* way of fixing it but it did the job :P.
You shouldn't need to copy the timedhosts.txt file the "fastestmirrors" yum plugin should recreate it. You might check /var/log/yum.log or /var/log/messages to make some sense of the errors. I don't see any harm in using the cache from the other machine, though.
On Fri, Apr 15, 2011 at 10:18 AM, Hans Vos hans@laissezfaire.nl wrote:
Hello,
Earlier this week I installed a test server with CentOS 5.6 with Virtualization enabled during the installer. Today I installed another server using the same method (they are identical servers). I just did a yum update and I found something curious. Both servers have a different kernel. Server 1 is at 9.1 version and server 2 at 5.1. How can this be? How to I get the latest version on server 2? If I run yum update there are none available.
The 9.1 kernel update was released last night. The mirrors must still be catching up. I was update to update one box to 9.1 and my other boxes still don't see the 9.1 update.
Ryan
Hello,
The 9.1 kernel update was released last night. The mirrors must still be catching up. I was update to update one box to 9.1 and my other boxes still don't see the 9.1 update.
Ah, that might also explain why on server 1 there were 51 updates and on server 2 only 33. Could not figure out why. Was comparing installed packages also.
-
Cal Webster -
Hans Vos -
Ryan Wagoner