This is the definition of the backend checks:
server adserver2 192.168.10.61:80 check inter 240000 we
ight 100
listen adserver.adworxs.net
bind 192.168.10.68:80
mode http
log global
option dontlognull
option httpclose
option forwardfor
maxconn 10000
clitimeout 1200000
balance roundrobin
contimeout 1200000
srvtimeout 1200000
retries 10
option httpchk HEAD /www/admin/index.php HTTP/1.0
stats enable
stats uri /haproxy?stats
stats realm adserver.adworxs.net
stats auth admin:<pw>
stats show-node
stats refresh s
I've already had the problem that the check intervals collided with the
check timeouts, but I thought I solved that problem by configuring
longer timeouts and check intervals longer than timeout times.
Best regards
Sebastian
On 12.02.2012 09:40, Baptiste wrote:
On Sun, Feb 12, 2012 at 9:12 AM, Sebastian Fohler<[email protected]> 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.
Best regards
Sebastian
Hey,
It seems HAProxy was not able to do the TCP connection to the server.
How is this server declared in your configuration?
I'm also interested by your timeout values.
cheers
