• 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!
  • 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.

Issue watchdog on php-fpm turned off

BrinsleyP

Regular Pleskian
Server operating system version
AlmaLinux 8.6
Plesk version and microupdate number
18.0.44 Update #2
Hello...
In this server the watchdog monitoring all services and PHP-FPM (FastCGI Process Manager) cant be runs fine.
Screenshot 2022-06-15 103211.png
I chech in some tools like a services, plesk repair and troubleshooter

Screenshot 2022-06-15 103245.png

Screenshot 2022-06-15 103406.png


Screenshot 2022-06-15 103449.png

So how to fix this ? In server i have some sites in fastcgi, phpfpm and all php version running OK.
 
I guess you've got a mail like this: "The PHP-FPM (FastCGI Process Manager) service on host <host> has been released from monitoring"

There used to be a support article about this issue, but it's no longer visible.
 
i try force "start" but without success

[root@server ~]# /usr/local/psa/admin/bin/phpinimng --type fpm --start --service-name php-fpm
Failed to start php-fpm.service: Unit php-fpm.service not found.
Failed to start php-fpm service
[root@server ~]#

But services apear on - see prints.
 
It's the OS PHP-FPM handler that is turned off. The reason is that no website is using that PHP-FPM handler.

This is an old article from web.archive.org:

The link below is a UserVoice request to add every PHP-handler to watchdog:

I can't find the current state of the issue.

Don't hesitate to create a report if you want an answer from the developers:
 
Back
Top