Problem while uploading through flash

[Alok Rao]

I have the following setup for my ror server. I have nginx serving a
mongrel cluster. The nginx server has 6 worker processs, and 6 mongrel
instances in the mongrel cluster. Now the trouble comes when I am
uploading a file from a flex application. The application allows
multiple files to be selected and uploaded. The upload is sequential,
i.e. when one upload finishes the other starts. However only around 10
uploads get processed, i.e. the request for the remaining uploads doesnt
reach the mongrel cluster. When I check the error log for nginx, I find
these statements.

2008/07/01 06:34:09 [warn] 13349#0: *1 a client request body is buffered
to a temporary file /srv/hmm/tmp/0/00/0000000000, client: hostname is
deleted, server: "hostname is deleted", request: "POST
/customers/upload_image/1 HTTP/1.1", host: "hostname is deleted"
2008/07/01 06:34:10 [warn] 13349#0: *1 a client request body is buffered
to a temporary file /srv/hmm/tmp/1/00/0000000001, client: hostname is
deleted, server: "hostname is deleted", request: "POST
/customers/upload_image/1 HTTP/1.1", host: "hostname is deleted"
2008/07/01 06:34:13 [warn] 13349#0: *1 a client request body is buffered
to a temporary file /srv/hmm/tmp/2/00/0000000002, client: hostname is
deleted, server: "hostname is deleted", request: "POST
/customers/upload_image/1 HTTP/1.1", host: "hostname is deleted"
2008/07/01 06:34:14 [warn] 13349#0: *1 a client request body is buffered
to a temporary file /srv/hmm/tmp/3/00/0000000003, client: hostname is
deleted, server: web.s121.com, request: "POST /customers/upload_image/1
HTTP/1.1", host: "hostname is deleted"
.

 Now when I check the temporary folder the folder doesnt contain
anything. I am not sure what is going on. I have set the client body
temp path and client body max size as below.

 #client body temp path
    client_body_temp_path /srv/hmm/tmp/;

    # Set the max size for file uploads to 250Mb
    client_max_body_size 250M;


Please let me know if this is a misconfiguration or a bug in nginx.

Thanks,
arca1n
-- 
Posted via http://www.ruby-forum.com/.