[Linux-cluster] LVS, not so fun today...
isplist at logicore.net
isplist at logicore.net
Thu Nov 9 16:43:19 UTC 2006
Hi and thank you for helping.
I'll post all I can think of. I have IPTables turned off, SElinux disabled so
it's not a firewall issue. I can also post my lvs.cf if that will help.
> Can you post the results of "arping 192.168.1.150"? You might need to
> specify the interface and source IP, see the man page for more info.
Sure, ping form where? All machines on my network see 192.168.1.150 which is
the VIP on the load balancer. I'm back to Piranha today.
192.168.1.150 is my VIP pn the load balancer.
192.168.1.53 is the load balancer.
# ifconfig
eth0 Link encap:Ethernet HWaddr 00:20:94:10:44:A5
inet addr:192.168.1.52 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::220:94ff:fe10:44a5/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:91631 errors:0 dropped:0 overruns:0 frame:0
TX packets:8142 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:6004157 (5.7 MiB) TX bytes:1402617 (1.3 MiB)
eth0:1 Link encap:Ethernet HWaddr 00:20:94:10:44:A5
inet addr:192.168.1.150 Bcast:192.168.1.150 Mask:255.255.255.255
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:8 errors:0 dropped:0 overruns:0 frame:0
TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:560 (560.0 b) TX bytes:560 (560.0 b)
My real servers are at 192.168.1.93, 93 and 94.
When I try a web connection, I can see this in the netstat;
# netstat -a|more
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address Foreign Address
State
tcp 0 0 192.168.1.52:32957 192.168.1.92:http
TIME_WAIT
tcp 0 0 192.168.1.52:32969 192.168.1.92:http
TIME_WAIT
tcp 0 0 192.168.1.52:32960 192.168.1.92:http
TIME_WAIT
tcp 0 0 192.168.1.52:32963 192.168.1.92:http
TIME_WAIT
tcp 0 0 192.168.1.52:32966 192.168.1.92:http
TIME_WAIT
tcp 0 0 192.168.1.52:32956 192.168.1.93:http
TIME_WAIT
tcp 0 0 192.168.1.52:32959 192.168.1.93:http
TIME_WAIT
tcp 0 0 192.168.1.52:32968 192.168.1.93:http
TIME_WAIT
tcp 0 0 192.168.1.52:32962 192.168.1.93:http
TIME_WAIT
tcp 0 0 192.168.1.52:32965 192.168.1.93:http
TIME_WAIT
tcp 0 0 192.168.1.52:32955 192.168.1.94:http
TIME_WAIT
tcp 0 0 192.168.1.52:32958 192.168.1.94:http
TIME_WAIT
tcp 0 0 192.168.1.52:32961 192.168.1.94:http
TIME_WAIT
tcp 0 0 192.168.1.52:32967 192.168.1.94:http
TIME_WAIT
tcp 0 0 192.168.1.52:32964 192.168.1.94:http
TIME_WAIT
However, I have yet to solve this problem;
Nov 9 10:41:28 lb52 nanny[3311]: READ to 192.168.1.92:80 timed out
Nov 9 10:41:40 lb52 nanny[3313]: READ to 192.168.1.94:80 timed out
Nov 9 10:41:40 lb52 nanny[3312]: READ to 192.168.1.93:80 timed out
More information about the Linux-cluster
mailing list