On Mon, Feb 13, 2012 at 08:01:11AM +0100, Willy Tarreau wrote: > On Sun, Feb 12, 2012 at 09:12:47AM +0100, Sebastian Fohler wrote: > > I get this socket error: > > > > haproxy[63881]: Server adserver.dev.adworxs.net/adserver2.dev is DOWN, > > reason: Socket error, check duration: 8ms. 1 active and 0 backup servers > > left. 0 sessions active, 0 requeued, 0 remaining in queue. > > > > The check duration changes with every error entry, and a manual check > > won't show me any errors. Is there some way to get more information > > about the error. The stats are no help eighter. > > At this point it indicates the OS rejected a socket creation. Either > something is putting a hard limit on the number of FDs, or your source > port range is too tight.
BTW if it's only the source port range which is too tight, it's easy to force it using the per-server "source" keyword, which will assign a source port range to each of them : server adserver1 192.168.10.61:80 source 0.0.0.0:1024-65535 check inter 24000 weight 101 You must ensure that all servers are running on a different IP:port for this, otherwise you'll get socket collisions. If it does not change anything, try to replace "0.0.0.0" by the haproxy machine's IP address to force the socket binding. Regards, Willy
