fcgiwrap upstream errors

[mike]

Grzegorz I don't know if you have enough time to whip up a quick perl  
launcher that uses tcp like php-fpm commonly does and makes it easy to  
say how many children you'd like? I don't know perl good enough or  
trust my hacking skills for that. Of course then it would be even one  
step closer to the solution we had talked about.

On Feb 28, 2009, at 4:04 AM,
Grzegorz Nosek <grzegorz.nosek at gmail.com> wrote:

> On sob, lut 28, 2009 at 01:52:21 -0800, Chris Cortese wrote:
>> Hello,
>
> Hi,
>
>> I'm still trying to get fcgiwrap to handle a hello, world perl cgi  
>> script.
>
> Care to post it here? Maybe it's a simple missed/double newline or  
> some
> such?
>
>> I run:
>>
>> spawn-fcgi -f /usr/local/bin/fcgiwrap -s /tmp/cgi.sock
>>
>> The first time I try to pull up my cgi-bin/test.pl file, I get:
>>
>> connect() to unix:/tmp/cgi.sock failed (13: Permission denied) while
>> connecting to upstream
>>
>> Then I tried chmod o+w /tmp/cgi.sock
>
> Yes, the web server must have access to the socket.
>
>> and then I get:
>>
>> upstream closed prematurely FastCGI stdout while reading response  
>> header
>> from upstream
>>
>> ... I read most of the 42 results I got from querying the mailing  
>> list
>> about this error.... to no avail.
>
> Please update fcgiwrap (I have just pushed a new snapshot with  
> possibly
> better error reporting), and retry. If you get a 403 response, check  
> your
> Nginx error log (fcgiwrap got the request but declined to run it for
> some reason). If it's still a 502, either Nginx is misconfigured, or
> something is badly broken in your CGI script (a CR on the hashbang  
> line
> is one tricky mofo ;))
>
> If it doesn't help, post the relevant parts of your config.
>
> Best regards,
> Grzegorz Nosek
>