<div class="gmail_quote">2009/9/10 Igor Sysoev <span dir="ltr"><<a href="mailto:is@rambler-co.ru">is@rambler-co.ru</a>></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div><div></div><div class="h5">On Thu, Sep 10, 2009 at 03:10:05PM +0400, Maxim Dounin wrote:<br>
<br>
> Hello!<br>
><br>
> On Thu, Sep 10, 2009 at 06:29:18AM -0400, gloomen wrote:<br>
><br>
> > Friends, help deal with nginx. I can not go to the site.<br>
> ><br>
> > 502 Bad Gateway<br>
> > nginx/0.7.61<br>
> ><br>
> > ee /var/log/nginx-error.log<br>
> ><br>
> > 2009/09/10 14:58:19 734#0: *3 upstream prematurely closed connection while reading response header from upstream, client: 10.10.10.10, server: <a href="http://xxx.net" target="_blank">xxx.net</a>, request: "GET / HTTP/1.1", upstream: "fastcgi://<a href="http://127.0.0.1:9000" target="_blank">127.0.0.1:9000</a>", host: "<a href="http://xxx.net" target="_blank">xxx.net</a>"<br>
><br>
> So upstream probably just died. Likely to be php-related issue,<br>
> try looking there.<br>
><br>
> Anyway it isn't "bugs in nginx".<br>
<br>
</div></div>There is one nginx fastcgi bug when fastcgi sends very large headers.<br>
The attached patch fixes this. In other cases it's more like backend error.<br>
<font color="#888888"><br></font></blockquote><div><br>and I assume this problem is only for fastcgi? (ie., not happening for http proxies)<br><br>-jf<br><br></div></div>