RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:

httpd should be allowed to run on its own, without php-fpm. Unfortunately, when both httpd and php-fpm are installed, this is not possible, php-fpm is forcefully started even if its service is disabled.

Version-Release number of selected component (if applicable):

httpd-2.4.37
php-fpm-7.2.11

How reproducible:

always

Steps to Reproduce:

1. dnf -y install httpd php-fpm
2. systemctl disable php-fpm
3. rm -rf /etc/php-fpm.d/*.conf
4. systemctl enable httpd
5. reboot
6. systemctl status

Actual results:

systemctl status reports as degraded because php-fpm is forcefully started.

Expected results:

php-fpm should not be forced to start when the service is disabled.

Additional info:

Apparently, the php-fpm package adds the following unit file:

/usr/lib/systemd/system/httpd.service.d/php-fpm.conf

with the following contents:

[Unit]
Wants=php-fpm.service

As a result, the httpd service will force-start the php-fpm service.

Thank you.

You can use "systemctl mask php-fpm" if you want to forcibly disable php-fpm.service entirely, but the default behaviour you describe is by design and is necessary to ensure that PHP is usable by default from httpd. I don't think there is any other way we can arrange the defaults, sorry.