This is a discussion on Re: Apache 2 - child process memory size growing - MaxMemFree within the Linux Web Servers forums, part of the Web Server and Related Forums category; "Christophe LEITIENNE" <c.leitienne@bgpartners.fr> wrote in message news:<bds6dm$5mh$1@news-reader1....
|
|||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
|
|||
|
"Christophe LEITIENNE" <c.leitienne@bgpartners.fr> wrote in message news:<bds6dm$5mh$1@news-reader1.wanadoo.fr>...
> Hi all, > > We're using Apache 2 to serve big files generated by php or cgi > shell-script. > Apache 2 is configured to use prefork MPM. > It runs on a Linux RedHat 9.0, P200 with 128MB. So you are probably using 2.0.40? If so, you should upgrade to the latest release (2.0.46) and I bet the problem will go away. Earlier releases of apache 2 would queue up the entire request in order to determine the content-length. JOshua. |
|
|||
|
Well, I found this seems to be a known bug, reopened some time ago on
bugzilla. cf. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=11427. Chris. |
|
|||
|
"Christophe LEITIENNE" <c.leitienne@bgpartners.fr> wrote in message news:<bdum0a$9i0$1@news-reader1.wanadoo.fr>...
> Well, I found this seems to be a known bug, reopened some time ago on > bugzilla. > cf. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=11427. No. The bug you posted to is almost certainly win32 specific. As I said, you need to start by upgrading to the most recent apache. Joshua. |
|
|||
|
"Joshua Slive" <google@slive.ca> a écrit dans le message de news:916ecaf4.0307020927.3c5a9f24@posting.google.c om... > "Christophe LEITIENNE" <c.leitienne@bgpartners.fr> wrote in message news:<bdum0a$9i0$1@news-reader1.wanadoo.fr>... > > Well, I found this seems to be a known bug, reopened some time ago on > > bugzilla. > > cf. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=11427. > > No. The bug you posted to is almost certainly win32 specific. > Not sure at all. All posts really sounds like my problem. > As I said, you need to start by upgrading to the most recent apache. > As I said, I already did. I use 2.0.46. Chris. |
|
|||
|
"Christophe LEITIENNE" <c.leitienne@bgpartners.fr> wrote in message news:<be0g4p$3ti$1@news-reader3.wanadoo.fr>...
> "Joshua Slive" <google@slive.ca> a écrit dans le message de > news:916ecaf4.0307020927.3c5a9f24@posting.google.c om... > > "Christophe LEITIENNE" <c.leitienne@bgpartners.fr> wrote in message > news:<bdum0a$9i0$1@news-reader1.wanadoo.fr>... > > > Well, I found this seems to be a known bug, reopened some time ago on > > > bugzilla. > > > cf. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=11427. > > > > No. The bug you posted to is almost certainly win32 specific. > > > Not sure at all. All posts really sounds like my problem. > > > As I said, you need to start by upgrading to the most recent apache. > > > As I said, I already did. I use 2.0.46. I missed that part, sorry. But if you are going to report a memory leak, you need to be extremely specific about your system. You haven't said what modules you are using, what changes you have made from the default config, etc. Joshua. |