On 8/26/05, Udo Rader <udo.rader@xxxxxxxxxxxxxxx> wrote: > Yet of course I would like to know the exact time and circumstances when > such a situtation occurs. When reaching the memory limit, apache > produces log entries like this: > > -----------CUT----------- > [...] > ^GOut of memory (Needed 8164 bytes) > ^GOut of memory (Needed 8164 bytes) > ^GOut of memory (Needed 8164 bytes) > ^GOut of memory (Needed 8164 bytes) > ^GOut of memory (Needed 8164 bytes) > FATAL: erealloc(): Unable to allocate 76 bytes > -----------CUT----------- > > Now what I would like to have is a more informative logging message, > such as which URL caused the error. > > Is that possible? In general, no. Apache considers out of memory to be an unrecoverable error, and therefore doesn't try to protect against it in many different code paths. On the other hand, there is a new module called mod_log_forensice included with apache that may help. It can be used to find requests that were received but where no response was sent. These would probably match up with your out-of-memory crashes. 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
|