Re: Diagnose a PD-- status

Christopher, We couldn’t had the error reproduced today : both dataset and client tool were updated. However, I keep the configuration options at hand if I ever need to debug this issue further again. Thanks for your time on this. Regards, Mildis > Le 7 nov. 2017 à 10:14, Christopher Faulet

Re: Diagnose a PD-- status

Le 06/11/2017 à 16:47, Mildis a écrit : Hi Christopher, Configuration is attached. The domain2backend map sends data mostly to bck-traefik. Hi Mildis, At first glance, I don't see anything strange here. The compression filter is not supposed to fail this way. So there is definitely

Re: Diagnose a PD-- status

Hi Christopher, Configuration is attached. The domain2backend map sends data mostly to bck-traefik. $ haproxy -vv HA-Proxy version 1.7.91~bpo7+1 2017/08/24 Copyright 2000-2017 Willy Tarreau Build options : TARGET = linux2628 CPU = generic CC = gcc CFLAGS =

Re: Diagnose a PD-- status

Hi, Le 02/11/2017 à 17:16, Mildis a écrit : [WARNING] 305/144718 (21260) : HTTP compression failed: unexpected behavior of previous filters This warning is very suspicious. It should not happen. Could you share your configuration and "haproxy -vv" output please ? -- Christopher Faulet

Re: Diagnose a PD-- status

t; However, ‘show errors’ does not tell anything about that. > > backend server returned 200, haproxy returned 200 to the client. > The entire request took 202ms and returned 15k of data : 3/0/0/199/202 200 > 15262 > > Is there a way to diagnose further the PD status ? > M

Diagnose a PD-- status

Hi, I got a request ending in a PD status. However, ‘show errors’ does not tell anything about that. backend server returned 200, haproxy returned 200 to the client. The entire request took 202ms and returned 15k of data : 3/0/0/199/202 200 15262 Is there a way to diagnose further the PD status