Resolved php-fpm.service from OS vendor shows failed state

[jola]

Server operating system version

AlmaLinux 9.5

Plesk version and microupdate number

18.0.66 #2

I'm setting up a new Plesk server and when I searched for potential problems I discovered that the php-fpm from the OS vendors gets a failed state:

systemctl | grep fpm
● php-fpm.service loaded failed failed The PHP FastCGI Process Manager
plesk-php83-fpm.service loaded active running The PHP 8.3.15 FastCGI Process Manager

The Plesk php-fpm83 is running well, but the OS fails. I do not think the OS is needed and I tried to disable the OS php-fpm by running:

systemctl disable php-fpm
systemctl stop php-fpm

However, the php-fpm service is still being started and fails when I reboot my server. Any ideas how to solve this?

 

[jola]

I have investigated this further and it seems as if the OS php-fpm service is started by Apache and nginx:

# systemctl list-dependencies --reverse php-fpm
php-fpm.service
● ├─httpd.service
● └─nginx.service
[root@cfd-online etc]# ls /etc/systemd/system/

This could be the reaseon why "systemctl disable php-fpm" does not help

Is this normal, I would expect apache/nginx to instead start the php-fpm version that I have active in Plesk (plesk-php83-fpm.service), and anyway the OS version fails, since Plesk has removed the pool I think:

# cat /etc/php-fpm.d/www.conf
; Default www-pool configuration has been disabled by Plesk Panel.
; Pool configuration was saved in '/etc/php-fpm.d/www.conf.saved_by_psa'.

Any hints on how to solve this failed state for the OS php-fpm service?

 

[Sebahat.hadzhi]

You are right, normally, Plesk does not use the OS PHP. Thus, the failed status shouldn't cause any issues. You should be able to remove it from Tools & Settings > Updates > Web Hosting dropdown > PHP from OS vendor.

 

[jola]

You are right, normally, Plesk does not use the OS PHP. Thus, the failed status shouldn't cause any issues. You should be able to remove it from Tools & Settings > Updates > Web Hosting dropdown > PHP from OS vendor.

This solved the problem and "systemctl --failed" now finally does not show a failed state for php-fpm. Thanks!