fastcgi debug and "no input file" cases

[Anıl Çetin]

Thanks Reinis and sorry that I did not read the fastcgi module
reference. The "fastcgi_intercept_errors" thing seems to solve problem
"2". Do you have an idea about problem "1"?

Php files are working as expected and it loads right php.ini file. My
problem is there is no error log displayed nor error written to file.


Reinis Rozitis yazmış:
> I have asked the same questions a bit ago and here is the thread:
>
> http://www.ruby-forum.com/topic/163301
>
> As to quick answers:
>
> 1) Probably fastcgi_index  index.php; is missing from the config.
> 2) See the url above.
> Iin short location ~ \.php$  catches and overrides before the global 
> error_page 404 (eg it sends the request to php backend even the file 
> doesnt exist))
>
> Quick workarround:
>
> location ~ .*\.php$ {
>     if (!-f $request_filename) {
>          return 404;
>     }
>     fastcgi_pass .......
>    ....
> }
>
>
> rr
>
> ----- Original Message ----- From: "Anıl Çetin" <anil at saog.net>
> To: <nginx at sysoev.ru>
> Sent: Saturday, September 06, 2008 1:51 PM
> Subject: fastcgi debug and "no input file" cases
>
>
>> Hi there,
>>
>> I have two main problems about nginx(0.6.32)+fastcgi-php (4.4.9). I am
>> spawning php with spawn-fcgi thing and chrooting. nginx and fastcgi
>> processes are on different machines.
>>
>> 1) PHP is not logging error nor display them even it defined in php.ini
>> file which I am using while spawning php. php.ini directives below;
>>
>> error_reporting = E_ALL & ~E_NOTICE
>> display_errors = On
>> log_errors = On
>> error_log = /php.errors
>> fastcgi.log = 1
>>
>> But still I see a blank page and there is no php.errors file. "/ " path
>> is also owned by php-user so there are no permission problems about 
>> that.
>>
>> 2) When an unexisted page requested from fastcgi-php, it says "no input
>> file specified". In nginx logs it shows 404 code but it doesnt shows 404
>> page, instead gives that message. How can I get rid of this message?
>> Some apache users found something with url-rewrite but I dont want to
>> use url-rewrite thing.
>>
>> Thanks.
>>
>>
>>
>>
>>
>