Approaching the limit on PV entries, consider increasing either the vm.pmap.shpgperproc or the vm.pmap.pv_entry_max sysctl.

[Evren Yurtesen]

Thomas Hurst wrote:

>> In either case, I already increased vm.pmap.shpgperproc to 2000 (from
>> 200) and still the error occurs, there is not so much load on this
>> box, maybe there is a leak somewhere?
> 
> What sort of load is there?  Do you have a bunch of big processes
> sharing significant chunks of memory in any way?
> 

How do I see what process is sharing memory and how much memory?

There are a bunch of apache 2.2 processes working normally about 20-30 
processes. This box doesnt do much more than that...

I just checked the machine and here is what it looks like:
  2:32PM  up 18 days,  5:40, 3 users, load averages: 0.41, 0.36, 0.27

web:/root#ps ax |grep http
21429  ??  Ss     0:18.08 /usr/local/sbin/httpd
86473  ??  S      0:00.09 /usr/local/sbin/httpd
86659  ??  S      0:00.09 /usr/local/sbin/httpd
86851  ??  S      0:00.07 /usr/local/sbin/httpd
86857  ??  S      0:00.04 /usr/local/sbin/httpd
86912  ??  S      0:00.04 /usr/local/sbin/httpd
86918  ??  S      0:00.03 /usr/local/sbin/httpd
86919  ??  S      0:00.03 /usr/local/sbin/httpd
86996  ??  S      0:00.04 /usr/local/sbin/httpd
87023  ??  S      0:00.02 /usr/local/sbin/httpd
87028  ??  S      0:00.03 /usr/local/sbin/httpd
87059  ??  S      0:00.01 /usr/local/sbin/httpd
87060  ??  S      0:00.01 /usr/local/sbin/httpd
87062  ??  S      0:00.02 /usr/local/sbin/httpd
87065  ??  S      0:00.03 /usr/local/sbin/httpd
87074  ??  S      0:00.01 /usr/local/sbin/httpd
87076  ??  S      0:00.02 /usr/local/sbin/httpd
87077  ??  S      0:00.03 /usr/local/sbin/httpd
87079  ??  S      0:00.04 /usr/local/sbin/httpd
87081  ??  S      0:00.03 /usr/local/sbin/httpd
87083  ??  S      0:00.03 /usr/local/sbin/httpd
87085  ??  S      0:00.04 /usr/local/sbin/httpd
87090  ??  S      0:00.02 /usr/local/sbin/httpd
87190  p1  R+     0:00.00 grep http
web:/root#

Although I see now that for 2 days the PV entries error did not appear. I wonder 
if it is spooling up somehow...

There is a cron job restarting apache everyday at midnight so it cant be apache 
leaking perhaps.

Thanks,
Evren