On 4/23/07, Martijn <sweetwatergeek@xxxxxxxxxxxxxx> wrote:
> In all likelihood, those messages are only tangentially related to > your problem. They simply indicate that the client end of the > connection disappeared, which is a perfectly normal thing for a busy > webserver. The 206 responses are probably caused by a very impolite > download accelerator making multiple overlapping requests. When it has > received what it wants, it drops all the requests, resulting in the > error messages. > > But then you say the server "crashed". What exactly does that mean? > Did it dump core? Did it simply get very slow? It is not normal for a > server to "crash" when it hits MaxClients. You need to be more > detailed about what actually happened. Thank you for your reply. It did not just reach MaxClients, but the number of httpd processes stayed at this maximum for hours, until someone (not me) finally restarted apache. (Of course, this problem happened on Sunday night, so I wasn't there to see what really happened. Or to sort out things myself.) Both the access_log file and the error_log file weren't written to from the time the aforementioned mmap-info messages appeared until apache was restarted hours later. There is, indeed, no sign that apache really 'crashed', so it probably, didn't but the effect was the same. People who were awake at that time told me that they couldn't reach the site, but the server did ping.
Was this just a denial-of-service attack? Did you use a tool like netstat to identify the client connections and track down the origin? If apache was really "frozen" (not serving a connection and not answering new connections, even after the Timeout has expired), then you should attach to some process to get a backtrace: http://httpd.apache.org/dev/debugging.html#backtrace Joshua. --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|