httpd-bugs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 27138] - httpd processes gets 100% of CPU, apache stop/kill don't work
Date Tue, 08 Mar 2005 10:18:33 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=27138>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=27138





------- Additional Comments From nelson.menezes@city-link.co.uk  2005-03-08 11:18 -------
(In reply to comment #10)
> I still have the problem in 2.0.53. We are just monitoring the ill behaviour 
> and killing the slave daemons when needed (they are no longer under control of 
> master httpd process anyway). We live like that but forgot about solving this 
> issue... Not sure if it comes from Apache itself or PHP but we cannot build a 
> useful test config without php...
> 
> Michel


I've trawled the net for answers; apparently this behaviour can also come from a
misbehaving PHP script.

The best way to track it down might be to set "ExtendedStatus On" and check the
offending processes in /server-status/. Also, "strace -p <PID>" and "lsof -p
<PID>" could help find any open files that are being written/read/failed in a cycle.

I didn't find anything in my case (seems to be internal to the version of Apache
we're running), but those methods should allow you to track down the cause of
the problem, if it's a script.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org


Mime
View raw message