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
