Hey,
On 05.01.2014 17:33, Lukas Tribus wrote:
Hi,
Well, after spending some time compiling testing compiling testing I
finally found that the patch
0103-OPTIM-MEDIUM-epoll-fuse-active-events-into--1.5-dev19.diff done
between 20131115 and 20131116 is causing my problems.
I also found that this problem is much easier to reproduce on Safari
than on Firefox or Chrome.
Ok. Can you try if disabling epoll works around this problem (noepoll
in
the config or command-line argument "-de" [1]) to double check it has
todo
with epoll?
Disabling epoll doesn't fix it... drat... Tested it with ss-20140104.
Could it be that it's a more subtle bug somewhere else? The (reverted)
epoll patch and some other patch currently included may make it easier
to trigger?
The weird thing is that this commit has been reverted in dev21 but I
still have the problem in dev21. So I am a bit confused....
No, dev-21 don't has this revert. dev-21 was released December 16th and
the offending commit 2f877304ef (from November 15th) was reverted via
commit 3ef5af3dcc on December 20th.
Sorry, that's actually what I meant.
Just to be on the safe side: could you download a clean and uptodate
snapshot haproxy-ss-20140104 [2], to avoid any missing patches?
Did that, with and without epoll enabled and it both fails.
So in the end, haproxy-ss-20131115 [3] works fine and
haproxy-ss-20131116
[4] has this problem, correct?
I know this triple checking sucks, but what you are reporting doesn't
make
sense because, like you said yourself, this was reverted.
No problem, check as much as you want. It sucks if I somehow push you
guys in the wrong direction.
But, Yes, that is correct. 20131115 works and 2013116 doesn't. I tested
it a couple of times. The bug is very, very subtle I just found out.
When using OSX 10.9 with safari 7 it fails with for instance 20140104
and 20131116 and works with 20131115. But, if I take an older 10.8
machine with safari 6 it works with all versions.
I am losing my mind here ;-) I'm pretty sure I saw other
platforms/browsers hang in the same way but that was all under load ~150
people accessing there servers during office starting hours.
Greets,
Sander
