Usually, httpd runs as a pool of processes. It does not appear that the application has gotten that far, but you cannot be sure unless you follow my recommendation. I'll highlight it, once more, because you've missed it twice now.
Quote:
Originally Posted by jggimi
...Run top(1) from another console while httpd is started and inoperative. Filter for httpd, and examine any httpd processes shown. Is one or more CPU bound? If not, what is/are the process(es) waiting for?
|
It is likely that this won't show anything of value, of course. But we will never know unless you try it and report.
Should you bother to read
httpd(8), you will see that there are a few things you could try that would be easier than posting here.
Example:
-X. Does it produce any console output? If there is an error, it might show here.
Example:
-T/-t. Do both produce confirmation of a valid httpd.conf file?
Example;
-V/-v. Do both produce valid output?
All this time, httpd just might have been reporting problems in /var/www/logs. It is possible that the reason for the hang is in /var/www/logs/error_log.