Nevermind, exact same issue already described in role::webperf::profiling_tools

# class httpd installs mpm_event by default, and once installed,
# it cannot easily be uninstalled. The xhgui profile installs
# libapache2-mod-php7.0 which in turn installs mpm_prefork, which
# fails if mpm_event is present. (T180761)
class { '::httpd::mpm':
    mpm => 'prefork'
}

Change 470106 had a related patch set uploaded (by Dzahn; owner: Dzahn):
[operations/puppet@production] icinga/alerting_host: ensure mpm_prefork is selected for httpd and php7.0

https://gerrit.wikimedia.org/r/470106

Change 470106 merged by Dzahn:
[operations/puppet@production] icinga/alerting_host: ensure mpm_prefork is selected for httpd and php7.0

https://gerrit.wikimedia.org/r/470106

I think we should stop using mod_php *anywhere*. We should really use php-fpm for anything that is not explicitly known not to work with fcgi (and I wonder, what that might be).

So for LAMP applications we might want to create a simple profile that installs:

• httpd
• php-fpm using the php module
• The entrypoint in the application if needed

And use it for all of them minus MediaWiki.

In T208108#4701107, @Joe wrote:

I think we should stop using mod_php *anywhere*. We should really use php-fpm for anything that is not explicitly known not to work with fcgi (and I wonder, what that might be).

+1 for php-fpm, it's a much better solution in my experience.

I made T208257 based on this comment.

Mentioned in SAL (#wikimedia-operations) [2022-12-07T21:02:10Z] <mutante> contint1002 a2dismod mpm_event - https://phabricator.wikimedia.org/T208108 Bug: T313832