Hello!

On Mon, May 31, 2010 at 11:43:21AM +0200, Axel wrote:

> Hi guys,
>
> I recently migrated from Apache to Nginx. Really cool. My
> website is much faster. BUT I have a really weird issue that
> didn't occur with Apache. It seems that some big files are
> sometimes truncated by the server. For instance, I generate a
> 200 entries videos sitemap (4600 lines) for Google (Google
> allows up to 50 000 entries FYI). Quite often, Google cannot
> parse this XML file because it is truncated in the middle and
> the XML is therefore no longer valid. It seems I have the same
> issue when I browse this XML into Safari or Firefox. When I try
> a feed validator (http://validator.w3.org/feed/check.cgi), the
> test fails 8 times out of 10 and the source is clearly
> truncated.
>
> I tried to disable gzip encoding or to adapt quite a lot of
> settings. Nothing did the trick. Have U any idea that could
> help?
> Thks a lot

1. As Anton already suggested, try looking into error log. From
symptoms you describe it looks like nginx can't write to
fastcgi_temp_path/proxy_temp_path, it should complain in logs.

2. If the above doesn't help, please follow this topic:

http://wiki.nginx.org/NginxDebugging

You have to provide config, nginx -V and debug log of a request
which exposes the problem.

Maxim Dounin

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