FreeBSD 8.2-RELEASE
From time to time, I get in /var/log/messages
kernel: Approaching the limit on PV entries, consider increasing either
the vm.pmap.shpgperproc or the vm.pmap.pv_entry_max sysctl.
this started a few weeks ago, never had that before, don't have it on other
FreeBSD 8.2-RELEASE
Did you explicitly disabled superpages?
What is the output of $ sysctl vm.pmap.pg_ps_enabled ?
On 02/01/2012 10:17, n dhert wrote:
FreeBSD 8.2-RELEASE
From time to time, I get in /var/log/messages
kernel: Approaching the limit on PV entries, consider increasing either
On Wed, 1 Feb 2012 10:17:21 +0100
n dhert ndhert...@gmail.com wrote:
FreeBSD 8.2-RELEASE
From time to time, I get in /var/log/messages
kernel: Approaching the limit on PV entries, consider increasing
either the vm.pmap.shpgperproc or the vm.pmap.pv_entry_max sysctl.
this started a few
Hello,
We have an HP Proliant DL380G5 with 4GB of RAM and FreeBSD 7.0 which
runs PostgreSQL 8.3 for more than a year now. No problems, except that
two days ago I noticed those messages in my kernel logs :
Approaching the limit on PV entries, consider increasing either the
vm.pmap.shpgperproc
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 high load;
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
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
system can run under high
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 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
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
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 decrease the MaxClients
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
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 !
During
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
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
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
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 your
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
Apache(set
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 demand
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 inside
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
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 AMD64
On 10/10/08, Mark Tinguely [EMAIL PROTECTED] wrote:
vm.pmap.pv_entry_count: 583006
vm.pmap.shpgperproc: 200
vm.pmap.pv_entry_max: 2243305
The system:
FreeBSD 7.0-RELEASE-p5 FreeBSD 7.0-RELEASE-p5 #0: Wed Oct 1
07:51:58 UTC 2008
[EMAIL
Thanks. I'll see what happens.
In amd64/7.0 is there any chance running out of pv_entrys would show
up as failures in interprocess communication rather than a panic? The
original symptom was that certain web pages (or jailed servers, I'm
not sure) were unreachable, as if the firewall
A web server with several jailed copies of Apache is having problems
that seem to be caused by incorrect IPFW rules, but in the process of
working on that, I find in the log the following repeated many times:
Oct 8 23:29:50 spider kernel: Approaching the limit on PV entries,
consider increasing
Bob Johnson wrote:
A web server with several jailed copies of Apache is having problems
that seem to be caused by incorrect IPFW rules, but in the process of
working on that, I find in the log the following repeated many times:
Oct 8 23:29:50 spider kernel: Approaching the limit on PV entries
vm.pmap.pv_entry_count: 583006
vm.pmap.shpgperproc: 200
vm.pmap.pv_entry_max: 2243305
The system:
FreeBSD 7.0-RELEASE-p5 FreeBSD 7.0-RELEASE-p5 #0: Wed Oct 1
07:51:58 UTC 2008
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC amd64
Can someone briefly explain what
Hello questions,
I'm getting these messages on my FreeBSD 7.0-RC1 as well as on BETA4
boxes (I haven't noticed it in the past):
Dec 27 01:18:49 web1 kernel: Approaching the limit on PV entries, consider
increasing either the vm.pmap.shpgperproc or the vm.pmap.pv_entry_max sysctl.
I
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
searching on the error and found the same problem
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
searching
, 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
searching on the error and found the same problem with Apache, but none with
my
configuration
/MYKNL
Panic String: no pv entries: increase vm.pmap.shpgperproc
Dump Parity: 2383301964
Bounds: 49
Dump Status: good”
I had searched in google, but I didn’t know how to do.
You _should_ be able to raise the vm.pmap.shpgperproc sysctl to prevent
the problem
)
Blocksize: 512
Dumptime: Wed Jan 17 16:39:08 2007
Hostname: myhost.mydomain.com
Magic: FreeBSD Kernel Dump
Version String: FreeBSD 6.0-RELEASE #0: Tue Apr 25 15:07:33 CST 2006
[EMAIL PROTECTED]:/usr/src/sys/i386/compile/MYKNL
Panic String: no pv entries: increase
)
Blocksize: 512
Dumptime: Wed Jan 17 16:39:08 2007
Hostname: myhost.mydomain.com
Magic: FreeBSD Kernel Dump
Version String: FreeBSD 6.0-RELEASE #0: Tue Apr 25 15:07:33 CST 2006
[EMAIL PROTECTED]:/usr/src/sys/i386/compile/MYKNL
Panic String: no pv entries: increase vm.pmap.shpgperproc
Panic String: no pv entries: increase vm.pmap.shpgperproc
Dump Parity: 2383301964
Bounds: 49
Dump Status: good”
I had searched in google, but I didn’t know how to do.
You _should_ be able to raise the vm.pmap.shpgperproc sysctl to prevent
the problem -- but there doesn't seem
Hostname: myhost.mydomain.com
Magic: FreeBSD Kernel Dump
Version String: FreeBSD 6.0-RELEASE #0: Tue Apr 25 15:07:33 CST 2006
[EMAIL PROTECTED]:/usr/src/sys/i386/compile/MYKNL
Panic String: no pv entries: increase vm.pmap.shpgperproc
Dump Parity: 2383301964
Bounds: 49
Dump Status: good
Hello list,
I am configuring a very heavily used apache webserver, that required
some special needs.
This particular configuration needs to have at least 1024 httpds always
running. Reaching this number is not a problem, but whenever I stop
apache via apachectl stop, I notice all the httpds
Hi,
I just got this on one of our machines It talks about Apache
being the issue, but when I run the ipcs -a ; sysctl vm.zone | grep PV
I get :
odin# ipcs -a ; sysctl vm.zone | grep PV
Message Queues:
T ID KEYMODE OWNERGROUP CREATOR CGROUP CBYTES
QNUM
-
From: admin [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Tuesday, August 12, 2003 2:23 PM
Subject: collecting pv entries -- suggest increasing PMAP_SHPGPERPROC
FreeBSD 4.8 Stable
Hi there,
I am seeing the following log entry in my /var/log/messages
any clue what I can do to cure
FreeBSD 4.8 Stable
Hi there,
I am seeing the following log entry in my /var/log/messages
any clue what I can do to cure this issue?
snip
Aug 12 03:00:55 /kernel: pmap_collect: collecting pv entries -- suggest
increasing PMAP_SHPGPERPROC
- snip
- noah
Markie
- Original Message -
From: admin [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Tuesday, August 12, 2003 2:23 PM
Subject: collecting pv entries -- suggest increasing PMAP_SHPGPERPROC
FreeBSD 4.8 Stable
Hi there,
I am seeing the following log entry in my /var/log
41 matches
Mail list logo
