Hello,

we're using Haproxy 1.5.5-1 to load balance traffic between frontentds running Lighttpd with mod_FastCGI and backends running a custom Perl app, based on FastCGI. Traffic between front and backends is not http - frontends open a socket to the VIP, and thus communicate to the backends.

The problem occurs when we restart haproxy due to config changes, as the frontend doesn't know the socket has closed, and starts throwing errors. After restarting Lighty on the frontends, everything works fine again.

The question is - can Haproxy handle such restarts in a better way, or is this the only way?

Below is the relevant haproxy config:

listen CI_2001 1.2.3.4:5000
        mode tcp
        balance leastconn
        server xx 192.168.0.100:5000 check inter 2000 rise 2 fall 5
        server yy 192.168.0.200:5000 check inter 2000 rise 2 fall 5

thanks, Stojan

Reply via email to