• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

PHP FPM service failed for domain

Chris1

Regular Pleskian
Hello,

We have a client that started receiving a "503 Service Unavailable" error on their website. After taking a look at the logs I found the following.

/var/log/plesk-php56-fpm/error.log
Code:
[25-May-2016 03:37:15] NOTICE: Terminating ...
[25-May-2016 03:37:15] NOTICE: exiting, bye-bye!

/var/www/vhosts/example.com/logs/error_log
Code:
[Wed May 25 03:37:27.279428 2016] [proxy:error] [pid 10551:tid 139733187417856] (2)No such file or directory: AH02454: FCGI: attempt to connect to Unix domain socket /var/www/vhosts/system/example.com/php-fpm.sock (*) failed
This entry kept repeating hours. I ended up re-syncing them to a service plan, the problem then went away and the website became available.

I'm not sure if these two log entries are related but they happened very close to each other. What could cause the plesk-php56-fpm error log to give the above output?
 
Hmmm I don't think one can conclude that just because the server is a VPS that it is due to a lack of resources.

In this specific case there are no resource related issues either at the node, VPS or user level.
 
Back
Top