Nginx and cgit - upstream prematurely closed FastCGI stdout

[Richard Stanway]

Hello,
I recently had a lot of trouble similar to this, and discovered that
the fastcgi_param directive is additive - eg a later declaration of
SCRIPT_FILENAME simply adds a second SCRIPT_FILENAME to the fastcgi
parameters. You most likely have SCRIPT_FILENAME set in your "include
fastcgi_params" which means the second one later on is being ignored.

On Sat, Jan 25, 2014 at 11:22 PM, Lars <snafu at live.de> wrote:
> I'm trying to setup cgit 0.10 with nginx 1.2.1-2.2 and fastcgi 1.0.3-3.
> Unfortunately the reponse is a 502. The following message is written in the
> error.log:
>
> [error] 30956#0: *1 upstream prematurely closed FastCGI stdout while reading
> response header from upstream, client: **, server: **, request: "GET /
> HTTP/1.1", upstream: "fastcgi://unix:/var/run/fcgiwrap.socket:", host:
> "**"</i>
>
>
> My nginx site is configured as follows:
>
>    server {
>       ...
>       root /var/www/cgit/;
>       proxy_redirect off;
>
>       location ~* ^.+\.(css|png|ico)$ {
>           expires 30d;
>       }
>
>       location / {
>             include fastcgi_params;
>             fastcgi_param  SCRIPT_FILENAME  /var/www/cgit;
>             fastcgi_pass   unix:/var/run/fcgiwrap.socket;
>             fastcgi_param    PATH_INFO $uri;
>             fastcgi_param    QUERY_STRING  $args;
>       }
> }
>
> Does anybody have an idea, what is going wrong? I also tried to raise the
> timeout limit, but I have no success.
>
> Thanks!
> snafu
>
> _______________________________________________
> nginx mailing list
> nginx at nginx.org
> http://mailman.nginx.org/mailman/listinfo/nginx