I have no idea why, if I do service httpd restart it just goes back to prompt:root@host [/home3/backup/2013-08-25/accounts]# service httpd start httpd (pid 29767) already runningroot@host [/home3/backup/2013-08-25/accounts]# service httpd stoproot@host [/home3/backup/2013-08-25/accounts]# service httpd restartroot@host [/home3/backup/2013-08-25/accounts]# service httpd statusNothing! And after a while it reports that apache is not running. No error message whatsoever.However WHM and CPanel run though.root@host [/home3/backup/2013-08-25/accounts]# service httpd configtestSyntax OKroot@host [/home3/backup/2013-08-25/accounts]#Notice that it used to work fine.I got something:root@host [/home3/backup/2013-08-25/accounts]# service httpd statusTerminatedroot@host [/home3/backup/2013-08-25/accounts]# 403 Forbidden   Access is forbidden to the requested page:     localhost/whm-server-status (port 80)   Please forward this error screen to localhost's [1]WebMaster.     __________________________________________________________________    Apache/2.2.23 (Unix) mod_ssl/2.2.23 OpenSSL/1.0.0-fips    mod_auth_passthrough/2.1 mod_bwlimited/1.4 FrontPage/5.0.2.2635    Server at localhost Port 80References   1. mailto:webmaster@buildingsuperteams.com?subject=Error%20message%20[403]%20403%20Forbidden%20for%20localhost/whm-server-status%20port%2080%20on%20Thursday,%2029-Aug-2013%2023:43:54%20MDTforbidden what?Restarting the whole server works. Restarting apache doesn't/
httpd server simply doesn't want to run anymore
apache httpd;cpanel
As Mauro suggests - check the httpd/apache logs - typically under /var/log.  Their locations can vary; to find them, try:find /var/log -name '*http*' -printfind /var/log -name '*apache*' -printYou can also check the config - a typical cause of this type of problem:service httpd configtestIf a reboot of the server restarts httpd, but the service commands do not, that suggests the problem could be that httpd is started at boot a different way (try chkconfig to find out), or some runtime state is leading to the problem (such as a server running low on memory due to too many processes using too much memory).  To check for a possible memory-related cause, try dmesg and see if the OOM killer ran.