Hi Ben, On Thu, Mar 24, 2011 at 05:20:26PM -0400, Ben Timby wrote: > I am testing HAProxy 1.5-dev4, actually, I used the archive: > haproxy-ss-20110317.tar.gz. And I am seeing some really weird results. > I have attached a netstat command (netstat -anp | grep haproxy). I am > using the following config: > > -- > global > log 127.0.0.1 local2 > chroot /var/chroot/haproxy > pidfile /var/run/haproxy.pid > maxconn 4000 > user haproxy > group haproxy > daemon > > defaults > log global > option dontlognull > option redispatch > timeout connect 10000 # default 10 second time out if a backend is not > found > timeout client 1d > timeout server 1d > maxconn 60000 > retries 3 > > # Beta Listeners > > listen ftpes-vip00 > bind 172.16.1.190:21 > mode tcp > option tcplog > balance roundrobin > server alderaan 10.19.78.38:21 check > server ansion 10.19.78.18:21 check > > listen ftpis-vip00 > bind 172.16.1.190:990 > mode tcp > option tcplog > balance roundrobin > server alderaan 10.19.78.38:990 check > server ansion 10.19.78.18:990 check > -- > > That's a whole lotta' connections to itself. also, I am unable to > connect to the services. 1.4 worked fine with the same config. > > What I am doing wrong? Any ideas? (...) > tcp 0 0 172.16.1.190:21 172.16.1.190:53504 > ESTABLISHED 17536/haproxy > tcp 0 0 172.16.1.190:21 172.16.1.190:53248 > ESTABLISHED 17536/haproxy > tcp 0 0 172.16.1.190:21 172.16.1.190:54016 > ESTABLISHED 17536/haproxy > tcp 0 0 172.16.1.190:21 172.16.1.190:53760 > ESTABLISHED 17536/haproxy > tcp 0 0 172.16.1.190:21 172.16.1.190:50944 > ESTABLISHED 17536/haproxy (...)
I'm sure you hit the issue that David has fixed a few days ago. In short, due to a parsing issue on the server address, haproxy is reconnecting to IP 0.0.0.0 on the target port. IP 0.0.0.0 is any IP, and the system connects to whatever IP it is listening on. Thus you have a loop. I merged the fix into the git tree, it is in the 20110324 snapshot if you want to give it a try again. I need to quickly release an 1.5-dev5 with this fix, but as I have found another very minor one, I'd like to see if I can fix it too before the release. Thanks, Willy
