Absolutley, here is the config:

global
    log         127.0.0.1 local0 crit
    pidfile     /var/run/haproxy.pid
    stats socket /var/run/haproxy.stat mode 666
    nbproc 2
    maxconn     65000
    tune.maxrewrite 1024
    tune.bufsize 32768
    user        haproxy
    group       haproxy
    daemon


defaults
    mode        http
    log         global
    option      dontlognull
    option      httplog
    option http-server-close
    #option forwardfor       except 127.0.0.0/8
    option forwardfor header X-Real-IP
    option      redispatch
    stats enable
    stats auth change:me
    stats uri /stav1
    timeout connect 5000 # default 5 second time out if a backend is not
found
    timeout client 300s
    timeout server 300s
    #timeout http-request    10s
    #timeout queue           1m
    #timeout http-keep-alive 10s
    timeout check           5s
    maxconn     65000
    retries     3

frontend sinatra *:5000
    default_backend            sinatra_backend

backend sinatra_backend
    mode http
    balance roundrobin
    option httpchk HEAD /ha.txt HTTP/1.0

On Mon, Mar 11, 2013 at 4:36 PM, Thomas Heil <[email protected]>wrote:

>  Hi,
>
>
> On 11.03.2013 21:23, Saul Waizer wrote:
>
> Hello List,
>
>  I am experiencing some erratic behavior on 2 fresh installs (V 1.4.22)
> that I've never seen before. Basically the haproxy is taking 100% of cpu,
> there is nothing running on the box and there is no traffic going through
> it, yet the load average is 8 and and cpu is constantly hitting 100%. I
> have the same installation/configuration running on 20+ servers and never
> experienced this before, nothing on the logs either...here is the relevant
> information:
>
>  Crazy. Could we take a look at your config? I had a similar problem
> years ago, when using the option transparent.
>
>  HA-Proxy version 1.4.22 2012/08/09
> Copyright 2000-2012 Willy Tarreau <[email protected]>
>
>  Build options :
>   TARGET  = linux26
>   CPU     = generic
>   CC      = gcc
>   CFLAGS  = -O2 -g -fno-strict-aliasing
>   OPTIONS = USE_PCRE=1
>
>  Default settings :
>   maxconn = 2000, bufsize = 16384, maxrewrite = 8192, maxpollevents = 200
>
>  Encrypted password support via crypt(3): yes
>
>  Available polling systems :
>      sepoll : pref=400,  test result OK
>       epoll : pref=300,  test result OK
>        poll : pref=200,  test result OK
>      select : pref=150,  test result OK
> Total: 4 (4 usable), will use sepoll.
>
>  Linux ip-x.x.x.x 2.6.21.7-2.fc8xen #1 SMP Fri Feb 15 12:34:28 EST 2008
> x86_64 x86_64 x86_64 GNU/Linux
>
>  CentOS release 5.4 (Final)
>
>  Any suggestions are greatly appreciated.
>
>  Thank You
>
>
>  cheers
> thomas
>

Reply via email to