On Tuesday 28 October 2008 15:44:49 Francis Dubé wrote:
> Jeremy Chadwick a écrit :
> > On Mon, Oct 27, 2008 at 12:56:30PM -0700, Chuck Swiger wrote:
> >> On Oct 27, 2008, at 12:38 PM, FreeBSD wrote:
> You need to keep your MaxClients setting limited to what your system
> can run under hi
Chuck Swiger a écrit :
On Oct 28, 2008, at 9:49 AM, Francis Dubé wrote:
Here's an example of top's output regarding our httpd process :
54326 apache1 960 156M 13108K select 1 0:00 0.15%
httpd
54952 apache1 960 156M 12684K select 1 0:00 0.10%
httpd
52343 apac
On Oct 28, 2008, at 9:49 AM, Francis Dubé wrote:
Here's an example of top's output regarding our httpd process :
54326 apache1 960 156M 13108K select 1 0:00
0.15% httpd
54952 apache1 960 156M 12684K select 1 0:00
0.10% httpd
52343 apache1 40
Jeremy Chadwick a écrit :
On Tue, Oct 28, 2008 at 10:44:49AM -0400, Francis Dubé wrote:
Jeremy Chadwick a écrit :
On Mon, Oct 27, 2008 at 12:56:30PM -0700, Chuck Swiger wrote:
On Oct 27, 2008, at 12:38 PM, FreeBSD wrote:
You need to keep your MaxClients setting
On Tue, Oct 28, 2008 at 10:44:49AM -0400, Francis Dubé wrote:
> Jeremy Chadwick a écrit :
>> On Mon, Oct 27, 2008 at 12:56:30PM -0700, Chuck Swiger wrote:
>>
>>> On Oct 27, 2008, at 12:38 PM, FreeBSD wrote:
>>>
> You need to keep your MaxClients setting limited to what your
> syste
Jeremy Chadwick a écrit :
On Mon, Oct 27, 2008 at 12:56:30PM -0700, Chuck Swiger wrote:
On Oct 27, 2008, at 12:38 PM, FreeBSD wrote:
You need to keep your MaxClients setting limited to what your system
can run under high load; generally the amount of system memory is the
governing fact
On 10/27/08, Simon Chang <[EMAIL PROTECTED]> wrote:
>> Raising PMAP_SHPGPERPROC works most of the time. You can also re-tune
[...]
> By the way, does anyone know whether there is any way to tune
> PMAP_SHPGPERPROC using sysctl, or does such button/knob not exist?
It is tunable with a sysctl in AM
Francis Dubé wrote:
Hi everyone,
I'm running a a webserver on FreeBSD (6.2-RELEASE-p6) and I have this
error in my logs :
collecting pv entries -- suggest increasing PMAP_SHPGPERPROC
I've read that this is mainly caused by Apache spawning too many
processes. Everyone seems to suggest to dec
In response to "Simon Chang" <[EMAIL PROTECTED]>:
>
> By the way, does anyone know whether there is any way to tune
> PMAP_SHPGPERPROC using sysctl, or does such button/knob not exist?
No. I've had this discussion with the developer who originally wrote
that code. The table size is too deep ins
> Raising PMAP_SHPGPERPROC works most of the time. You can also re-tune
> your Apache setting to keep processes from constantly spawning and
> dying. For example, set the max spare and min spare servers settings
> higher, so Apache keeps more spare servers around instead of spawning
> them on dem
In response to FreeBSD <[EMAIL PROTECTED]>:
> Simon Chang a écrit :
> >> collecting pv entries -- suggest increasing PMAP_SHPGPERPROC
> >>
> >> I've read that this is mainly caused by Apache spawning too many processes.
> >> Everyone seems to suggest to decrease the MaxClients directive in
> >> A
On Mon, Oct 27, 2008 at 12:56:30PM -0700, Chuck Swiger wrote:
> On Oct 27, 2008, at 12:38 PM, FreeBSD wrote:
>>> You need to keep your MaxClients setting limited to what your system
>>> can run under high load; generally the amount of system memory is the
>>> governing factor. [1] If you set you
On Oct 27, 2008, at 12:38 PM, FreeBSD wrote:
You need to keep your MaxClients setting limited to what your
system can run under high load; generally the amount of system
memory is the governing factor. [1] If you set your MaxClients
higher than that, your system will start swapping under th
Simon Chang a écrit :
collecting pv entries -- suggest increasing PMAP_SHPGPERPROC
I've read that this is mainly caused by Apache spawning too many processes.
Everyone seems to suggest to decrease the MaxClients directive in Apache(set
to 450 at the moment), but here's the problem...i need to in
Chuck Swiger a écrit :
On Oct 27, 2008, at 11:39 AM, Francis Dubé wrote:
I've read that this is mainly caused by Apache spawning too many
processes. Everyone seems to suggest to decrease the MaxClients
directive in Apache(set to 450 at the moment), but here's the
problem...i need to increase i
> collecting pv entries -- suggest increasing PMAP_SHPGPERPROC
>
> I've read that this is mainly caused by Apache spawning too many processes.
> Everyone seems to suggest to decrease the MaxClients directive in Apache(set
> to 450 at the moment), but here's the problem...i need to increase it !
> D
On Oct 27, 2008, at 11:39 AM, Francis Dubé wrote:
I've read that this is mainly caused by Apache spawning too many
processes. Everyone seems to suggest to decrease the MaxClients
directive in Apache(set to 450 at the moment), but here's the
problem...i need to increase it ! During peaks all
It looks like a process associated with Postfix is eating up all of the memory
and crashing the system. Im trying to find out which one now.
Thanks for you help.
Thron
On Mon Sep 24 9:13 , Bill Moran sent:
>In response to [EMAIL PROTECTED]>:
>
>> Hi,
>>
>> I have a new 6.2 install running po
In response to <[EMAIL PROTECTED]>:
> Hi,
>
> I have a new 6.2 install running postfix, amavisd-new, clamav and SpamAssassin
> and over the weekend the server stopped responding with the following error.
> collecting pv entries -- suggest increasing PMAP_SHPGPERPROC. I did some
> google
> searc
On Tue, 12 Aug 2003 21:44:20 +0100, Markie wrote
> Hi,
>
> I have had this error once before, though it seemed to freeze/panic the
> machine, I think it may have been related to Apache or PHP since I
> was doing a 'stress test' at the time. I would guess that you can up
> PMAP_SHPGPERPROC in the
Hi,
I have had this error once before, though it seemed to freeze/panic the
machine, I think it may have been related to Apache or PHP since I was doing
a 'stress test' at the time. I would guess that you can up PMAP_SHPGPERPROC
in the kernel, perhaps a sysctl.
Markie
- Original Message
21 matches
Mail list logo
