Re: SD-termination cause

Hi Maksim, On Wed, Jun 05, 2019 at 09:59:29AM +0200, Willy Tarreau wrote: > I'm still trying to fix this mess, it's not trivial at all and may > even require an extra -dev. So expect some updates later. Just a quick note to let you know that Olivier just fixed a directly related issue in 2.0-dev

Re: SD-termination cause

Hi Maksim, On Tue, Jun 04, 2019 at 07:55:09AM +0300, ?? ? wrote: > Sorry for bothering you, but do you have any news about this case? I just wanted to send you a quick update on this to let you know that it's not forgotten, it is that while taking a look at the connection setup parts,

Re: SD-termination cause

Hi Willy! Sorry for bothering you, but do you have any news about this case? чт, 23 мая 2019 г. в 10:35, Willy Tarreau : > Hi Maksim, > > On Thu, May 23, 2019 at 10:00:19AM +0300, ?? ? wrote: > > 2nd session (from haproxy to ssl-enabled backend A, dumped with tshark > for > > better

Re: SD-termination cause

Hi Maksim, On Thu, May 23, 2019 at 10:00:19AM +0300, ?? ? wrote: > 2nd session (from haproxy to ssl-enabled backend A, dumped with tshark for > better readability): > 1 09:10:48.222518 HAPROXY -> BACKEND_A TCP 94 36568 -> 9790 [SYN] Seq=0 > Win=26520 Len=0 MSS=8840 SACK_PERM=1 TSval=30

Re: SD-termination cause

Hi, Willy! This kind of errors only happen on proxy-sections with ssl-enabled backends ('ssl verify none' in server lines). In order to find out what realy happens from network point of view I added one plain-http backend to one of the proxy-sections. Then I captured the sutuation when request fai

Re: SD-termination cause

Hi Maksim, On Tue, May 21, 2019 at 01:47:30PM +0300, ?? ? wrote: > Hi! > > I've run into some weird problem of many connections failed with SD status > in log. And I have no idea how to discover the source of the problem. > > >From the point of client it looks like this: > * Client (

SD-termination cause

Hi! I've run into some weird problem of many connections failed with SD status in log. And I have no idea how to discover the source of the problem. >From the point of client it looks like this: * Client (located on the same machine as haproxy) successfully opens a connection to haproxy over loop