Thanks Maxim.

So I guess my issue is really not related to that warning.
It seems the connection is closed before the entire file was downloaded by the client. Once it happens, the client has the shortened version in its cache and is unable to read the full video
Any idea about it?

Thanks

Axel


Le 7 juil. 2010 à 17:44, Maxim Dounin a écrit :

> Hello!
>
> On Wed, Jul 07, 2010 at 05:00:21PM +0200, Axel wrote:
>
>> Hi guys,
>>
>> another quick question: I'm still trying to figure out why sometimes some files are truncated when they arrive on the client's browser. For instance, a video that lasts 1 minute is cut after 5 second on the browser. I found this in my logs:
>>
>> 2010/07/07 16:55:02 [warn] 11417#0: *1389 an upstream response is buffered to a temporary file /usr/local/nginx/fastcgi_temp/8/03/0000000038 while reading upstream, client: 213.215.7.xxx, server: www.yyy.com, request: "GET /reyrant/cyrylot-87.htm HTTP/1.0", upstream: "fastcgi://127.0.0.1:9000", host: "www.yyy.com"
>>
>> I tried to issue:
>> root@ns20xxx46:/# ls /usr/local/nginx/fastcgi_temp/8/03/0000000038
>> ls: cannot access /usr/local/nginx/fastcgi_temp/8/03/0000000038: No such file or directory
>>
>> What is that a Warning? Is it normal the file does not exist?
>
> It's warning which mean to say "hey, you are hitting disk, and
> may want to tune your proxy_buffers". And yes, it's normal that
> file isn't visible on disk as it's temporary file and unlinked
> right after creation.
>
> Maxim Dounin
>
> _______________________________________________
> nginx mailing list
> nginx@nginx.org
> http://nginx.org/mailman/listinfo/nginx


_______________________________________________
nginx mailing list
nginx@nginx.org
http://nginx.org/mailman/listinfo/nginx