From owner-freebsd-arm@FreeBSD.ORG  Mon Mar 18 13:35:32 2013
Return-Path: <owner-freebsd-arm@FreeBSD.ORG>
Delivered-To: freebsd-arm@freebsd.org
Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115])
 by hub.freebsd.org (Postfix) with ESMTP id 0469FE33
 for <freebsd-arm@freebsd.org>; Mon, 18 Mar 2013 13:35:32 +0000 (UTC)
 (envelope-from ronald-freebsd8@klop.yi.org)
Received: from smarthost1.greenhost.nl (smarthost1.greenhost.nl
 [195.190.28.78]) by mx1.freebsd.org (Postfix) with ESMTP id 99DBAAC0
 for <freebsd-arm@freebsd.org>; Mon, 18 Mar 2013 13:35:31 +0000 (UTC)
Received: from smtp.greenhost.nl ([213.108.104.138])
 by smarthost1.greenhost.nl with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32)
 (Exim 4.69) (envelope-from <ronald-freebsd8@klop.yi.org>)
 id 1UHZyU-0003Vk-LL
 for freebsd-arm@freebsd.org; Mon, 18 Mar 2013 14:19:39 +0100
Received: from [81.21.138.17] (helo=ronaldradial.versatec.local)
 by smtp.greenhost.nl with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32)
 (Exim 4.72) (envelope-from <ronald-freebsd8@klop.yi.org>)
 id 1UHZyU-0007gN-0x
 for freebsd-arm@freebsd.org; Mon, 18 Mar 2013 14:19:38 +0100
Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes
To: freebsd-arm@freebsd.org
Subject: Re: kern.ipc.maxsockets limit reached on Raspberry
References: <CANuCnH-Y4UoMoihO1R1NNj2GgT4XG6tn3Z51-ZFAm62rHcF7Ow@mail.gmail.com>
 <CANuCnH8M9F70-_sKw+zLKyL9L9DWqStwddp0anPN5EYV+e=8Gg@mail.gmail.com>
Date: Mon, 18 Mar 2013 14:19:36 +0100
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
From: "Ronald Klop" <ronald-freebsd8@klop.yi.org>
Message-ID: <op.wt48mytt8527sy@ronaldradial.versatec.local>
In-Reply-To: <CANuCnH8M9F70-_sKw+zLKyL9L9DWqStwddp0anPN5EYV+e=8Gg@mail.gmail.com>
User-Agent: Opera Mail/12.14 (Win32)
X-Virus-Scanned: by clamav at smarthost1.samage.net
X-Spam-Level: /
X-Spam-Score: -0.0
X-Spam-Status: No, score=-0.0 required=5.0 tests=BAYES_20 autolearn=disabled
 version=3.3.1
X-Scan-Signature: 919fae14bc17c74543a025539baad412
X-BeenThere: freebsd-arm@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Porting FreeBSD to the StrongARM Processor <freebsd-arm.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-arm>,
 <mailto:freebsd-arm-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-arm>
List-Post: <mailto:freebsd-arm@freebsd.org>
List-Help: <mailto:freebsd-arm-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arm>,
 <mailto:freebsd-arm-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Mar 2013 13:35:32 -0000

On Mon, 18 Mar 2013 13:28:19 +0100, Alie Tan <alie@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@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.

Ronald.