LVS
lvs-users
Google
 
Web LinuxVirtualServer.org

[lvs-users] Install script does not work on 2.6 kernel

To: lvs-users@xxxxxxxxxxxxxxxxxxxxxx
Subject: [lvs-users] Install script does not work on 2.6 kernel
From: "David Dyer-Bennet" <dd-b@xxxxxxxx>
Date: Thu, 4 Sep 2008 15:18:27 -0500 (CDT)
configure-0.9.4-lvs.pl fails to find the DIP when it's assigned as a
secondary on one of the ethernet ports:

[root@prcapp02 ~]# ip addr list
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast qlen
1000
    link/ether 00:1e:c9:b3:2a:86 brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.14/24 brd 192.168.1.255 scope global eth0
    inet6 fe80::21e:c9ff:feb3:2a86/64 scope link
       valid_lft forever preferred_lft forever
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast qlen
1000
    link/ether 00:1e:c9:b3:2a:88 brd ff:ff:ff:ff:ff:ff
    inet 172.17.0.1/24 brd 172.17.0.255 scope global eth1
    inet 172.0.17.100/32 scope global eth1
    inet6 fe80::21e:c9ff:feb3:2a88/64 scope link
       valid_lft forever preferred_lft forever
4: sit0: <NOARP> mtu 1480 qdisc noop
    link/sit 0.0.0.0 brd 0.0.0.0

[root@prcapp02 ~]# rc.lvs_nat
[many success reports snipped]
error: not a server, not a director
I'm not a server machine -
this machine doesn't have any of the IPs listed in the SERVICE lines.
I'm not a director - I don't have the DIP 172.17.0.100
bummer - exiting.

It's weird that the configure script expects the DIP to be already
assigned, anyway; that wouldn't normally be assigned when no LVS was
running.  I had to manually assign it just to please configure -- and then
that didn't work either.

The claims about what kernel version are supported are confusing:

[root@prcapp02 ~]# ./configure conf-test-cluster
kernel 2.6.18-92.el5 is being treated as 2.6.17
warning: ./configure has not been tested with kernel version 2.6.17

This seems to me to say that it *does* support 2.6.17 (else why would it
have a concept of treating my kernel as 2.6.17?), but the next line says
it *hasn't* been tested with 2.6.17.

I must say, everything I do to try to set up a simple, understandable
configuration so I can learn enough to go on to do something useful is
rather blowing up in my face.  Bummer.

-- 
David Dyer-Bennet, dd-b@xxxxxxxx; http://dd-b.net/
Snapshots: http://dd-b.net/dd-b/SnapshotAlbum/data/
Photos: http://dd-b.net/photography/gallery/
Dragaera: http://dragaera.info



<Prev in Thread] Current Thread [Next in Thread>