cloudstack-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Carlos Reategui <car...@reategui.com>
Subject Re: Host in Alert state after upgrade
Date Tue, 01 Jul 2014 17:12:26 GMT
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 <creategui@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
>
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message