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 13661] - Apache cannot not handle dynamic IP reallocation
Date Tue, 19 Nov 2002 18:27:46 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13661>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13661

Apache cannot not handle dynamic IP reallocation





------- Additional Comments From ivelin@apache.org  2002-11-19 18:27 -------
Unfortunately stopping all AntiVirus services did not help.

Here is additionaly analisys from one of our team members:

Symptoms:
	CPU goes from a normal load to 100% and stays there.  Usually the 
system stops responding to requests.  Apache stops logging events, sometimes 
after logging an Out of Threads message to the error.log, sometimes not.  
Process lists indicate that Apache is taking up all CPU resources.  Process 
monitoring indicates that the actual child process is taking the CPU.  If the 
log contains an Out of Threads message, usually the second web server will go 
down with the same symptoms within 15 minutes or so.  If there is no OOT 
message, usually this will not happen.

Info:
	Memory seems steady.  I/O seems OK as well.  No pattern in when these 
occur.  Slightly more likely during the week then the weekend.  HTML requests 
right before this happens are normal requests.  The service will rarely respond 
to NET STOP commands when in this state.  Reboots correct this problem.  Anti-
Virus has been stopped on the system.  After stopping AV on 11-12, the problem 
happened several hours later, then not again until 11-18, the longest period 
yet.  Since then, the Patrol has reported 8 various CPU pegs, including the 
first one on 11-18.  The Web boxes are Win2K SP2.  Apache is 2.0.42.  We are 
not able to duplicate this problem in the lab under stress conditions.

Speculation:
	I believe this may be two linked but still separate problems, one, the 
OOT problem, the other, the "stoplog" problem.  I say this because with an OOT, 
if threads are not released, Apache will not accept connections, and there's 
nothing to put in the logs.  Also, this issue somehow crosses to the other web, 
which soon goes down.  On the other hand, the stoplog problem never crosses to 
another server, and often the server continues to serve requests after the CPU 
peg.  These requests are not logged, however.  I also believe this to be a non-
RSM related problem as I feel we would be seeing more regular occurrences or 
duplication in the lab.  Possibly a malformed HTML request.

Conclusion:
	Stopping AV did not fix this problem. 

Thanks,
Andrew

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


Mime
View raw message