Le 08/10/2024 à 11:05, Luke Seelenbinder a écrit :
Hi Christopher,
I was out last week, but we were able to gather a few more pieces of data.
1) We ran some tcpdumps, and nothing odd popped up at all. Given our traffic
levels, we were actually surprised how few RST, etc. we had. Any TCP issues that
did occur did *not* coincide with the SD-- log lines.
2) We've confirmed this also happens with similar rates on publicly served
traffic, as well (which mostly uses varnish as the backend). The symptom is a
slightly truncated response body.
That left us with the upgrade to 3.0.5 as the culprit, so we're going to need to
rollback to 3.0.4 for now. If we have the time, we'll run some more tests on a
limited subset of servers to see if we can find out anything more.
Thanks Luke for the info. For me, there are just few commits that may be related
(with no explanation):
* e2a93b6492 ("BUG/MEDIUM: stconn: Report error on SC on send if a previous SE
error was set")
* 0be5e36d8c ("BUG/MAJOR: mux-h1: Wake SC to perform 0-copy forwarding in
CLOSING state")
* aa43ed1719 ("BUG/MEDIUM: http-ana: Report error on write error waiting for
the response")
The first one is the best candidate. If you perform some tests, you can try to
revert it.
--
Christopher Faulet
