anybody? I restarted my XS hosts with the fallback kernel and I was able to proceed with the upgrade. Servers are now out of alert state.
This seems like an issue that needs to be addressed in the docs. How does one go about getting the ipset-modules for the updated XenServer kernels? On Tue, Jul 1, 2014 at 10:50 AM, Carlos Reategui <car...@reategui.com> wrote: > So upset is part of the CSP. I tried re-installing it but the kernel > modules are not there for my current kernel version. > > Here are the contents of the CSP: > > mount -o loop xenserver-cloud-supp.iso /mnt/tmp > # ll /mnt/tmp/ > total 1437 > -r--r--r-- 1 root root 31340 Jan 24 2012 arptables-0.0.3-4.i686.rpm > -r--r--r-- 1 root root 3506 Jan 24 2012 csp-pack-6.0.2-53069p.noarch.rpm > -r--r--r-- 1 root root 98961 Jan 24 2012 > ebtables-2.0.9-1.el5.1.xs.i386.rpm > -r-xr-xr-x 1 root root 7163 Jan 24 2012 install.sh > -r--r--r-- 1 root root 46791 Jan 24 2012 ipset-4.5-1.xs32.i686.rpm > *-r--r--r-- 1 root root 47895 Jan 24 2012 > ipset-modules-kdump-2.6.32.12-0.7.1.xs6.0.2.542.170665-4.5-1.xs32.i686.rpm* > *-r--r--r-- 1 root root 48020 Jan 24 2012 > ipset-modules-xen-2.6.32.12-0.7.1.xs6.0.2.542.170665-4.5-1.xs32.i686.rpm* > -r--r--r-- 1 root root 247133 Jan 24 2012 > iptables-1.3.5-5.3.el5_4.1.1.xs32.i386.rpm > -r--r--r-- 1 root root 719799 Jan 24 2012 > iptables-debuginfo-1.3.5-5.3.el5_4.1.1.xs32.i386.rpm > -r--r--r-- 1 root root 49657 Jan 24 2012 > iptables-devel-1.3.5-5.3.el5_4.1.1.xs32.i386.rpm > -r--r--r-- 1 root root 166044 Jan 24 2012 > iptables-ipv6-1.3.5-5.3.el5_4.1.1.xs32.i386.rpm > -r--r--r-- 1 root root 1600 Jan 24 2012 XS-PACKAGES > -r--r--r-- 1 root root 262 Jan 24 2012 XS-REPOSITORY > > How do I go about getting the required kernel modules for: > # uname -a > Linux srvengxen02 2.6.32.12-0.7.1.xs6.0.2.611.170703xen #1 SMP Mon Oct 21 > 11:21:50 EDT 2013 i686 i686 i386 GNU/Linux > > How is this supposed to be handled in general when one applies XenServer > kernel patches? > > thanks, > Carlos > > > > On Tue, Jul 1, 2014 at 10:12 AM, Carlos Reategui <car...@reategui.com> > wrote: > >> Looking around for the ipset kernel module, I found it in an older >> version of the kernel: >> >> # uname -a >> Linux srvengxen02 2.6.32.12-0.7.1.xs6.0.2.611.170703xen #1 SMP Mon Oct 21 >> 11:21:50 EDT 2013 i686 i686 i386 GNU/Linux >> # find /lib/modules/ -name ip_set.ko >> /lib/modules/2.6.32.12-0.7.1.xs6.0.2.542.170665xen/extra/ipset/ip_set.ko >> /lib/modules/2.6.32.12-0.7.1.xs6.0.2.542.170665kdump/extra/ipset/ip_set.ko >> >> So where does ip_set come from? Is that part of the CSP should I >> re-install it? >> >> thanks, >> Carlos >> >> >> >> On Tue, Jul 1, 2014 at 9:25 AM, Carlos Reategui <create...@gmail.com> >> wrote: >> >>> Starting a new thread... >>> >>> Environment: Ubuntu 12.04 + XenServer 6.0.2, Upgrading Cloudstack 4.1.1 >>> ---> 4.4 (deb packages built from source). >>> >>> If I attempt a "force reconnect" from UI it errors out. >>> >>> I found the following on one of the hosts in the SMLog: >>> >>> [760] 2014-07-01 09:18:40.980234 ['/bin/bash', >>> '/opt/cloud/bin/setupxenserver.sh'] >>> [760] 2014-07-01 09:18:41.023377 SUCCESS >>> [785] 2014-07-01 09:18:41.251005 ['ebtables', '-V'] >>> [785] 2014-07-01 09:18:41.268054 SUCCESS >>> [785] 2014-07-01 09:18:41.268250 ['ipset', '-V'] >>> [785] 2014-07-01 09:18:41.311253 FAILED: (rc 1) stdout: 'ipset >>> v4.5, protocol version 4. >>> ', stderr: 'FATAL: Module ip_set not found. >>> ipset v4.5: Couldn't verify kernel module version! >>> ' >>> >>> Any ideas how to fix this? >>> >>> thanks, >>> Carlos >>> >>> >>> >> >
