From owner-freebsd-arm@FreeBSD.ORG  Mon Mar 18 12:28:20 2013
Return-Path: <owner-freebsd-arm@FreeBSD.ORG>
Delivered-To: freebsd-arm@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by hub.freebsd.org (Postfix) with ESMTP id 9AB9FB28
 for <freebsd-arm@freebsd.org>; Mon, 18 Mar 2013 12:28:20 +0000 (UTC)
 (envelope-from alie@affle.com)
Received: from mail-qc0-x230.google.com (mail-qc0-x230.google.com
 [IPv6:2607:f8b0:400d:c01::230])
 by mx1.freebsd.org (Postfix) with ESMTP id 336677DA
 for <freebsd-arm@freebsd.org>; Mon, 18 Mar 2013 12:28:20 +0000 (UTC)
Received: by mail-qc0-f176.google.com with SMTP id n41so2697984qco.21
 for <freebsd-arm@freebsd.org>; Mon, 18 Mar 2013 05:28:19 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=google.com; s=20120113;
 h=mime-version:x-received:in-reply-to:references:date:message-id
 :subject:from:to:content-type:x-gm-message-state;
 bh=iv/5Rfu7WSElNRafavvnDxQxEEkdK3tMx9BQ4vmrfrQ=;
 b=U/VxtGRSqWKOQVvJC0OaAPNb33Tk86mfFzadtaEZcRtZfh+dVB89xgBi+KjSSM+fZJ
 BhColCcBI5BuehGgAYoFKPDFEnnDHEERRooAC9xYdd3MpdiFwVnK1OkRzN61iIvEjIAo
 KUYNkAIVK5yQBDE3nTadncJZ/TL7PL5VSqc4Ontx6c/aQN93N+oL0hbKqgeGeR22Gr5j
 11EbenKqdp/9SxbzzYPQS07WR6vPzN0571D8FyARHU6zoSjHv0H4fk1XTZAnA1tbpzuj
 AkFgujST3QE3wOaNYPP8x7Pr6T1/lTaubx7I8w4+CRdhph5EUNcrLNmTtTPzhne/PatJ
 CtIQ==
MIME-Version: 1.0
X-Received: by 10.224.18.138 with SMTP id w10mr19143209qaa.20.1363609699686;
 Mon, 18 Mar 2013 05:28:19 -0700 (PDT)
Received: by 10.49.87.193 with HTTP; Mon, 18 Mar 2013 05:28:19 -0700 (PDT)
In-Reply-To: <CANuCnH-Y4UoMoihO1R1NNj2GgT4XG6tn3Z51-ZFAm62rHcF7Ow@mail.gmail.com>
References: <CANuCnH-Y4UoMoihO1R1NNj2GgT4XG6tn3Z51-ZFAm62rHcF7Ow@mail.gmail.com>
Date: Mon, 18 Mar 2013 20:28:19 +0800
Message-ID: <CANuCnH8M9F70-_sKw+zLKyL9L9DWqStwddp0anPN5EYV+e=8Gg@mail.gmail.com>
Subject: Re: kern.ipc.maxsockets limit reached on Raspberry
From: Alie Tan <alie@affle.com>
To: "freebsd-arm@freebsd.org" <freebsd-arm@freebsd.org>
X-Gm-Message-State: ALoCoQmm2hmDDuQYzIztLdZ5xOqQqwdgVFJf1xjrxuJvNiSCw3MAn51aNT1H4r+dCUYW4Wg6Cn+o
Content-Type: text/plain; charset=ISO-8859-1
X-Content-Filtered-By: Mailman/MimeDel 2.1.14
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 12:28:20 -0000

Forgot to mention. I can't SSH to the device once this issue occurred.


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.
>
> Regards,
> Alie T
>
>
>