Le (On) Fri, May 18, 2012 at 03:43:50PM +0200, Willy Tarreau ecrivit (wrote): > Hi Sameh, > > On Fri, May 18, 2012 at 01:55:08PM +0200, Sameh Ghane wrote: > > Le (On) Fri, May 18, 2012 at 12:05:20AM +0200, Baptiste ecrivit (wrote): > > > Hi, > > > > > > Before pointing the load-balancing algorithm, have you tried an other > > > one? (if yes, what was the result) > > > > Oops, yes of course, sorry, when removing "balance uri" the request is > > answered > > well. > > > > > Are you sure HAProxy can reach the server? > > > > Yes, both.
Actually, I was speaking about routing/network reach. One of the daemons was not started... See below. > > > Could you first enable halth checking (add the keyword check on the > > > server line description), and logging as well? > > > That may provide useful information :) > > > > Sure I could, although I don't even see a TCP connection until I remove the > > directive or request a one-char-length URI. > > I'm sorry, but I cannot reproduce it with 1.5-dev7. All the requests are > correctly forwarded to the servers. I have tried with latest snapshot too > and cannot reproduce it either. > > Does it happen systematically for you ? Could you please send the output of > "haproxy -vv" in case I spot a build option which might be worth testing ? Actually it is yet another newbie issue :( I was thinking default behavior would be to not use servers that failed at layer 4, even without checks enabled, but that was not the case. Adding the 'check' keyword fixed the issue... Not sure why I couldn't see TCP SYN packets though... Sorry again ! I'll try to implement a patch to make up for lost time, like one gathering all balance uri options into one regular expression parser. Cheers, -- Sameh Ghane
