Testing an upgrade from haproxy 2.4.15 to 2.4.16 and started getting some 500's with session state IH---, only on load balancers upgraded to 2.4.16.
It's only affecting requests from a couple of customers (about 0.08% of traffic) and I haven't reproduced it in a testing environment yet. I assume there's something unusual about these requests. All the failed requests are POSTS over HTTP/2.0, but so are most of the successful requests, so I don't think that's necessarily relevant. haproxy isn't logging anything unusual at the time (just the normal http request log, no exceptions being logged or anything). Any thoughts on what might've changed in 2.4.16 to cause this? Is there any way to ask haproxy to log something specifically when it hits whatever internal error causes an I state? I'm going to roll back to 2.4.15 for now. James Brown
