File upload with a 500 response

woodsmar nginx-forum at nginx.us
Fri Jun 18 18:25:10 MSD 2010


[size=small]
Hi Maxim

Many thanks for your excellent suggestion!

I tried the patch but unfortunately that didn't work as I still get the
same behaviour. With debugging turned on the following is an excerpt
from the error log: 


2010/06/18 13:16:48 [debug] 30676#0: *1 http proxy status 500 "500
Internal Server Error"
2010/06/18 13:16:48 [debug] 30676#0: *1 http proxy header: "Server:
MochiWeb/1.1"
2010/06/18 13:16:48 [debug] 30676#0: *1 http proxy header: "Date: Fri,
18 Jun 2010 12:16:48 GMT"
2010/06/18 13:16:48 [debug] 30676#0: *1 http proxy header:
"Content-Type: text/html"
2010/06/18 13:16:48 [debug] 30676#0: *1 http proxy header:
"Content-Length: 272"
2010/06/18 13:16:48 [debug] 30676#0: *1 http proxy header done
2010/06/18 13:16:48 [debug] 30676#0: *1 HTTP/1.1 500 Internal Server
Error
Server: nginx/0.7.65
Date: Fri, 18 Jun 2010 12:16:48 GMT
Content-Type: text/html
Connection: keep-alive
Content-Length: 272

2010/06/18 13:16:48 [debug] 30676#0: *1 write new buf t:1 f:0 08DAB75C,
pos 08DAB75C, size: 167 file: 0, size: 0
2010/06/18 13:16:48 [debug] 30676#0: *1 http write filter: l:0 f:0
s:167
2010/06/18 13:16:48 [debug] 30676#0: *1 file cleanup: fd:12
2010/06/18 13:16:48 [debug] 30676#0: *1 http cacheable: 0
2010/06/18 13:16:48 [debug] 30676#0: *1 http upstream process upstream
2010/06/18 13:16:48 [debug] 30676#0: *1 pipe read upstream: 1
2010/06/18 13:16:48 [debug] 30676#0: *1 pipe preread: 272
2010/06/18 13:16:48 [debug] 30676#0: *1 readv: 1:3642
2010/06/18 13:16:48 [error] 30676#0: *1 readv() failed (104: Connection
reset by peer) while reading upstream, client: 1
27.0.0.1, server: myserver.com, request: "POST /some/url HTTP/1.1",
upstream: "http://some/other/url", host: "127.0.0.1"
2010/06/18 13:16:48 [debug] 30676#0: *1 pipe recv chain: -1
2010/06/18 13:16:48 [debug] 30676#0: *1 pipe write downstream: 1
2010/06/18 13:16:48 [debug] 30676#0: *1 pipe write downstream done
2010/06/18 13:16:48 [debug] 30676#0: *1 event timer add: 13:
60000:1258182058
2010/06/18 13:16:48 [debug] 30676#0: *1 http upstream exit: 00000000
2010/06/18 13:16:48 [debug] 30676#0: *1 finalize http upstream request:
0
2010/06/18 13:16:48 [debug] 30676#0: *1 finalize http proxy request
2010/06/18 13:16:48 [debug] 30676#0: *1 free rr peer 2 0
2010/06/18 13:16:48 [debug] 30676#0: *1 close http upstream connection:
13
2010/06/18 13:16:48 [debug] 30676#0: *1 event timer del: 13: 1258182058
2010/06/18 13:16:48 [debug] 30676#0: *1 event timer del: 13: 1258181956
2010/06/18 13:16:48 [debug] 30676#0: *1 http upstream temp fd: -1
2010/06/18 13:16:48 [debug] 30676#0: *1 http output filter "/some/url"
2010/06/18 13:16:48 [debug] 30676#0: *1 copy filter: "/some/url"
2010/06/18 13:16:48 [debug] 30676#0: *1 http postpone filter "/some/url"
BFAB4798
2010/06/18 13:16:48 [debug] 30676#0: *1 write old buf t:1 f:0 08DAB75C,
pos 08DAB75C, size: 167 file: 0, size: 0
2010/06/18 13:16:48 [debug] 30676#0: *1 write new buf t:0 f:0 00000000,
pos 00000000, size: 0 file: 0, size: 0


There is in fact an error in there - "readv() failed (104: Connection
reset by peer)". So is this the upstream server closing the connection
before it received the entire body, because it already responded?

[/size]

Posted at Nginx Forum: http://forum.nginx.org/read.php?2,99801,99902#msg-99902




More information about the nginx mailing list