Question

Error - php7.0-fpm.sock failed [NGINX - Ubuntu Server]

Posted September 5, 2018 8.4k views
Nginx PHP Ubuntu 16.04

Respected,
I’m facing php7.0-fpm.sock failed error from a long time on Ubuntu 16.04.5 LTS (NGINX). Six websites are active on this server.

Kindly check below detailed logs.

php7.0-fpm.log:

2018/09/04 06:25:04 [error] 18209#18209: *362673 connect() to unix:/run/php/php7.0-fpm.sock failed (11: Resource temporarily unavailable) while connecting to upstream, client: 162.158.126.43, server: [domainnamehidden].com, request: “GET / HTTP/1.1”, upstream: “fastcgi://unix:/run/php/php7.0-fpm.sock:”, host: “[domainnamehidden].com”

error.log:

[02-Sep-2018 06:25:02] NOTICE: error log file re-opened
[04-Sep-2018 09:19:40] NOTICE: Terminating …
[04-Sep-2018 09:19:41] NOTICE: exiting, bye-bye!
[04-Sep-2018 09:19:57] NOTICE: configuration file /etc/php/7.0/fpm/php-fpm.conf test is successful
[04-Sep-2018 09:19:57] NOTICE: fpm is running, pid 1745
[04-Sep-2018 09:19:57] NOTICE: ready to handle connections
[04-Sep-2018 09:19:57] NOTICE: systemd monitor interval set to 10000ms
[04-Sep-2018 19:53:56] WARNING: [pool www] server reached pm.max_children setting (5), consider raising it

If reboot the server then websites are working for a limited period (Approximately 5-7 hours). Another fix, I need to restart the PHP FPM through the following command: sudo service php7.0-fpm restart

Please help. Thank you!

Add a comment
D1ed46757d5c4ac9e2e30ff395d2df8aa35aa57b
By:
chinmayrajyaguru
Add a comment
1 comment
  • worm September 16, 2019
    Reply Report

    I had this same problem and seemed to have fixed it.

    Details:

    • Running
      • Ubuntu 19.04
      • php7.2
    • Checked the status of both nginx and php-fpm. Both were running fine.
    • error log was throwing a “502 Bad Gateway”

    Like chinmayrajyaguru, I changed unix:/run/php/php7.0-fpm.sock to unix:/var/run/php/php7.0-fpm.sock. However, I changed /etc/php/7.2/fpm/pool.d/www.conf.

    Upon doing that (and without restarting nginx or php-fpm), I refreshed the page which was displaying the 502 error and it immediately went back to normal.

    To the best of my knowledge, you need to make sure the unix socket path is the same in your nginx site config and the php-fpm pool config.

    Hope this helps anyone with this issue. I will post again if this isn’t a permanent fix.

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

2 answers
chinmayrajyaguru September 5, 2018

I have changed root from unix:/run/php/php7.0-fpm.sock to unix:/var/run/php/php7.0-fpm.sock in Nginx Conf and Sites-available files for the testing purpose. I’ll update soon if the error appears again.

Reply Report
kgudger December 17, 2019

Here’s a summary of what fixed this error:
In /etc/php/7.0/fpm/pool.d/www.conf change the lines as below:
listen = /var/run/php/php7.0-fpm.sock
In /etc/nginx/sites-available/yoursite.conf:
Under “location ~ .php$ {”
change the line to:
fastcgipass unix:/var/run/php/php7.0-fpm.sock;
Restart nginx: sudo service nginx restart
Everything should then work.

Reply Report
Submit an Answer

Related

Looking for something else?

Ask a new question Search for more help