*From: *Patrick Hemmer <[email protected]> *Sent: * 2014-04-16 17:38:54 E *To: *[email protected] <[email protected]> *Subject: *haproxy incorrectly reporting connection flags
> With 1.5-dev22, we have a scenario where haproxy is saying the client > closed the connection, but really the server is the one that closed it. > > Here is the log entry from haproxy: > haproxy[12540]: 10.230.0.195:33580 storage_upd > storage_upd/storage_upd_2 0/0/0/522/555 0/0/0/0/0 0/0 412/271 200 CD-- > 73E3-20FF5 + GET /1/public_link/1BMcSfqg3OM4Ng HTTP/1.1 > > The log format is defined as: > capture request header X-Request-Id len 64 > log-format %ci:%cp\ %ft\ %b/%s\ %Tq/%Tw/%Tc/%Tr/%Tt\ > %ac/%fc/%bc/%sc/%rc\ %sq/%bq\ %U/%B\ %ST\ %tsc\ %hrl\ +\ %r > > Attached is the haproxy config, along with a packet capture between > haproxy and the backend server. > The packet capture shows that the backend server listening on port > 4001 sent a TCP FIN packet to haproxy first. Therefore haproxy > shouldn't have logged it with "C---" > > -Patrick Any feedback on this? I can happily provide any additional information if needed. -Patrick
