Hi Thomas,
On 02.04.2013 21:02, Thomas Heil wrote:
Of course, it matters. As you explained the problem should be arround
patch 86 up to 101. How does you haproxy -vv
look like? Do you use compression or SSL? Could you eliminate Patch
91,92 and 98?
haproxy -vv looks like:
sander@lb01-a:~$ /usr/sbin/haproxy -vv
HA-Proxy version 1.5-dev17 2012/12/28
Copyright 2000-2012 Willy Tarreau <[email protected]>
Build options :
TARGET = linux26
CPU = generic
CC = gcc
CFLAGS = -O2 -g -fno-strict-aliasing
OPTIONS = USE_LINUX_SPLICE=1 USE_LINUX_TPROXY=1 USE_LIBCRYPT=1
USE_GETADDRINFO=1 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 0.9.8o 01 Jun 2010
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.
I do not use SSL or compression in my current config. I was actually
upgrading to the latest snapshot to start using SSL :-)
I've recompiled without path 91,92 and 98 but I still see the same
problem. The websites on the new cluster (nginx) don't load, or
partially load. And, the sites on the old cluster (apache) behave
normally.
I'm not sure, but it almost looks like the timing issue I had with
POST's back in the early dev17 days. Although I'm doing a simple get
right now.
Greets,
Sander
