LVS
lvs-users
Google
 
Web LinuxVirtualServer.org

Re: no response from director for www service with ip-tun

To: Paul Baker <pbaker@xxxxxxxxxxxxxxx>
Subject: Re: no response from director for www service with ip-tun
Cc: Linux Virtual Server <lvs-users@xxxxxxxxxxxxxxxxxxxxxx>
From: Joseph Mack <mack@xxxxxxxxxxx>
Date: Fri, 20 Apr 2001 18:45:08 -0400 (EDT)
On Fri, 20 Apr 2001, Paul Baker wrote:

> I sent a previous version of this message, with attachements that 

please don't send attachments, I have to read them separately.

>   -> 63.216.62.177:www      Tunnel  1      0          1
> 
> You can see that the director did infact receive the response and tried 
> to send one request to each real-server.
> 
> Still the telnet session receives no response and eventually times out 
> with this output:
> 
> $ telnet 63.216.62.170 80
> Trying 63.216.62.170...
> telnet: Unable to connect to remote host: Connection timed out
> 
> pinging 63.216.62.170 does return a response and traceroute is 
> successful as well.

hopefully the machine that responded was the director?

This error is usually a routing error on the real-server.
Make sure the route to the client from the real-server 
doesn't go through the director.

Is there any other device with the VIP on the real-server?

You can try the configure script if you want an alternative
view on the matter. You'll at least see how a working
setup is set up.


> checking the access and error logs for apache shows no connection 
> attempt or errors of any kind. from the same client as above I can 
> successfully connect to http://63.216.62.179/ and it serves me a page, 
> so apache is functioning properly.
> 
> So now I removed the real-server entries with ipvsadm and then ran 
> `ifconfig tunl0 down` on the real-servers.
> 
> Then I re-added the real-servers only this time using direct routing.
> 
> ipvsadm -a -t 63.216.62.170:80 -r 63.216.62.177 -g
> ipvsadm -a -t 63.216.62.170:80 -r 63.216.62.179 -g
> 
> I then executed these commands on the real-servers to set up the 
> real-server protion of VS-DR
> 
> ifconfig lo:0 63.216.62.170 netmask 255.255.255.255 broadcast 
> 63.216.62.170 up
> route add -host 63.216.62.170 dev lo:0
> echo 1 > /proc/sys/net/ipv4/conf/all/hidden
> echo 1 > /proc/sys/net/ipv4/conf/lo/hidden
> 
> After doing that, connections to the director do work and are properly 
> load balanced and serve pages just as expected.

if you haven't changed the routing then the routing in the VS-Tun
case isn't the problem.

Joe
--
Joseph Mack mack@xxxxxxxxxxx



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