www-apache-bugdb mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Zdeeck Kudrle <zde...@atc.cz>
Subject general/4041: Apache doesn't answer when in huge traffic
Date Thu, 11 Mar 1999 14:53:57 GMT

>Number:         4041
>Category:       general
>Synopsis:       Apache doesn't answer when in huge traffic
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    apache
>State:          open
>Class:          sw-bug
>Submitter-Id:   apache
>Arrival-Date:   Thu Mar 11 08:10:01 PST 1999
>Originator:     zdeeck@atc.cz
>Release:        1.3.4
Linux kernels 2.2.1 , 2.2.2. Double Pentium II 400Mhz, gcc , PHP 3, MySQL
Installation RedHat 5.2
We are running huge database. After installing new kernels , everything seemed
to be OK, but in critical hours, when the traffic is very high, apache simply
'fell' down. He(?:) didn't answer, but there were about 80 httpds running, kernel
said 'waiting'. We tried to telnet on port 80, but 'connection timed out'.
MaxAllowed was 256, but no other apaches were forked. In kernel 2.0.36 is
everything OK. (or should I report this to kernel-bugs?)
Sorry for my English... :(
Eh, we can't provide you repeatment, 'cos we are quite small firm with  lot
of customers providing them free-email. Look at: http://www.email.cz
And this is very critical section of our business.
It seems to me, that kernel doesn't want to fork another httpd. _Very_ strange.
[In order for any reply to be added to the PR database, ]
[you need to include <apbugs@Apache.Org> in the Cc line ]
[and leave the subject line UNCHANGED.  This is not done]
[automatically because of the potential for mail loops. ]
[If you do not include this Cc, your reply may be ig-   ]
[nored unless you are responding to an explicit request ]
[from a developer.                                      ]
[Reply only with text; DO NOT SEND ATTACHMENTS!         ]

View raw message