|
The most common causes of this symptom I have seen are:
1. the real servers are not using the NAT IP (the virtual IP associated
with the inside of the director) as the default gateway.
2. the NAT IP is down. do an ifconfig and see if the NAT IP is still
there.
On Thu, 2004-03-18 at 12:39, ntadmin@xxxxxxxxxxxx wrote:
> Jim Nachlin Wrote:
> > When a web browser tries to reach 216.18.133.219, ipvsadm tells
> > me that there are InActConn's on both web01 and web02, but no
> > ActiveConn - this remains 0. The browser's connection will
> > eventually time out.
>
> Also, the issue may be with the web servers as HTTP connections
> go to inactive immediately after the request is made. Make sure the
> webservers are configured to use the LVS-nat system as the gw..etc..
> Good Luck.
>
> -Billy
> _______________________________________________
> LinuxVirtualServer.org mailing list - lvs-users@xxxxxxxxxxxxxxxxxxxxxx
> Send requests to lvs-users-request@xxxxxxxxxxxxxxxxxxxxxx
> or go to http://www.in-addr.de/mailman/listinfo/lvs-users
--
Ryan Leathers <ryan.leathers@xxxxxxxxxxxxxxxxxxx>
Global Knowledge
|
