nginx upstream prematurely closed connection

姚伟斌 nbubingo at gmail.com
Mon Apr 9 13:34:56 UTC 2012


This is also proxy log, not the static content request log.

You should be sure you have enough resources in your backend server,
like memory, connection...

2012/4/9 Tariq wali <lists at ruby-forum.com>:
> Maxim,
>
> I see the same error on few of our lamp servers and nginx serving static
> content .
> I have looked for clues in apache error logs and syslog messages but
> can't establish a connection ..
>
> 2012/03/21 00:00:01 [error] 569#0: *10867863 upstream prematurely closed
> connection while reading response header from upstream, client:
> 121.243.22.130, server: _, request: "GET / HTTP/1.1", upstream:
> "http://127.0.0.1:8080/", host: "servername.net"
> 2012/03/22 00:00:01 [error] 568#0: *10869967 upstream prematurely closed
> connection while reading response header from upstream, client:
> 121.243.22.130, server: _, request: "GET / HTTP/1.1", upstream:
> "http://127.0.0.1:8080/", host: "servername.net"
> 2012/03/23 00:00:01 [error] 569#0: *10872221 upstream prematurely closed
> connection while reading response header from upstream, client:
> 121.243.22.130, server: _, request: "GET / HTTP/1.1", upstream:
> "http://127.0.0.1:8080/", host: "servername.net"
>
> I would appreciate a direction I can take this issue in ..'
>
>
> T
>
> --
> Posted via http://www.ruby-forum.com/.
>
> _______________________________________________
> nginx mailing list
> nginx at nginx.org
> http://mailman.nginx.org/mailman/listinfo/nginx



More information about the nginx mailing list