From owner-freebsd-stable@FreeBSD.ORG Tue Feb 5 19:38:38 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 89780741 for ; Tue, 5 Feb 2013 19:38:38 +0000 (UTC) (envelope-from efraindector@motumweb.com) Received: from mail-pa0-f43.google.com (mail-pa0-f43.google.com [209.85.220.43]) by mx1.freebsd.org (Postfix) with ESMTP id 5FE39276 for ; Tue, 5 Feb 2013 19:38:38 +0000 (UTC) Received: by mail-pa0-f43.google.com with SMTP id bh2so323953pad.16 for ; Tue, 05 Feb 2013 11:38:32 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:message-id:from:to:cc:references:in-reply-to:subject :date:organization:mime-version:content-type :content-transfer-encoding:x-priority:x-msmail-priority:importance :x-mailer:x-mimeole:x-gm-message-state; bh=0aYwFLvNQoijSAA1+AH/uA0fEDvEOMDpv22CuAvrwAE=; b=K4FLyO3Cj5pf7Dwe2AMSFKBD5PUnoATgERBnApLMlH43Wap9W1KxT3J+2wpgBNopn7 Gp0GtzFVZekU+rAZSv4q/W3rmSGz2zeWyz3rxuZIHdQOTHOc9zb5kicicSJxRwrqy+nW tA1Rz6vnJH0nXlYn14e2M3FMPfkFZYmg61EZMYhFVOHaBplcG0J++GK66GNNvT5CdKfq vbkUCBfySpUILMOA1u/CqLpsXKo6crTPDKrGKy8vlSlDDSicAJGlkeTQSEZWfng/5oAg WHiVlm5sRzDY13vfVMoMGdGAogIX34WKWYWSG0omCBbnWyqco0mUxa3Ydxo5nEI5ZVgR SqEw== X-Received: by 10.66.81.199 with SMTP id c7mr67236296pay.39.1360093111781; Tue, 05 Feb 2013 11:38:31 -0800 (PST) Received: from CMOTUM25PC ([187.210.81.114]) by mx.google.com with ESMTPS id t7sm28051142pax.17.2013.02.05.11.38.29 (version=TLSv1 cipher=RC4-SHA bits=128/128); Tue, 05 Feb 2013 11:38:30 -0800 (PST) Message-ID: From: =?iso-8859-1?Q?Efra=EDn_D=E9ctor?= To: "Kubilay Kocak" References: <5108E720.70705@gmail.com> <510A65F5.9070706@gmail.com> In-Reply-To: <510A65F5.9070706@gmail.com> Subject: Re: About kern.ipc.somaxconn and netstat Date: Tue, 5 Feb 2013 13:38:28 -0600 Organization: =?iso-8859-1?Q?HESA_T=E9cnica?= MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 8bit X-Priority: 3 X-MSMail-Priority: Normal Importance: Normal X-Mailer: Microsoft Windows Live Mail 16.4.3505.912 X-MimeOLE: Produced By Microsoft MimeOLE V16.4.3505.912 X-Gm-Message-State: ALoCoQmuhYU0BS2hHZsy1e+QgPQP8C4P2xwkydezRKiMF3wtolOTvKglx6MemmDJ0Z3KR6f6WGYg Cc: freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Feb 2013 19:38:38 -0000 Hello. Sorry for the very late answer. That is a very good command, thank you for your recommendation. All the time that I have executed it it shows "0 listen queue overflows" so I guess our configuration is working. Thank you so much. -----Mensaje original----- From: Kubilay Kocak Sent: Thursday, January 31, 2013 6:39 AM To: Efraín Déctor Cc: freebsd-stable@freebsd.org Subject: Re: About kern.ipc.somaxconn and netstat On 31/01/2013 4:54 AM, Efraín Déctor wrote: > -----Mensaje original----- From: Kubilay Kocak > Sent: Wednesday, January 30, 2013 3:25 AM > To: Efraín Déctor > Cc: freebsd-stable@freebsd.org > Subject: Re: About kern.ipc.somaxconn and netstat > > On 30/01/2013 12:26 PM, Efraín Déctor wrote: >> Hello. >> >> We have a webserver using FreeBSD, we read about tunning >> kern.ipc.somaxconn >> (http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/configtuning-kernel-limits.html) >> so the OS can handle all the connections. Is there a way to know how >> many connections are established in a certain moment?. I know about >> netstat(1) but is there any other command that we can use to know the >> exact amount of how many connections are established?. >> > This one might help: > > kern.ipc.numopensockets: Number of open sockets > > It's usefulness will depend on the granularity you require (in only, out > only, established only, etc) but it's always represented system-wide > resource consumption very well (matching observed workloads - baseline value>) > > > Thank you, it is very helpfull, using kern.ipc.numopensockets with > sockstat(1) and netstat(1) will give me a clue to tune kern.ipc.somaxconn > > Thank you all. Also, if you haven't already come across this one in your netstat travels, this one directly reports listen queue overflows: netstat -s -p tcp |grep listen -- Ta, Koobs