After uninstalling certain plugins like xVarnish or cPnginx, you may experience issues with the Apache (httpd) service failing to start. This typically happens when the software does not clean up its configuration files properly.
Symptoms:
- Apache service fails to restart.
- Errors referencing missing or invalid modules (e.g.,
mod_xvarnish,mod_cpnginx).
Solution:
You can manually disable the broken module by renaming its configuration file. This prevents Apache from trying to load the module.
Example (xVarnish):
mv /etc/apache2/conf.modules.d/999_mod_xvarnish.conf /etc/apache2/conf.modules.d/999_mod_xvarnish.conf.bkpGeneral Rule:
If the issue is caused by a different module (e.g., cPnginx), adjust the file name accordingly:
mv /etc/apache2/conf.modules.d/999_mod_cpnginx.conf /etc/apache2/conf.modules.d/999_mod_cpnginx.conf.bkpAfter Making Changes:
- Test Apache Configuration:
apachectl configtest - Restart Apache:
systemctl restart httpd
This method helps recover Apache functionality without needing to fully reinstall affected plugins.