After update to v1.9.1 php-fpm error: "Sock failed (2: No such file or directory)"

andrey.druz · February 7, 2025, 10:42am

Hello,

I have the number of servers which migrated to new version (Hestia Control Panel v1.9.1).
All servers have same problem and problem happens on all sites.
Error happens 10–20 times a day on every site.
Error started on 04/02/2025.

Server data:

Ubuntu 22.04
Nginx + php-fpm

Error example:

2025/02/07 10:21:29 [crit] 2227399#2227399: *514560 connect() to unix:/run/php/php8.1-fpm-xxxxxxxxxx.com.sock failed (2: No such file or directory) while connecting to upstream, client: xxx.xxx.xxx.xxx, server: xxxxxxxxxxxxxxx.com, request: "HEAD /xxxxxxxxxxxxxxxxxxxxx HTTP/2.0", upstream: "fastcgi://unix:/run/php/php8.1-fpm-xxxxxxxxxxxxxx.com.sock:", host: "xxxxxxxxxxxxxxxxx.com"

Please let me know with system settings changed so I will try to play with it and change it back in order to resolve the errors.

eris · February 7, 2025, 11:02am

We have not changed anything with websites templates.

So that is strange…

When does it happens randomly?
Or all sites on the same time?

andrey.druz · February 7, 2025, 11:25am

Hello,

Attached screenshots of logs from different sites on same server.
Looks like it in different times.

But doing these times I see in syslog, and it’s happen every 10-30 min

