• The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Apache fails to start: "Configuration failed"

eugenevdm

Regular Pleskian
I've just migrated 450 domains and 250 clients from Plesk SuSE 7.5.4 to Plesk 8.0 using Plesk Migration Manager.

For the most part the migration went smooth and I didn't notice any errors.

Now when I start Apache using Services management in Plesk I get:

ERROR: PleskFatalException

Unable to make action: Unable to manage service by websrvmng: websrvmng: Service httpd failed to start

0: /usr/local/psa/admin/plib/common_func.php3:169
psaerror(string 'Unable to make action: Unable to manage service by websrvmng: websrvmng: Service httpd failed to start')
1: /usr/local/psa/admin/htdocs/server/restart_services.php:30



When I examine the /etc/error_log file I all I get is: "Configuration failed".

Where can I look next? I have no idea what to do now.
 
I've just noticed that Apache on SuSE 9.1 Plesk 7.5.4 is vastly different from Apache on Plesk 8.0 FC4. For starters, the httpd.conf files on SuSE is in /etc/apache2 whereas the one on FC4 Plesk 8 is in /etc/httpd/conf.

Just skimming over the new one in /etc/httpd/conf it looks like a ton of stuff is missing, including what appears on the old system an very important include file which list all the Apache sites. Looks like I'm in for the long haul...

I tried setting the error log value to "debug" but I'm still just getting "Configuration Failed".

Can anyone help me to:
(1) create the httpd.conf file
(2) reload Plesk Apache

I'm quite desperate because I have 450 sites down.
 
The culprit turned out to be in what used to be "httpd.include". Inside this file, which on my FC4 64-bit is now:

/etc/httpd/conf.d/zz010_psa_httpd.conf

there was a refence to an include folder in one of my sites which relies on Tomcat and mod_rewrite. Something inside this file caused Apache to start working with this bizarre error.
 
Back
Top