Date: Tue, 22 Nov 2011 13:09:54 -0600 From: Adam Vande More <amvandemore@gmail.com> To: Henry M <henry95@gmail.com> Cc: freebsd-questions@freebsd.org Subject: Re: reexec socketpair: No buffer space available Message-ID: <CA%2BtpaK1bvimw-U7uDc2V-OHCm=179K0vr2dU0eqd0ZQywA_a5Q@mail.gmail.com> In-Reply-To: <CAK1r8CUP_W5kHtXVk-_--ZN0-G7Xb-2no3SROTJdgvD2RNDobQ@mail.gmail.com> References: <CAK1r8CUP_W5kHtXVk-_--ZN0-G7Xb-2no3SROTJdgvD2RNDobQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Nov 22, 2011 at 11:50 AM, Henry M <henry95@gmail.com> wrote: > Hi all, > > Has anyone come across this error before: > sshd[20861]: error: reexec socketpair: No buffer space available > > It stops remote users/services to connect to the machine remotely. I have > 17 jails running on the machine. > CPU load on the machine is low, and RAM usage is also low (16GB avail, 5GB > Active) > > System info: > FreeBSD 8.0-RELEASE-p6 FreeBSD 8.0-RELEASE-p6 > > $ netstat -mb > 1029/4101/5130 mbufs in use (current/cache/total) > 514/3446/3960/65536 mbuf clusters in use (current/cache/total/max) > 0/1536 mbuf+clusters out of packet secondary zone in use (current/cache) > 0/1582/1582/12800 4k (page size) jumbo clusters in use > (current/cache/total/max) > 0/0/0/6400 9k jumbo clusters in use (current/cache/total/max) > 0/0/0/3200 16k jumbo clusters in use (current/cache/total/max) > 1285K/14245K/15530K bytes allocated to network (current/cache/total) > 0/0/0 requests for mbufs denied (mbufs/clusters/mbuf+clusters) > 0/0/0 requests for jumbo clusters denied (4k/9k/16k) > 0/0/0 sfbufs in use (current/peak/max) > 0 requests for sfbufs denied > 0 requests for sfbufs delayed > 373686 requests for I/O initiated by sendfile > 0 calls to protocol drain routines > > > What else should I be looking for to help me trouble this? I know I'm > hitting some limit, but not sure which one. > > Any help would be much appreciated. > http://unix.derkeiler.com/Mailing-Lists/FreeBSD/stable/2007-03/msg00764.html So sysctl's like net.inet.tcp.recvbuf_max might play role here, but I would be curious as to what is the reason this comes up in the first place. Is the traffic to system valid, and hence raising the limits would be the correct course of action. Or do you have some deeper problem which limit raising would only mask or temporarily alleviate the issue. -- Adam Vande More
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CA%2BtpaK1bvimw-U7uDc2V-OHCm=179K0vr2dU0eqd0ZQywA_a5Q>