Troubleshooting connections
Denis
denismpa at gmail.com
Thu May 24 00:13:08 EST 2007
Proxy-Node1:~# lsmod |grep ip_vs
ip_vs_wrr 3200 0
ip_vs_wlc 2176 1
ip_vs_sh 2688 0
ip_vs_sed 2176 0
ip_vs_rr 2176 0
ip_vs_nq 2176 0
ip_vs_lc 2048 0
ip_vs_lblcr 6916 0
ip_vs_lblc 5892 0
ip_vs_ftp 6024 0
ip_vs_dh 2688 0
ip_vs 77664 24
ip_vs_wrr,ip_vs_wlc,ip_vs_sh,ip_vs_sed,ip_vs_rr,ip_vs_nq,ip_vs_lc,ip_vs_lblcr,ip_vs_lblc,ip_vs_ftp,ip_vs_dh
Proxy-Node1:~# uname -r
2.6.8-2-386
Proxy-Node1:~# cat /etc/debian_version
4.0
Proxy-Node1:~# ip addr show eth2
4: eth2: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 1000
link/ether 00:0f:ea:26:b4:17 brd ff:ff:ff:ff:ff:ff
inet 172.16.8.83/21 brd 172.16.15.255 scope global eth2
inet 172.16.8.77/21 brd 172.16.15.255 scope global secondary eth2
inet6 fe80::20f:eaff:fe26:b417/64 scope link
valid_lft forever preferred_lft forever
Proxy-Node1:~# ipvsadm -L -n
IP Virtual Server version 1.2.0 (size=4096)
Prot LocalAddress:Port Scheduler Flags
-> RemoteAddress:Port Forward Weight ActiveConn InActConn
TCP 172.16.8.77:3128 wlc persistent 180
-> 172.16.8.85:3128 Route 4 2 215
-> 172.16.8.86:3128 Route 1 8 150
-> 172.16.8.83:3128 Local 5 228 374
This output is from the node that I updated to Debian etch with a dist-upgrade.
If I call a ipvsadm -Lnc I can see that the mostly of connections that
is forwarded to another nodes, stay with the status "SYN_RECV".
When the connection is forwarded for the director own self it works.
May be I have to update something?
Because it was working ok, before the dist upgrade, so I think that
the configurations are correctly configured.
Thanks.
2007/5/21, Simon Horman <horms at verge.net.au>:
> On Fri, May 11, 2007 at 05:41:31PM -0300, Denis wrote:
> > Hi dears!
> >
> > I have an UltraMonkey 3 streamlined load balancing system. There are only
> > two servers in this setup. The servers run as both directors and squid proxy
> > servers. The LVS manages 1 virtual IP shared on both servers.
> >
> > Few days ago I made an dist-upgrade to etch version on one of the machines.
> >
> > Everything appeared to be working properly.
> >
> > Today I noted that lots of clients couldn't connect to the servers.
> > And surf the web.
> >
> > If I try to connect to the proxys by the real IPs, I get success.
> >
> > But by the virtual IP I cannot connect.
> >
> > looking at
> > #ipvsadm -L -nc |grep 172.16.224.116
> >
> > I got this:
> >
> > TCP 00:40 SYN_RECV 172.16.224.117:1722 172.16.8.77:3128 172.16.8.86:3128
> > TCP 00:40 SYN_RECV 172.16.224.117:1723 172.16.8.77:3128 172.16.8.86:3128
> > TCP 00:46 SYN_RECV 172.16.224.117:1733 172.16.8.77:3128 172.16.8.86:3128
> >
> > What can I do to solve that?
> >
> > actually when I get problems with LVS I get little lost to troubleshoot.
> >
> > Can U tell me how do u troubleshoot your own LVSs ?
>
> What does the ouput of ipvsadm -Ln look like?
>
>
> --
> Horms
> H: http://www.vergenet.net/~horms/
> W: http://www.valinux.co.jp/en/
>
>
--
Ultra Monkey - http://www.ultramonkey.org/
To UNSUBSCRIBE, email to lisa at ultramonkey.org, with a body:
unsubscribe ultramonkey-users your-email-address at some.domain
where "your-email-address at some.domain" is YOUR email address.
More information about the Ultramonkey-users
mailing list