2nd April 2009
|
|
More noise than signal
|
|
Join Date: May 2008
Location: USA
Posts: 7,984
|
|
Above, I said:
Quote:
Originally Posted by jggimi
- Patch #4 is for httpd. It does not appear to directly apply, as it is related to mod_proxy, which is not enabled by default in /var/www/conf/httpd.conf. Examine the file, and confirm that mod_proxy is commented out. Please consider applying the patch, as well.
|
It apparently did not fix your problem, as expected. But I'd also written:
Quote:
Since this appears to be an httpd process hang, and not an OS hang, perhaps you can gather more diagnostic information: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?
Diagnostics may be obtained from tools like gdb(1), systrace(1), and ktrace(1), but you do not appear to have the applicable skills or knowledge required to deploy them. We are left with empirical examination using tools like top, systat(1), and vmstat(1).
|
Last edited by jggimi; 2nd April 2009 at 12:54 PM.
|