On 2013-05-23, james <[email protected]> wrote: > We had a short outage today and I think it might have been due to our > firewall. I can see that we hit the limit for this variable but I'm not > really sure what it does or if it is safe to set it higher. I found the > following at the time of the outage in the log: > > May 23 09:57:27 shiva2 /bsd: WARNING: mclpool limit reached; increase > kern.maxclusters > May 23 09:58:27 shiva2 /bsd: WARNING: mclpool limit reached; increase > kern.maxclusters > May 23 10:00:27 shiva2 last message repeated 2 times > > netstat -m shows this now: > > -bash-3.1$ netstat -m > 199 mbufs in use: > 195 mbufs allocated to data > 1 mbuf allocated to packet headers > 3 mbufs allocated to socket names and addresses > 194/6152/6144 mbuf clusters in use (current/peak/max)
If this is under normal conditions then it suggests kern.maxclusters is probably high enough, most likely you ran into an mbuf leak in which case raising nmbclusters might help in the short term, but would only delay the inevitable. You could try logging this line periodically and determine if there's a slow leak or a fast increase in mbuf clusters in use.. > 13860 Kbytes allocated to network (3% in use) > 0 requests for memory denied > 0 requests for memory delayed > 0 calls to protocol drain routines > > Can anyone offer any advice? Other than the above, you missed including the dmesg that is requested for any problem reports, and an overview of the network configuration might suggest areas to look at. Also since you are running a version of the OS which can be no newer than December 2008, you might like to investigate the option of upgrading, because bugs do get fixed..
