In my experiences it something other than apache causing the Out of memory error. Does it happen a certain time of day? If its system related it may be helpful to log whats happening just before the error. What OS do you use? ----- Original Message ----- From: "Mario Passaggio" <[EMAIL PROTECTED]> To: <users@httpd.apache.org> Sent: Saturday, August 27, 2005 7:11 AM Subject: Re: [EMAIL PROTECTED] "Out of memory" logging format
> do you use NFS? > Search nfs between the apache bugs > This could happen I guess even on local file sistem > when the httpd process tries to read a file: it stats the file for its size > meanwhile if the sought file has been substituted with a new smaller one > it will try to read (and so allocating memory) the last part of the file > that can't find > because of substitution. > Could this scenario be your own? > bye > ----- Original Message ----- > From: "Udo Rader" <[EMAIL PROTECTED]> > To: <users@httpd.apache.org> > Sent: Friday, August 26, 2005 4:59 PM > Subject: Re: [EMAIL PROTECTED] "Out of memory" logging format > > > > On Fri, 2005-08-26 at 10:20 -0400, Joshua Slive wrote: > >> On 8/26/05, Udo Rader <[EMAIL PROTECTED]> 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. > > > > thanks, this looks very promising. > > > > Udo Rader > > > > -- > > bestsolution.at EDV Systemhaus GmbH > > http://www.bestsolution.at > > > > > > --------------------------------------------------------------------- > > 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: [EMAIL PROTECTED] > > " from the digest: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > --------------------------------------------------------------------- > 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: [EMAIL PROTECTED] > " from the digest: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- 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: [EMAIL PROTECTED] " from the digest: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
