• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

apache not starting

T

tezhit

Guest
Hi,

We are having problem in starting apache. Apache service is stopped while restarting it from plesk service management.
Now while starting it agin it is showing me some error..

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

please help me out of this problem

Thank you
 
There could be a number of reasons for this.

have a look in in the various files you'll fine in /var/log/httpd/ (e.g. error.log) to see if anything obvious is shown (most "warning"s are not bad. Only actual errors are likely to be problems). Also look in /var/log/messages for anything in there.

Or simply try restaring apache from the command line (e.g. "service httpd restart" if you have red hat/centos type linux) in case something obvious is shown there.

Faris.
 
Thank you so much Faris

I used service httpd restart
and it showed me errors in vhost.conf file. It was comments in file. I removed comments and it worked fine for me.
Now all sites are on.
but I cannot understand why changes from vhost.conf file was not applying earlier.
I restarted apache server before this also from control panel.
 
Confusing things like this can happen from time to time. There is almost always a rational explanation but it is often hard to figure out :)
 
actually.....I think I may know.

Restarting Apache (from anywhere) does not make it look at the vhosts files. You need to use websrvmngr -u -a to do this (then restart apache).

However, if you add a new domain, or do certain other things then this command gets run by Plesk itself. So that may be why you didn't see the problem until now.

Faris.
 
Back
Top