On Sun, Jul 5, 2009 at 8:37 PM, Tobias Lott<tlott@gamesnet.de> wrote:

> Additionally I got another issue, which is that customers getting 502s
> pretty damn randomly (using nginx-0.7.61 as frontend and apache 2.2.11
> as backend for the time being, which gonna gets migrated soon). Was
> trying to tweak a lil with proxy_*_timeout and keepalive_timeout but
> since its not reproducible I can't be sure its fixed, are there some
> "good to go" values or another option to check?

Is it nginx giving the 502 or apache?