On 3.2.2014 19.58, m.r...@5-cent.us wrote:
That's a*lot* of apache. Is that really correct? Do you really need that
many threads? How heavily is the webserver used?
Is this a good measure? At least it's exact. :-)
# du -sh /var/log/httpd
261M/var/log/httpd
Those logs are rotated with
On Feb 4, 2014, at 3:46 AM, Jussi Hirvi listmem...@greenspot.fi wrote:
On 3.2.2014 19.58, m.r...@5-cent.us wrote:
That's a*lot* of apache. Is that really correct? Do you really need that
many threads? How heavily is the webserver used?
Is this a good measure? At least it's exact. :-)
On Tue, Feb 4, 2014 at 7:53 AM, sjt5atra sjt5a...@gmail.com wrote:
Others have mentioned tuning httpd.conf parameters. Problem is apache
doesn't give you the math to know what to set those without lots of
trial-and-error. The best guide for this math is from F5:
My web name server runs out of memory from time to time, to the point
where it's completely unresponsive to anything. At that point reset is
the only alternative. (Or, as this is a virtual guest, I just say virsh
destroy).
But why this happens - I would like to know.
The host in question is
Jussi Hirvi wrote:
My web name server runs out of memory from time to time, to the point
where it's completely unresponsive to anything. At that point reset is
the only alternative. (Or, as this is a virtual guest, I just say virsh
destroy).
But why this happens - I would like to know.
- Original Message -
From: Jussi Hirvi listmem...@greenspot.fi
To: CentOS mailing list centos@centos.org
Sent: Monday, February 3, 2014 5:43:16 AM
Subject: [CentOS] Memory leak - how to investigate
My web name server runs out of memory from time to time, to the
point
where it's
On Mon, Feb 3, 2014 at 8:43 AM, Jussi Hirvi listmem...@greenspot.fi wrote:
My web name server runs out of memory from time to time, to the point
where it's completely unresponsive to anything. At that point reset is
the only alternative. (Or, as this is a virtual guest, I just say virsh
Kwan Lowe wrote:
On Mon, Feb 3, 2014 at 8:43 AM, Jussi Hirvi listmem...@greenspot.fi
wrote:
My web name server runs out of memory from time to time, to the point
where it's completely unresponsive to anything. At that point reset is
the only alternative. (Or, as this is a virtual guest, I
On Mon, Feb 3, 2014 at 8:43 AM, Jussi Hirvi listmem...@greenspot.fi
wrote:
My web name server runs out of memory from time to time, to the point
where it's completely unresponsive to anything. At that point reset is
the only alternative. (Or, as this is a virtual guest, I just say
On 2/3/2014 12:59, m.r...@5-cent.us wrote:
Kwan Lowe wrote:
Mem: 1361564k total, 1264324k used,97240k free, 8428k buffers
That doesn't look like a lot of memory.. Possible to add another .5G or
so?
Ah! I missed that. Is it actually the case that your server doesn't even
have 2G
On Mon, Feb 3, 2014 at 1:59 PM, m.r...@5-cent.us wrote:
Kwan Lowe wrote:
On Mon, Feb 3, 2014 at 8:43 AM, Jussi Hirvi listmem...@greenspot.fi
wrote:
My web name server runs out of memory from time to time, to the point
where it's completely unresponsive to anything. At that point reset is
On 2/3/2014 13:39, Les Mikesell wrote:
A new child process will share almost all
memory with the parent, slowly growing as values change.
The trick is to load up as much as possible in the parent before the
children start forking off.
If the parent does little more than initialize the web
On Mon, Feb 3, 2014 at 2:45 PM, Warren Young war...@etr-usa.com wrote:
On 2/3/2014 13:39, Les Mikesell wrote:
A new child process will share almost all
memory with the parent, slowly growing as values change.
The trick is to load up as much as possible in the parent before the
children
On Mon, Feb 3, 2014 at 3:36 PM, Warren Young war...@etr-usa.com wrote:
Ah! I missed that. Is it actually the case that your server doesn't even
have 2G of RAM? That's a *real* problem.
Small RAM limits with strange values like 1.3 GB are normal for VMs.
This is true. I can start up VMs
On Mon, Feb 3, 2014 at 2:59 PM, m.r...@5-cent.us wrote:
We've got a number of websites on one of our production servers, and they
get hit moderately (it's not Amazon... but they are US gov't scientific
research sites), and I think we've got 25 threads running, total, to
server *all* of them.
Kwan Lowe wrote:
On Mon, Feb 3, 2014 at 2:59 PM, m.r...@5-cent.us wrote:
We've got a number of websites on one of our production servers, and
they
get hit moderately (it's not Amazon... but they are US gov't scientific
research sites), and I think we've got 25 threads running, total, to
You could try tunning apache..
Start with MaxRequestPerChild, whichs sets a number of requests for
child process before it is stopped. When a child is stopped, memory is
freed. This could be your protection before running out of memory.
KeepAlive is enabled? If yes, maybe you could try
17 matches
Mail list logo
