On Sat, Jun 30, 2018 at 04:35:21PM +0200, Thierry FOURNIER wrote:
> Hi,
>
> It have a bug in the Lua HTTP parser which is a trigger for close-wait
> behavior.
>
> I thing that the close-wait state is not due to the parser bug. I will
> sent anoter email with a method to reproduce it.
>
> This pa
Hi List,
It have a bug with internal applets. Maybe this bug impacts other parts
like these subject "Connections stuck in CLOSE_WAIT state with h2".
when the applet requires more data and doesn't read the input buffer
buffer, and when the client stops waiting and break the connection, a
CLOSE-WAI
Hi,
It have a bug in the Lua HTTP parser which is a trigger for close-wait
behavior.
I thing that the close-wait state is not due to the parser bug. I will
sent anoter email with a method to reproduce it.
This patch must be backported from 1.6 to 1.8.
Thierry
>From e0790d51546e7f032076852f2dd4
We have 2 haproxy servers ( 1.8.9 + 1.7.10) with the same traffic, Api
for mobile application. (different domains - one service).
Today in the same time 2 servers went to sigfault. I have difficulties to
create dump. I need some time to figure how to do it. Strange thing is that
they restarted a
4 matches
Mail list logo