On 04/02/12 08:56, niraj wrote:
> the error of Nginx is not system admin friendly at all. from the below
> error we are not able to conclude anything.

nginx error logs is very friendly and useful.

> how to solve the such kind of issue by checking the error log ??????
>
>
> 2012/03/30 09:58:05 [error] 29619#0: *1 upstream closed prematurely
> FastCGI stdout while reading response header from upstream, client:
> 192.168.1.44, server: localhost, request: "GET
> /cgi-bin/baybuy_vendx/index.cgi?vendx_action=myoffice_commonuser&userid=53616c7465645f5f1fed4bcaa10a7da569ecb5a53e5a718a&page=1b662ecc4610f940ec530e3bc8762169&BusinessGrID=1
> HTTP/1.1", upstream: "fastcgi://unix:/var/run/fcgiwrap.socket:", host:
> "192.168.1.225:90", referrer:
> "http://192.168.1.225:90/cgi-bin/baybuy_vendx/index.cgi?vendx_action=validate_both2"

words "upstream closed prematurely FastCGI stdout" show, that problem is
probably in FastCGI server.

See FastCGI manager error logs, and OS logs (one of usual problem is segfault in
FastCGI process).

--
Anton Yuzhaninov

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