It looks like "show errors" isn't returning anything and I am definitely seeing PR's in the logs.
Aug 26 14:45:54 HOST haproxy[20549]: IP:26591 [26/Aug/2010:14:45:53.438] http_proxy http_proxy/<NOSRV> -1/-1/-1/-1/926 400 187 - - PR-- 1093/1093/0/0/0 0/0 "<BADREQ>" Any ideas? -Joe On Aug 26, 2010, at 7:38 AM, Joe Williams wrote: > > > On Aug 25, 2010, at 11:13 PM, Willy Tarreau wrote: > >> Hi Joe, >> >> On Wed, Aug 25, 2010 at 03:46:06PM -0700, Joe Williams wrote: >>> >>> Is there anyway to look deeper into erroneous requests? Preferably having >>> haproxy log more details in the cases of something like a PR (400 status >>> code). I have some naughty clients and want to see what haproxy is seeing >>> and why it determines a request as PR. If haproxy doesn't have a facility >>> for this anyone have suggestions on tools (better than tcpdump?) to get >>> this information? >> >> yes there's already something for that. Connect to your stats socket >> using socat and issue "show errors". You will see a precise dump of >> the last invalid request and invalid response for each frontend/backend, >> with a pointer to the first faulty character. Example : >> >> $ echo "show errors" | socat stdio unix-connect:/var/run/haproxy.stat > > > Duh, for whatever reason it didn't occur to me to use the stats socket. > > As always thanks! > > -Joe > > > > Name: Joseph A. Williams > Email: [email protected] > Blog: http://www.joeandmotorboat.com/ > Twitter: http://twitter.com/williamsjoe > > Name: Joseph A. Williams Email: [email protected] Blog: http://www.joeandmotorboat.com/ Twitter: http://twitter.com/williamsjoe
