kern.ipc.maxsockets limit reached on Raspberry

Ian Lepore ian at FreeBSD.org
Fri Mar 22 17:27:45 UTC 2013


On Fri, 2013-03-22 at 20:36 +0800, Alie Tan wrote:
> On Mon, Mar 18, 2013 at 9:19 PM, Ronald Klop <ronald-freebsd8 at klop.yi.org>wrote:
> 
> > On Mon, 18 Mar 2013 13:28:19 +0100, Alie Tan <alie at affle.com> wrote:
> >
> >  Forgot to mention. I can't SSH to the device once this issue occurred.
> >>
> >
> > That is expected. SSH needs a socket, so as maxsockets is reached... You
> > get the point. ;-)
> >
> >
> >>
> >> On Mon, Mar 18, 2013 at 8:23 PM, Alie Tan <alie at affle.com> wrote:
> >>
> >>  Hi,
> >>>
> >>> I just got this issue on my Hiawatha web-server on Raspi 512MB with
> >>> FreeBSD r247518. This issue happens every 1-2 days.
> >>>
> >>> Anyone got any clue about this issue? I can increase the maxsockets but
> >>> it
> >>> seems just a workaround.
> >>>
> >>
> >
> > You can put this in cron. (From the top of my head so beware of typos.)
> >
> > */15 * * * * sockstat
> >
> > This will mail you the open sockets every 15 minutes. See what is growing
> > infinitely.
> >
> Strange http://ompldr.org/vaHVocQ/P30322-202828.jpg
> 
> All Foreign addresses are *.* and seems opened sockets also still normal,
> not above maxsockets
> 

That's seems to be, if anything, not enough sockets open, and no udp
sockets at all (do you not run ntpd? syslogd?  they normally have udp
sockets open).  Just to make sure the values themselves are sane, what
does sysctl kern.ipc.maxsockets show?  How about vmstat -z | grep inpcb?
On my (completely idle) rpi, I see this:

rpi# sysctl kern.ipc.maxsockets
kern.ipc.maxsockets: 16389

rpi# vmstat -z | grep inpcb
udp_inpcb:              252,  16395,       4,      26,    1928,   0,   0
tcp_inpcb:              252,  16395,       2,      28,       6,   0,   0

-- Ian




More information about the freebsd-arm mailing list