Hello Willy,

It works perfect! Problem solved :)

>From my side, yesterday afternoon I was walking along the commits to reach 
>when was the change. I finished in the same commit "MEDIUM: connection: make 
>conn_sock_shutw() aware of lingering", and the workaround that I found was 
>using "option nolinger". Coincidentally, when I was going to write the email, 
>your answer arrived with the right fix.

The doubt that I have now is related with the trace line "-1 ENOTCONN 
(Transport endpoint is not connected)" and the relationship with the issue...

It still happend, but the problem is solved, therefore it hasn't any link 
between each one.

I found that this behaviour was introduced since the commit 
"3256073976d4f43e12e7ff97d243fdb8eb56165a - MEDIUM: stream: do not forcefully 
close the client connection anymore", but I can't reproduce it if I make the 
test sending the request (a simple curl) from outside the server network using 
a vpn link. Due that I can't see any other issue, does it fit inside the 
expected behaviour?


Thanks for your time Willy and Christopher.




________________________________
De: Willy Tarreau <[email protected]>
Enviado: viernes, 22 de diciembre de 2017 18:57
Para: Ricardo Fraile
Cc: [email protected]
Asunto: Re: Issue after upgrade from 1.7 to 1.8 related with active sessions

Hi Ricardo,

On Fri, Dec 22, 2017 at 12:37:42PM +0100, Ricardo Fraile wrote:
> Continuing with the investigation, I changed the listen only to this:
>
> listen proxy-test-tcp
>         bind *:81
>         option tcplog
>         server test1 192.168.1.101:80
>
>
> And the difference between 1.7 and 1.8 tracing the process who receive
> only 1 request is that the shutdown of the socket who receives the
> request fails with an ENOTCONN. In 1.8 continue in CLOSE_WAIT a few
> time, meanwhile in 1.7 pass to TIME_WAIT as usual.

(...)

I finally found it thanks to all your information and to Christopher's
bisect. I've just fixed it now with the attached patch. Feel free to
retest it, but I'm confident I can issue 1.8.2 now.

Many thanks for your very detailed report!

Willy

Reply via email to