News: This forum is now permanently frozen.
Pages: [1]
Topic: Approaching the limit on PV entries  (Read 844 times)
« on: August 14, 2014, 11:34:21 »
wdv *
Posts: 2

After updating FreeBSD 6.x-based m0n0wall 1.3 to m0n0wall 1.8.1
Generic PC on an VMWare ESXi 5.1 Server, AMD Opteron(tm) Processor
6176 686-class CPU with 256 MB RAM for m0n0wall, we were running into
problems. The Uptime was about 14 days under daily load of 30 users.

In system.log error messages appeared:

monospace kernel: Approaching the limit on PV entries, consider increasing either the vm.pmap.shpgperproc or the vm.pmap.pv_entry_max tunable.

after 1 or 2 days the system was starting to kill processes which
resulted in users not being able to authenticate with vouchers on the
portal site.

In system.log the previous error messages disapeared, processes were
killed instead

monospace kernel: pid 27370 (php), uid 0, was killed: out of swap space

Looking for a solution I read in different FreeBSD-mailing lists that
enabling superpages by setting 'vm.pmap_pg_ps_enabled' to "1" and/or
increasing 'vm.pmap.shpgperproc' in '/boot/loader.conf' could help
resolving that issue.

How could I solve this with m0n0wall, isn't 256MB RAM enough for
version 1.8.1?

Thanks in advance.

« Reply #1 on: August 14, 2014, 18:01:56 »
Fred Grayson *****
Posts: 994

In the m0n0wall GUI, what are you seeing for RAM usage when these problems preset themselves?

Status | System

Google is your friend and Bob's your uncle.
« Reply #2 on: August 15, 2014, 09:07:25 »
wdv *
Posts: 2

Memory usage is pretty high, near 80% when this problems occur.
After a reboot and normal operation RAM usage is about 20% in Status | System

Thanks for your reply.
Pages: [1]
Powered by SMF 1.1.20 | SMF © 2013, Simple Machines