Are you getting the httpd configuration error: No MPM loaded in your server? We’ll help you.

The most common reason for this error is missing MPM, which binds network ports to the server and processes web requests.

At Bobcares, we often get requests to fix Apache related errors as a part of our Server Management Services.

Today, let’s analyze the cause and see how our Support Team fixes the httpd error.

Why does the server show httpd configuration error?

Bad configurations in webservers always end up in errors. One such error is httpd configuration error: No MPM loaded.

Here the web server goes down and all websites fail to load. This badly affects the business and customers often approach us for a quick resolution.

In most of the cases, the error occurs after an EasyApache4 update. The error occurs due to missing MPM.

Multi-Processing Modules or MPMs in Apache binds the network ports to the machine, accepts and handles requests. For better scalability, stability, and compatibility, Apache makes use of MPMs like worker, event, prefork, etc. The choice of the MPM depends largely on the type of apps and websites running on the server too.

However, when these modules are not available in the server, it ends up in the httpd error.

How we fix httpd configuration error: No MPM loaded?

Recently one of our customers approached us with an httpd error. The error message appeared as,

AH00534: httpd: Configuration error: No MPM loaded

In this case, httpd service was down after an EasyApache4 update. He tried to restart the service several times, without any luck.

Let’s see how our Support Engineers fixed this error.

We tried to restart the service, but the same error showed up. Then we checked the logs. There we found that it occurred due to the missing shared object “.so” files or broken modules.

In this case, the error was due to missing libmodsecurity.so file. This file was the compiled library file for the ModSecurity module. Therefore, it was not loading properly.

Here the problem was with the package repository. So, we created a folder with the name repo under /tmp. Then we took the backup of the existing repo list to the newly created folder and then deleted the originals.

mkdir /tmp/repo
mv /etc/yum.repos.d/*.repo /tmp/repo
rm /etc/yum.repos.d/*.repo

Secondly, we cleaned the repo and updated it again.

yum clean all
yum update y

This fixed the problem and Apache restarted successfully.

[Having trouble in fixing webserver errors? – We’ll fix it for you.]

Conclusion

In short, the httpd configuration error: No MPM loaded occurs due to missing modules or corrupted configuration. Today, we saw how our Support Engineers fixed the error in a CentOS 7 server.