LVS
lvs-users
Google
 
Web LinuxVirtualServer.org

Re: Everything installed, but doesn't work

To: <lvs-users@xxxxxxxxxxxxxxxxxxxxxx>, Joseph Mack <mack@xxxxxxxxxxx>
Subject: Re: Everything installed, but doesn't work
From: Mike Warwick <mwarwick@xxxxxxxxx>
Date: Sat, 19 May 2001 17:56:12 -0400
Joe,

I saw a problem in the rc.lvs_dr script for running on the real servers.  I
changed these lines:

DIRECTOR_INSIDE_NETWORK="255.255.255.240"
DIRECTOR_INSIDE_NETMASK="209.116.71.47"

to:

DIRECTOR_INSIDE_NETWORK="209.116.71.32"
DIRECTOR_INSIDE_NETMASK="255.255.255.240"

It still isn't working, but at least the script output on the real servers
is a bit cleaner:

--------------------------------------------------------------
[root@www3]# ./rc.lvs_dr
looking for standard utilities
$ECHO=/bin/echo
$IPCHAINS=/sbin/ipchains
$FPING=/usr/sbin/fping
$PING=/bin/ping -c 1
$IFCONFIG=/sbin/ifconfig
$NETSTAT=/bin/netstat
$ROUTE=/sbin/route
$AWK=/bin/awk
$AWK=/usr/bin/awk
$NTPD=/usr/sbin/ntpd
$IP=/sbin/ip
$IPTABLES=/sbin/iptables
$GREP=/bin/grep
$HOSTNAME_CMD=/bin/hostname
$UNAME_CMD=/bin/uname
$CAT=/bin/cat
$CUT=/usr/bin/cut
$TAIL=/usr/bin/tail
$XARGS=/usr/bin/xargs
$PS=/bin/ps
$KILL=/bin/kill
$WC=/usr/bin/wc
$TRACEROUTE=/usr/sbin/traceroute
$ARP=/sbin/arp
$ROUTE=/sbin/route
$LSMOD=/sbin/lsmod
$RMMOD=/sbin/rmmod
$INSMOD=/sbin/insmod
$TR=/usr/bin/tr
$EXPR=/usr/bin/expr
$CHMOD=/bin/chmod
using /usr/sbin/fping for fping
rc.lvs version 0.8 Apr 2001
(C) 2000-2001 Joseph Mack jmack@xxxxxxxx, distributed under GPL license
This file is part of the LVS project http://www.linuxvirtualserver.org
setting up www3


LVS realserver type vs-dr
installing default gw 209.116.71.33
deleting current default gw 209.116.71.33
setting default gw to 209.116.71.33
showing routing table

Kernel IP routing table
Destination     Gateway         Genmask         Flags   MSS Window  irtt
Iface
192.168.1.3     0.0.0.0         255.255.255.255 UH        0 0          0
eth1
209.116.71.36   0.0.0.0         255.255.255.255 UH        0 0          0 lo
209.116.71.32   209.116.71.33   255.255.255.240 UG        0 0          0
eth0
209.116.71.32   0.0.0.0         255.255.255.240 U         0 0          0
eth0
127.0.0.0       0.0.0.0         255.0.0.0       U         0 0          0 lo
0.0.0.0         209.116.71.33   0.0.0.0         UG        0 0          0
eth0

checking if DEFAULT_GW 209.116.71.33 is reachable - 209.116.71.33 is alive
good
set_realserver_ip_forwarding to OFF (1 on, 0 off).
proc/sys/net/ipv4/ip_forward 0

clearing iptables/ipchain rules
device lo:1 has VIP 209.116.71.36


 
looking for DIIP 209.116.71.37
209.116.71.37 is alive
found, good
not local, good 

looking for VIP on director from realserver

looking for VIP on director from realserver
director is accepting packets on VIP 209.116.71.36 on device eth0:1
No VIP on real-server, VIP will be on director.

pinging VIP 209.116.71.36 from RIP
LVS_TYPE is vs-dr and VIP 209.116.71.36 not in same network as RIP
209.116.71.36 is alive
VIP 209.116.71.36 pingable, good.
LVS_TYPE = vs-dr, VIP device installed

OS verion Linux-2.2.16-22smp being treated as minor version 15
install_realserver_vip: configuring Linux 2.2.15
lo:1 is local, up'ing lo.
ifconfig output 
lo:1      Link encap:Local Loopback
          inet addr:209.116.71.36  Mask:255.255.255.255
          UP LOOPBACK RUNNING  MTU:3924  Metric:1

installing route for VIP 209.116.71.36 on device lo:1
listing routing info for VIP 209.116.71.36
209.116.71.36   0.0.0.0         255.255.255.255 UH        0 0          0 lo
hiding interface lo:1, will not arp

ntpd not running, won't be restarted
--------------------------------------------------------------



on 5/19/01 8:31 AM, Joseph Mack at mack@xxxxxxxxxxx wrote:

> On Fri, 18 May 2001, Mike Warwick wrote:
> 
>> Joseph,
>> 
>> Thanks for your reply.  I made the changes you suggested to lvs_dr.conf,
>> re-ran the configure script, bounced all of the servers, and ran the new
>> rc.lvs_dr scripts on each.  I'm still seeing the same problem of failure to
>> connect to the VIP using a browser.
> 
> A browser is a terrible client for debugging. Use telnet, preferably with
> telnet as the LVS'ed service and look at the errors there.
> 
> The output of the script below looks fine. What was the output when run
> on the real-servers?
> 
> Joe
> --
> Joseph Mack mack@xxxxxxxxxxx



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