|
On Tue, 8 Sep 2009, Brent Clark wrote:
I assume you have a two box LVS.
> The problem I have is, if I use siege to test, what I have found is that ..
> if I do a HTTP GET to 41.203.4.5,
the VIP
> and LVS is running on
the master director is running on
> 41.203.4.4, I get replys, but when LVS's round robin changes to
directs connections to
> 41.203.4.7, I get "Error: socket: unable to connect sock.c:215: No route to
> host".
There is no route from the client to the realserver. I
assume there's a route from the client to the VIP on the
director. You need to find why packets can't get from the
VIP on the director to the NIC with the RIP. It's just
routing you need to check.
Joe
--
Joseph Mack NA3T EME(B,D), FM05lw North Carolina
jmack (at) wm7d (dot) net - azimuthal equidistant map
generator at http://www.wm7d.net/azproj.shtml
Homepage http://www.austintek.com/ It's GNU/Linux!
_______________________________________________
Please read the documentation before posting - it's available at:
http://www.linuxvirtualserver.org/
LinuxVirtualServer.org mailing list - lvs-users@xxxxxxxxxxxxxxxxxxxxxx
Send requests to lvs-users-request@xxxxxxxxxxxxxxxxxxxxxx
or go to http://lists.graemef.net/mailman/listinfo/lvs-users
|
