Note that there are some explanatory texts on larger screens.

plurals
  1. POnginx + php-fpm + pidora(fedora) on raspberry
    text
    copied!<p>I would like to make the configuration what mentioned in the subject. If I start the nginx I see this error message in /var/log/nginx/error.log</p> <p>*<em>1 connect() to unix:127.0.0.1:9000 failed (2: No such file or directory) while connecting to upstream</em></p> <p>I tried to set with socket. I get the following error</p> <p><em>unix:/var/run/php5-fpm.sock failed (2: No such file or directory)</em></p> <p>Seems the nginx need a file or not the path is bad. Exactly I not understand how can I solve it,</p> <p>Here is my nginx settings</p> <pre><code>location ~ \.php$ { try_files $uri =404; fastcgi_pass unix:127.0.0.1:9000; fastcgi_index index.php; fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name; fastcgi_split_path_info ^(.+\.php)(/.+)$; include /etc/nginx/fastcgi_params; } </code></pre> <p>when I tried with socket I used this ( fastcgi_pass unix:/var/run/php-fpm/php5-fpm.sock;)</p> <p>I change in /etc/php-fpm/www.conf only the "listen" attribute depends on fastcgi_pass.</p> <p>Anyone has an idea how can I solve it?</p> <p><strong>Update:</strong> I changed fastcgi_pass unix:127.0.0.1:9000 to fastcgi_pass 127.0.0.1:9000 In this case I got the following error</p> <pre><code>*1 connect() failed (111: Connection refused) while connecting to upstream, </code></pre> <p>And the following messages when I started the php-fpm</p> <pre><code>Oct 17 09:30:31 raspi php-fpm[6605]: [17-Oct-2013 09:30:31] ALERT: [pool www] user has not been defined Oct 17 09:30:31 raspi php-fpm[6605]: [17-Oct-2013 09:30:31] ERROR: failed to post process the configuration Oct 17 09:30:31 raspi php-fpm[6605]: [17-Oct-2013 09:30:31] ERROR: FPM initialization failed Oct 17 09:30:31 raspi systemd[1]: php-fpm.service: main process exited, code=exited, status=78/n/a Oct 17 09:30:31 raspi systemd[1]: Unit php-fpm.service entered failed state </code></pre>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload