another symptom we saw often was we could not get to the stats page or even ssh into the box when this was happening
On Wed, Mar 3, 2010 at 2:48 PM, Joe Stein <joe.st...@medialets.com> wrote: > how do you change the timeout setting? > > This is what we have now in default (using same config as before) > > contimeout 1m > clitimeout 240s > srvtimeout 240s > > > > On Wed, Mar 3, 2010 at 2:40 PM, Willy Tarreau <w...@1wt.eu> wrote: > >> On Wed, Mar 03, 2010 at 02:34:46PM -0500, Joe Stein wrote: >> > the problem got serious so I stood up another LB set of instances and >> > installed v1.3.23 all traffic is getting routed over to it. >> > >> > what I used to see in the logs where just NOSRV 503 in the haproxy log >> once >> > it hit max con. >> >> OK but those are just two words in a line, the most important ones are >> around that. >> >> > Now that we upgraded (or rather migrated) let me see if the >> > issue continues or another one presents itself. so far so good but no >> burst >> > yet. >> > >> > Most likely "Everything worked once I upgraded" will be the result >> (isn't it >> > always), but thanks for the quick response as always. >> >> In my opinion, no such issue was known in 1.3.19, so no fix was applied >> either. And since it will be produced by default with a standard config, >> I find it very likely that it's just an improper timeout setting. >> >> It's good that you upgraded from 1.3.19, because it had a bug causing a >> risk of segfault if you used the unix socket. >> >> Regards, >> Willy >> >> > > > -- > /* > Joe Stein, 973-944-0094 > http://www.medialets.com > */ > -- /* Joe Stein, 973-944-0094 http://www.medialets.com */
