Why don't FastCGI+Nginx see PHP settings?

Question

PHP

Deployed on the server a classic bundle from Apache:8080+Nginx:80+FastCGI. At the same time, php, when accessing scripts through port 80, stopped seeing its settings (default ones are loaded). I tried to set the settings in php_value through .htaccess - all the same, they are not seen at close range.
And through the 8080 port, all settings are normally pulled up.
Compare: clio.su/test.php vs. clio.su:8080/test.php ( parameter upload_max_filesize for testing in php.ini set to 4M, in .htaccess 8M, default 2M)

work of a sheaf through fastcgi? I feel that the problem is solved elegantly, but after shoveling Yandex, I did not find a solution.

PS:And another related question, also related to fastcgi. When using the php mail() function, all mail is now sent with the FROM field: <[email protected]_server_name>… and is accordingly taxied by mailers due to the invalidity of the address. The sendmail_from php variable does not apply.

UPD: Small clarification. We have spawn_fcgi

Answer 1

classic bundle from Apache:8080+Nginx:80+FastCGI

wtf? You already decide - either Apache or fastcgi. The classic link is
nginx:80 --> apache:8080either :
nginx:80 --> fastcgi(php-fpm):8080

Answer 2

Does the Fastcgi process not have permission to list /usr/local/etc/ or read /usr/local/etc/php.ini?

Answer 3

about a passing question: how do you want it to work? With what parameters are you calling the mail() function? What mail server?

Answer 4

You have in clio.su/test.php at the very beginning Loaded Configuration File - (none). In your case, judging by the fact that the option is there and there, Configuration File (php.ini) Path - /usr/local/etcthe fastcgi process does not have enough rights to read the file /usr/local/etc/php.ini
It is also worth considering, depending on the OS. In Ubuntu, for example, separate PHP configs to run under Apache, Cli and CGI. those. in the /etc/php5/ folder there are cli/ apache/ cgi/ subfolders, each has its own php.ini and is loaded accordingly from that folder, how we launch php
In general, here Apache did not understand.