ServerBuddies Support Blog

Building the Apache Configuration File in WHM

The build process begins by distilling and recording Apache’s current configuration. The build time options you configured during the EasyApache setup are used to begin building the configuration.

Option modules such as mod_security are installed, and their corresponding modifications are made to the new Apache configuration file.
A new, assumedly valid Apache configuration file will exist in the configuration directory.
Directives added to the final Apache configuration file as defaults have been removed at this point.
No VirtualHost entries exist in the configuration file at this point.

The new configuration is distilled in much the same way as before; however, this time the configuration is used as the basis for creating the server’s main Apache configuration template.
New directives and values are stored.

Any directives and values held over from the previous configuration will retain their values from that configuration.
The combination of the main template and data stores will be the basis for regenerating the final configuration file.

Finally, the new Apache configuration file is generated from the template and data stores and checked for syntactical correctness.
If the new file passes the test, the process is complete.
If the file fails the syntax check, the previous Apache configuration is restored.

Reference: http://cpanel.net

Problems building Apache with your custom modules

If you have problems building Apache with your custom modules, and you are unable to troubleshoot the problem, run

This builds Apache and PHP without any custom modules.

From WHM

Access the WHM equivalent found in EasyApache’s Help section.

In order to remove a custom module from the server, simply delete the files you have created when you issued the above commands. The module will be removed from all future builds and the EasyApache interface.

Reference: http://cpanel.net/