Tariq wali
April 09, 2012 07:44AM
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@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
Subject Author Posted

nginx upstream prematurely closed connection

Ramy Allam March 29, 2012 11:52AM

Re: nginx upstream prematurely closed connection

Maxim Dounin March 30, 2012 08:02AM

Re: nginx upstream prematurely closed connection

Tariq wali April 09, 2012 07:44AM

Re: nginx upstream prematurely closed connection

姚伟斌 April 09, 2012 09:36AM



Sorry, only registered users may post in this forum.

Click here to login

Online Users

Guests: 247
Record Number of Users: 8 on April 13, 2023
Record Number of Guests: 500 on July 15, 2024
Powered by nginx      Powered by FreeBSD      PHP Powered      Powered by MariaDB      ipv6 ready