[ previous ] [ next ] [ threads ]
 From:  Angus Jordan <angus dot jordan at gmail dot com>
 To:  James Sheridan <stuff at phosphor dash ink dot com>
 Cc:  m0n0wall at lists dot m0n0 dot ch
 Subject:  Re: [m0n0wall] Beta 1.2b10 - All mbuf clusters exhausted
 Date:  Mon, 19 Sep 2005 12:32:11 -0700
Hi James,

What are your hardware specs? Also, can you goto the 
http://monowall.ip/exec.php and type this command in:

netstat -m

Send us the output from that command.

Also, for your reading; here is the pertinent info from the tuning manpage:

kern.ipc.nmbclusters may be adjusted to increase the number of network
mbufs the system is willing to allocate. Each cluster represents approx-
imately 2K of memory, so a value of 1024 represents 2M of kernel memory
reserved for network buffers. You can do a simple calculation to figure
out how many you need. If you have a web server which maxes out at 1000
simultaneous connections, and each connection eats a 16K receive and 16K
send buffer, you need approximately 32MB worth of network buffers to deal
with it. A good rule of thumb is to multiply by 2, so 32MBx2 = 64MB/2K =
32768. So for this case you would want to set kern.ipc.nmbclusters to
32768. We recommend values between 1024 and 4096 for machines with mod-
erates amount of memory, and between 4096 and 32768 for machines with
greater amounts of memory. Under no circumstances should you specify an
arbitrarily high value for this parameter, it could lead to a boot-time
crash. The -m option to netstat(1) may be used to observe network clus-
ter use. Older versions of FreeBSD do not have this tunable and require
that the kernel config(8) option NMBCLUSTERS be set instead.

Angus Jordan

On 9/16/05, James Sheridan <stuff at phosphor dash ink dot com> wrote:
> Just updated from 1.2b3 to the newest beta and noticed this in my logs
> (many times) during high-volume traffic.
> /kernel: All mbuf clusters exhausted, please see tuning(7).
> I'm running off a CF card and updated via the GUI update page. 
> Everything else looks ok and the device is running so I'm not real
> worried, but obviously something is wrong. Going back to 1.2b3 (where I
> am now) shows no such errors.
> Running "df -k" through exec.php on 1.2b3 shows:
> $ df -k
> Filesystem 1K-blocks Used Avail Capacity Mounted on
> /dev/md0c 10879 9669 1210 89% /
> procfs 4 4 0 100% /proc
> /dev/ad2a 5919 5553 366 94% /cf
> and on 1.2b10:
> $ df -k
> Filesystem 1K-blocks Used Avail Capacity Mounted on
> /dev/md0c 10879 10134 745 93% /
> /dev/ad2a 5919 5613 306 95% /cf
> procfs 4 4 0 100% /proc
> Am I just at the limits of the card now? Is there a configuration change
> I can make to clear this up?
> Thanks.
> --
> James
> --------------------------------------------------------------------- 
> To unsubscribe, e-mail: m0n0wall dash unsubscribe at lists dot m0n0 dot ch
> For additional commands, e-mail: m0n0wall dash help at lists dot m0n0 dot ch