Re: Debugging PH state

On 2023-03-13 15:50, Christopher Faulet wrote: Le 3/6/23 à 08:50, Christian Ruppert a écrit : On 2023-03-03 16:37, Christopher Faulet wrote: Le 3/3/23 à 15:40, Christian Ruppert a écrit : So I can reproduce it. I captured the response, extracted the data which includes to entire header +

Re: Debugging PH state

Le 3/6/23 à 08:50, Christian Ruppert a écrit : On 2023-03-03 16:37, Christopher Faulet wrote: Le 3/3/23 à 15:40, Christian Ruppert a écrit : So I can reproduce it. I captured the response, extracted the data which includes to entire header + payload. I put that into a file like foo.bin and I

Re: Debugging PH state

On 2023-03-03 16:37, Christopher Faulet wrote: Le 3/3/23 à 15:40, Christian Ruppert a écrit : So I can reproduce it. I captured the response, extracted the data which includes to entire header + payload. I put that into a file like foo.bin and I start a "nc" that just serves that one response

Re: Debugging PH state

Le 3/3/23 à 15:40, Christian Ruppert a écrit : So I can reproduce it. I captured the response, extracted the data which includes to entire header + payload. I put that into a file like foo.bin and I start a "nc" that just serves that one response on every request. It works fine, no 500, no PH.

Re: Debugging PH state

So I can reproduce it. I captured the response, extracted the data which includes to entire header + payload. I put that into a file like foo.bin and I start a "nc" that just serves that one response on every request. It works fine, no 500, no PH. Even with the same request so I really don't

Debugging PH state

Hi list, we have a case where a response results into a 500 (PH): Mar 1 14:44:05.000 n095211 haproxy[2427573]: 1.2.3.4:22917 [01/Mar/2023:14:44:05.108] genfrontend_somefoo_stage~ genbackend_49140-somefoo_stage/localhost 1/0/0/-1/533 500 20378 - - PH-- 24/1/0/0/0 0/0