| From | Sent On | Attachments |
|---|---|---|
| Anıl Çetin | Sep 6, 2008 3:50 am | |
| Reinis Rozitis | Sep 6, 2008 4:23 am | |
| Reinis Rozitis | Sep 6, 2008 4:31 am | |
| Anıl Çetin | Sep 6, 2008 4:54 am | |
| Anıl Çetin | Sep 6, 2008 1:31 pm | |
| Chris Savery | Sep 6, 2008 4:28 pm |
| Subject: | Re: fastcgi debug and "no input file" cases | |
|---|---|---|
| From: | Chris Savery (chri...@public.gmane.org) | |
| Date: | Sep 6, 2008 4:28:38 pm | |
| List: | ru.sysoev.nginx | |
Here's a few snippets from my config that are definitely working:
http { ... index index.php; ... server { ... root /var/www/whatever/you/use location ~ \.php$ { fastcgi_pass 127.0.0.1:9000; include fastcgi_params; } ... } } Make sure that your fastgi_params file contains this:
fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
without that line you will get the "no input specified" msg because an incorrect or missing script name gets passed on to php.
Chris :)
Anıl Çetin wrote:
The problem "3" is making default index "index.php". I did it by using rewrite;
location = / { rewrite ^ /index.php; }
must I use rewrite? When I do it like;
location / { index index.php; }
nginx does not pass "index.php" to fastcgi, rather than it looks in its own root and of course says 404.
thanks.
Anıl Çetin yazmış:
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.





