|
Joe,
If it's helpful, I ran tcpdump on the director and each of the real servers
while attempting to connect to the VIP using telnet. Only the director
reported any packets:
[root@www1]# tcpdump -n -i eth0 port http or telnet or icmp or arp
17:07:13.226377 < 24.162.230.236.64523 > 209.116.71.36.telnet: S
4149809018:4149809018(0) win 32768 <mss 1460,wscale 0,nop> (DF)
(...many more rows that look the same as above...)
I tried listening to both eth0 and lo on the real servers, but nothing
seemed to come in:
[root@www3]# tcpdump -n -i eth0 port http or telnet or icmp or arp
(...nada...)
[root@www3]# tcpdump -n -i lo port http or telnet or icmp or arp
(...still nada...)
--Mike
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
>
>
> _______________________________________________
> 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
>
>
|
