Hi Lincoln, On Wed, Apr 12, 2017 at 08:24:41PM -0400, Lincoln Stern wrote: (...) > *haproxy finishes connecting to the server (SYNACK/ACK) (good)* > 38.120527 IP 99.99.99.99.8000 > 10.10.10.10.34289: Flags [S.], seq > 4125907118, ack 333335568, win 28960, options [mss 1460,sackOK,TS val > 662461622 ecr 82055529,nop,wscale 8], length 0 > 38.120619 IP 10.10.10.10.34289 > 99.99.99.99.8000: Flags [.], ack 1, > win 229, options [nop,nop,TS val 82055545 ecr 662461622], length 0 > > *And now there is nothing for 5 seconds when we should have seen a data > packet from haproxy to the server with the "length 198" payload. * > > *It appears that haproxy never tried to send the data!?!? *
Thanks for this capture! This is a regression introduced in 1.7.3 while trying to fix a bug in 1.7.2, it was fixed later by this commit : commit 51f2336ef7738c945ccedf5f1179825ac401862c Author: Willy Tarreau <[email protected]> Date: Sat Mar 18 17:11:37 2017 +0100 BUG/MAJOR: stream-int: do not depend on connection flags to detect connectio (...) Please upgrade to 1.7.5 and it will be OK. Regards, Willy
