On , Willy Tarreau wrote:
On Mon, Dec 16, 2013 at 02:19:28PM +0100, Sander Klein wrote:
On , Willy Tarreau wrote:
>On Mon, Dec 16, 2013 at 01:10:11PM +0100, Sander Klein wrote:
>>On , Willy Tarreau wrote:
>>>OK here's the fix, it was not a big deal, just a missing NULL
>>>after a free when loading patterns from a file. Thank you for
>>>your quick help Sander!
>>
>>Something is fishy. I've compiled a new version with your patch,
>>haproxy
>>starts but it 'just doesn't work (tm)'.
>>
>>I know this is a useless vague description but it is the best I have
>>right now. I try and have a look later to see why web pages do not
>>load
>>with this new haproxy version.
>
>You should check logs to see if you think the traffic follows the
>correct backends. We could indeed imagine an ACL match issue related
>to the thing I just fixed.
I see that the correct backends are selected. It looks like this.
Dec 16 13:05:45 localhost haproxy[28322]: x.x.x.x:49389
[16/Dec/2013:13:05:40.833] cluster1-in cluster1-53/web008
8/4314/-1/-1/4322 503 1995 - - CQVN 552/401/211/6/0 68/0
{some.site.com|Mozilla/5.0
(Win||http://some.site.com/url/goes/here/24?q_searchfield=something}
{}
"GET /url/goes/here/36?q_searchfield=something HTTP/1.1"
It indicates the visitor aborts while waiting in the queue, so
typically
a click on the STOP button while waiting. There are 68 other requests
in
the backend's queue, 211 connections on the backend and 6 on the
server.
In your config, I'm seeing a minconn 100 on the server, so the server
is
not full. The slowstart could possibly limit the accepted concurrency
however. I'll have to see if something changed with slowstart (I'm not
aware of any change there).
Hmmmm, dev20 does a slowstart when haproxy starts. Dev19 (and before)
doesn't do that.
It even does a slowstart when I reload the config file. That doesn't
seem right to me.
Greets,
Sander
