On 4/23/07, Martijn <sweetwatergeek@xxxxxxxxxxxxxx> wrote:
[Mon Apr 23 12:41:40 2007] [info] [client 12.34.56.78] send mmap timed out and, more frequently: [Mon Apr 23 12:41:40 2007] [info] [client 12.34.56.78] (32)Broken pipe: client stopped connection before send mmap completed This usually isn't a problem and it never worried me (it is, after all, marked as "info"), until a number of the former errors, followed by a number of the latter errors (about 30 of each) caused the server to crash. The errors were all related to the same IP address and, as far as I can see, this belongs to a genuine user. I did, however, find in the access log files that their results returned httpd status '206' (partial content) and the number of bytes on large files, was always a nice rounded number, like 32768 (which is 2^15). It suggests that the problem has to do with the user downloading only parts of larger files (pdfs/gifs) and, I would guess, leaving an httpd process waiting for it to finish? At least the number of httpd processes had reached its maximum (which is why the server crashed).
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. 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
|