Restarting Apache - apachectl vs WHM

[ChrisHasenpflug]

Hello all,

I have made a change to my apache config file so that it will listen on only one IP address, instead of all 5 that I am given. The added code is "Listen xxx.xxx.xxx.130:80."

If I restart apache from the command line using /etc/httpd/etc/apachectl restart, all goes as expected and Apache restarts. However, if I use WHM or the WHM restart script (/scripts/restartsrv httpd) Apache fails to start and the error returned is "httpd has failed, please contact the sysadmin."

Well, I'm the sysadmin :D and I can make it start via apachectl, but not with the WHM script.

Any ideas??

 

[adept2003]

Just an idea, but the WHM apache restart might be using "apachectl restartssl" rather than simply "apachectl restart". Since you've only enabled port 80, that might explain the failure message.

Try using the "restartssl" via SSH and see what happens...

 

[RandyO]

httpd startssl

 

[adept2003]

httpd startssl

ah yes, you're right. Just the way my brain works.

Use "apachectl startssl" rather than "restartssl".

 

[ChrisHasenpflug]

Good call guys. That seems to be the case.

How can I setup WHM to just do start instead of startssl since we're not using SSL? I guess I could give the Listen an SSL port to make it happy, possibly?

 

[PWSowner]

Pretty much have to because you can't change what the WHM functions do. Most of them are hard coded functions.

 

[ChrisHasenpflug]

Have added "Listen xxx.xxx.xxx.130:443" and still no go for startssl. Ideas?

 

[ChrisHasenpflug]

Any ideas out there as to why it still won't start if I give it the SSL port??

If we hack the restartsrv_httpd script will it get overwritten in updates?? Will rebuilding Apache w/o mod_ssl keep it from doing startssl??