Checkmk Raw's Underlying Apache - Prefork vs. Worker

[svieth (Scott Vieth)]

CMK version: 2.1.0p31
OS version:CentOS 7

Error message:

I’m looking at doing an update to my checkmk installation. Our team is currently wanting me to switch from the mod_cgi module however to the mod_cgid module, which is much improved in terms of performance. However, upon giving things a closer look, I see why we’re still using mod_cgi … we’re using Apache in prefork mode as opposed to worker mode. Looks like we always have.

So my question here is simply to ask if checkmk requires Apache to be in prefork mode, or if I need to go down the rabbit hole of attempting to upgrade it to worker mode and then seeing if the mod_cgid module will work successfully with checkmk.

Thanks!

Output of “cmk --debug -vvn hostname”: (If it is a problem with checks or plugins)

[robin.gierse]

If you are looking at the system apache and not the site apache, you can just go ahead and change whatever you like.

If you are suggesting, that we change the site apache, you might want to post that idea here: https://features.checkmk.com/

[svieth (Scott Vieth)]

Not as much about asking them to change it, but more to get clarification. Does checkmk (for the site apache) require prefork mode, or can it be switched out to work in worker or event mode?

[robin.gierse]

I do not think we require prefork mode on the site apache. But for one thing, if you have a support contract, any change here will void your support. And even, if you are using CRE, I am uncertain if possible side effects are worth the effort of changing it and the potential improvements.