ok thanks willy. it makes sense. we were using 1.3.15.5 so i guess we should upgrade to 1.3.15.20 as i see there is at least one critical bug and several other bugfixes that may clean up some of my issues.
On Fri, Oct 9, 2009 at 5:14 PM, Willy Tarreau <[email protected]> wrote: > On Fri, Oct 09, 2009 at 04:14:02PM -0400, Greg Gard wrote: >> hi, >> >> we run 1.13.5 and have been very happy for the most part > > I think you meant 1.3.15. Please check then that it's a "recent" 1.3.15.X, > eg 1.3.15.10. > >> lately our >> traffic has increased and we are now getting more 500 errors. not sure >> what the cause is and don't think it is an haproxy problem as yet. > > Haproxy only emits status 500 on critical errors (eg: not enough memory). > And I don't think at all that any misbehaviour from it could cause a > server to issue a 500 either, so I tend to agree with you on the statement > above. > >> my >> question though is that i had maybe 200 500 errors today, but my stats >> page shows no problems. all of the haproxy ----- status codes are fine >> in the log no flags that i can see, just lots of server errors. are >> these not considered errors by haproxy stats? > > Exactly. Haproxy counts the errors that it is related to. Eg: timeouts, > disconnections, invalid HTTP messages, etc... But if the application > server returns an error 500, it normally forwards it and has no reason > to count an error if the response is correctly delivered. While I agree > it may sound surprizing at first, imagine the mess it would make for > people who balance outgoing HTTP proxies ! They would get a lot of false > errors when retrieving responses from random servers on the net. > > Regards, > Willy > > -- greg gard, psyd www.carepaths.com