Feb  7 10:31:38 ln12 systemd[1]: Stopping The PHP 5.6 FastCGI Process Manager...
Feb  7 10:31:38 ln12 systemd[1]: php5.6-fpm.service: Deactivated successfully.
Feb  7 10:31:38 ln12 systemd[1]: Stopped The PHP 5.6 FastCGI Process Manager.
Feb  7 10:31:38 ln12 systemd[1]: Stopping The PHP 7.0 FastCGI Process Manager...
Feb  7 10:31:38 ln12 systemd[1]: php7.0-fpm.service: Deactivated successfully.
Feb  7 10:31:38 ln12 systemd[1]: Stopped The PHP 7.0 FastCGI Process Manager.
Feb  7 10:31:38 ln12 systemd[1]: Stopping The PHP 7.1 FastCGI Process Manager...
Feb  7 10:31:38 ln12 systemd[1]: php7.1-fpm.service: Deactivated successfully.
Feb  7 10:31:38 ln12 systemd[1]: Stopped The PHP 7.1 FastCGI Process Manager.
Feb  7 10:31:38 ln12 systemd[1]: Stopping The PHP 7.2 FastCGI Process Manager...
Feb  7 10:31:38 ln12 systemd[1]: php7.2-fpm.service: Deactivated successfully.
Feb  7 10:31:38 ln12 systemd[1]: Stopped The PHP 7.2 FastCGI Process Manager.
Feb  7 10:31:38 ln12 systemd[1]: Stopping The PHP 7.3 FastCGI Process Manager...
Feb  7 10:31:38 ln12 systemd[1]: php7.3-fpm.service: Deactivated successfully.
Feb  7 10:31:38 ln12 systemd[1]: Stopped The PHP 7.3 FastCGI Process Manager.
Feb  7 10:31:38 ln12 systemd[1]: Stopping The PHP 7.4 FastCGI Process Manager...
Feb  7 10:31:38 ln12 systemd[1]: php7.4-fpm.service: Deactivated successfully.
Feb  7 10:31:38 ln12 systemd[1]: Stopped The PHP 7.4 FastCGI Process Manager.
Feb  7 10:31:38 ln12 systemd[1]: php7.4-fpm.service: Consumed 15.005s CPU time.
Feb  7 10:31:38 ln12 systemd[1]: Stopping The PHP 8.0 FastCGI Process Manager...
Feb  7 10:31:38 ln12 systemd[1]: php8.0-fpm.service: Deactivated successfully.
Feb  7 10:31:38 ln12 systemd[1]: Stopped The PHP 8.0 FastCGI Process Manager.
Feb  7 10:31:38 ln12 systemd[1]: Stopping The PHP 8.1 FastCGI Process Manager...
Feb  7 10:31:38 ln12 systemd[1]: php8.1-fpm.service: Deactivated successfully.
Feb  7 10:31:38 ln12 systemd[1]: Stopped The PHP 8.1 FastCGI Process Manager.
Feb  7 10:31:38 ln12 systemd[1]: php8.1-fpm.service: Consumed 33.928s CPU time.
Feb  7 10:31:38 ln12 systemd[1]: Stopping The PHP 8.2 FastCGI Process Manager...
Feb  7 10:31:38 ln12 systemd[1]: php8.2-fpm.service: Deactivated successfully.
Feb  7 10:31:38 ln12 systemd[1]: Stopped The PHP 8.2 FastCGI Process Manager.
Feb  7 10:31:38 ln12 systemd[1]: php8.2-fpm.service: Consumed 9.337s CPU time.
Feb  7 10:31:38 ln12 systemd[1]: Stopping The PHP 8.3 FastCGI Process Manager...
Feb  7 10:31:38 ln12 systemd[1]: php8.3-fpm.service: Deactivated successfully.
Feb  7 10:31:38 ln12 systemd[1]: Stopped The PHP 8.3 FastCGI Process Manager.
Feb  7 10:31:39 ln12 systemd[1]: Starting The PHP 5.6 FastCGI Process Manager...
Feb  7 10:31:39 ln12 systemd[1]: Starting The PHP 5.6 FastCGI Process Manager...
Feb  7 10:31:39 ln12 systemd[1]: Started The PHP 5.6 FastCGI Process Manager.
Feb  7 10:31:39 ln12 systemd[1]: Starting The PHP 7.0 FastCGI Process Manager...
Feb  7 10:31:39 ln12 systemd[1]: Started The PHP 7.0 FastCGI Process Manager.
Feb  7 10:31:39 ln12 systemd[1]: Starting The PHP 7.1 FastCGI Process Manager...
Feb  7 10:31:39 ln12 systemd[1]: Started The PHP 7.1 FastCGI Process Manager.
Feb  7 10:31:39 ln12 systemd[1]: Starting The PHP 7.2 FastCGI Process Manager...
Feb  7 10:31:39 ln12 systemd[1]: Started The PHP 7.2 FastCGI Process Manager.
Feb  7 10:31:39 ln12 systemd[1]: Starting The PHP 7.3 FastCGI Process Manager...
Feb  7 10:31:39 ln12 systemd[1]: Started The PHP 7.3 FastCGI Process Manager.
Feb  7 10:31:39 ln12 systemd[1]: Starting The PHP 7.4 FastCGI Process Manager...
Feb  7 10:31:39 ln12 systemd[1]: Started The PHP 7.4 FastCGI Process Manager.
Feb  7 10:31:39 ln12 systemd[1]: Starting The PHP 8.0 FastCGI Process Manager...
Feb  7 10:31:39 ln12 systemd[1]: Started The PHP 8.0 FastCGI Process Manager.
Feb  7 10:31:39 ln12 systemd[1]: Starting The PHP 8.1 FastCGI Process Manager...
Feb  7 10:31:39 ln12 systemd[1]: Started The PHP 8.1 FastCGI Process Manager.
Feb  7 10:31:39 ln12 systemd[1]: Starting The PHP 8.2 FastCGI Process Manager...
Feb  7 10:31:39 ln12 systemd[1]: Started The PHP 8.2 FastCGI Process Manager.
Feb  7 10:31:39 ln12 systemd[1]: Starting The PHP 8.3 FastCGI Process Manager...
Feb  7 10:31:39 ln12 systemd[1]: Started The PHP 8.3 FastCGI Process Manager.

andrey.druz · February 7, 2025, 12:55pm

Closing issue. Related to monit monitoring. Was using this code and now will need to change it.

check process php7-fpm with pidfile /run/php/php7.4-fpm.pid
    start program = "/usr/local/hestia/bin/v-start-service php-fpm"  with timeou$
    stop program = "/usr/local/hestia/bin/v-stop-service php-fpm"
if failed host 127.0.0.1 port 9000 type tcp for 3 cycles then restart

eris · February 7, 2025, 1:01pm

Yes that would explain in your probally want to monitor

/run/php/phpx.x-dummy.conf

and replace x.x with the releated php version

eris · February 7, 2025, 1:12pm

www.conf wil only monitor the “system” default php used for phpmyadmin
dummy file is always active for each php version

system · March 9, 2025, 1:13pm

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.