Interesting, didn't really understand the upstream advisories but re-started apache on the LAMP and things have started to work better. Quite strange that apache hadn't auto started on the LAMP, not sure why that would be but it's something we would need to happen...! (It's a snapshot created role so maybe that has some bearing on it? Who knows).
On Wednesday, 9 January 2013 13:48:22 UTC, RichBos wrote: > > Hi, yes, we're getting the same error, not sure where to find the upstream > logs? > > > On Wednesday, 9 January 2013 13:46:34 UTC, RichBos wrote: >> >> OK thanks Nick, we deleted the Nginx role and tried it directly to the >> LAMPS but had problems there too (the address was rejected), this project >> is seriously trying our patience...! It's just been one thing after another >> :-( >> >> I'll re-launch and Nginx role and see what we can find out. >> >> >> On Wednesday, 9 January 2013 13:39:51 UTC, Nick Toursky wrote: >>> >>> Hi Richard, >>> >>> I'd recommend to check error log on nginx server to see, what's wrong >>> with the upstream. >>> >>> Regards, >>> Nick >>> >>> On Wed, Jan 9, 2013 at 3:38 PM, RichBos <[email protected]> wrote: >>> >>>> Hi, just wondered if anyone else has had this error? >>>> >>>> We're getting Error 502 Bad Gateway on our NGINX load balancer, tried a >>>> different instance (10.04 instead of 12.04) and it's still the same, as >>>> such we're presuming it's a problem app side (we're running x2 LAMP >>>> instances) but have no idea what or why? >>>> >>>> Any pointers appreciated....! >>>> >>>> Richard. >>>> >>>> -- >>>> >>>> >>>> >>> >>> --
