On Thu, Apr 2, 2015 at 2:27 PM, Hongyi Zhao <hongyi.z...@gmail.com> wrote: > Hi all, > > My haproxy.cfg is as follows: > > --------- > global > maxconn 4096 > daemon > nbproc 3 > defaults > mode tcp > timeout connect 5000ms > timeout client 50000ms > timeout server 50000ms > frontend socks5 > bind 0.0.0.0:8888 > default_backend socks5-balance > backend socks5-balance > balance roundrobin > > server socks5-1 104.220.35.112:48178 check > server socks5-2 104.236.196.208:1234 check > server socks5-3 113.61.111.196:60088 check > server socks5-4 114.94.131.120:8118 check > server socks5-5 115.119.233.36:2235 check > server socks5-6 115.29.49.52:9999 check > server socks5-7 117.247.65.204:1080 check > server socks5-8 118.26.201.224:1080 check > server socks5-9 118.26.228.8:1080 check > ... > server socks5-31 94.23.80.193:60088 check > server socks5-32 95.163.65.88:49389 check > --------- > > I found that the the health-check results given by haproxy are not > consistent with the real statues/availabilities of these servers listed > in the backend section. > > For example, when I use the -db mode to see the message on stdout, I can > found that even haproxy reported there are serveral backend servers are > available, I still cann't use 127.0.0.1:8888 as proxy to access websites/ > urls. > > Any hints on how to let haproxy give a more precise/reliable/correctness > health-check for this case? > > Thanks in advance. > > Regards > -- > .: Hongyi Zhao [ hongyi.zhao AT gmail.com ] Free as in Freedom :. >
Hi Hongyi, What happens if you brows directly one of the IP address??? Baptiste
