You are viewing a plain text version of this content. The canonical link for it is here.
Posted to bugs@httpd.apache.org by bu...@apache.org on 2005/03/29 14:03:01 UTC
DO NOT REPLY [Bug 34221] New: -
Apache server probably falls into endless cpu-consuming loop.
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=34221>.
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=34221
Summary: Apache server probably falls into endless cpu-consuming
loop.
Product: Apache httpd-2.0
Version: 2.0.52
Platform: Other
OS/Version: Linux
Status: NEW
Severity: major
Priority: P1
Component: All
AssignedTo: bugs@httpd.apache.org
ReportedBy: gtsakiris@dolnet.gr
CC: gtsakiris@dolnet.gr
I have two identical servers (2 cpus, pIII @ 1000MHz, 1 GB each) running SuSE
Linux 9.1 (kernel 2.4) with 2.0.52 apache installed and php 4.3.11 (apache
module).
The computers are used as web servers with no other software running (like
database servers, etc). At rush hour the two machines serve about 300,000
requests both (the load is balanced equally).
At rush hour the load average of each computer reaches a maximum of 0.5-0.6.
Ar random time one of the two computers stops serving pages, all opened httpd
processes are busy (running) trying to consume cpu. The load average increases
quickly and in few seconds it approaches the number of the maximum server
processes (500 processes). At this conditions the machine responds very
slowly, you can hardly type commands in the shell, and no respond at all to
web requests. When this happens I reboot the computer and everything is coming
back to normal.
I checked the logs both apache's and system's but there is nothing suspicious,
just normal messages ending at the time of the stuck.
This can happen at any time, and at any of the two computers. It has occur
after a few hours of uptime or after 20 days since the last reboot. Anyway, as
an average we can accept that it happens once in a week.
I discussed this in the apache web server user's forums and many people said
that have the same problem, even when using apache without any modules (like
php). The do not have a decent explanation and the only thing they suggest is
to downgrade to apache 1.3 (where the problem exists no more).
I looked at the changelog of 2.0.53 but I can't see something relevant.
The symptoms make me think that all of the httpd processes fall into an cpu
consuming infinite-loop.
--
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