Could this be related to the number of concurrent connections being run?
maxconn 1024 under global seems quite low, and if your servers are holding connections open due to responding slowly could this be the cause?
Chris On 13/01/2012 03:37, John Lauro wrote:
If the refused connection concerns you, and you can't avoid starting haproxy, one option is to put up a firewall rule to block syn packets while haproxy reloads, and then unblock. That way clients will retry the connection in about 3 seconds instead of being refused.
