On Tue, Jul 09, 2013 at 09:37:06PM +0300, ?zg?r Kazan??? wrote: > And the browser side: > "502 Bad Gateway" > (Actually the same error occurs when trying with any filenames (no matter > exists or not) ended with .cgi.
... and the log probably says "upstream prematurely closed FastCGI stdout". What happens here is that fork(2) fails, there is no stdout to send to nginx and the error is reported in stderr to nginx. I'm wondering if there is some option in nginx to tell it to log the stderr stream to the logfile. Alternatively slowcgi(8)'s error logging should be improved. -- I'm not entirely sure you are real.
