Hi,

Unfortunately, I restarted haproxy, so show errors returns little of use.
 Good to know about this command though.

root@www1-new:/var/log# echo "show errors"  | socat
unix-connect:/tmp/haproxy stdio
Total events captured on [10/Apr/2013:12:29:14.795] : 0

Here's haproxy-vv

root@www1-new:/var/log# haproxy -vv
HA-Proxy version 1.5-dev18 2013/04/03
Copyright 2000-2013 Willy Tarreau <[email protected]>

Build options :
  TARGET  = linux2628
  CPU     = native
  CC      = gcc
  CFLAGS  = -O2 -march=native -g -fno-strict-aliasing
  OPTIONS = USE_ZLIB=1 USE_OPENSSL=1 USE_PCRE=1

Default settings :
  maxconn = 2000, bufsize = 16384, maxrewrite = 8192, maxpollevents = 200

Encrypted password support via crypt(3): yes
Built with zlib version : 1.2.3.4
Compression algorithms supported : identity, deflate, gzip
Built with OpenSSL version : OpenSSL 1.0.1 14 Mar 2012
OpenSSL library supports TLS extensions : yes
OpenSSL library supports SNI : yes
OpenSSL library supports prefer-server-ciphers : yes

Available polling systems :
      epoll : pref=300,  test result OK
       poll : pref=200,  test result OK
     select : pref=150,  test result OK
Total: 3 (3 usable), will use epoll.

WILL


On Wed, Apr 10, 2013 at 5:25 AM, Lukas Tribus <[email protected]> wrote:

> > No warnings is syslog or dmesg
>
> Can you issue a "show errors" [1] on the control socket?
>
>
> > To recover I switched away from the haproxy server to
> > an older Apache-based web server.
>
> So haproxy is still in a broken condition on that server?
>
> If thats the case, you could attach strace to the process
> and see what haproxy is doing:
> sudo strace -p<pid>
>
>
> > Load was high, around 1.5
>
> How many CPUs do you have? You need to check where that
> load is coming from. Is haproxy spending cpu cycles in user
> space or where is the load coming from?
>
>
> > which is better to use - httpclose or http-server-close?
>
> "option http-server-close" enables keepalive on the client
> side, which is generally a good thing. I suggest you configure
> it along with "timeout http-keep-alive" [2]. But this has nothing
> to do with your problem and wont fix the issue.
>
>
> Regards,
> Lukas
>
>
> [1]
> http://cbonte.github.io/haproxy-dconv/configuration-1.5.html#show%20errors
> [2]
> http://cbonte.github.io/haproxy-dconv/configuration-1.5.html#option%20http-server-close
> [3]
> http://cbonte.github.io/haproxy-dconv/configuration-1.5.html#timeout%20http-keep-alive




-- 
Forio Online Simulations

Will Glass-Husain
415 440-7500x89
[email protected]
www.forio.com

Reply via email to