From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: To: 9fans@9fans.net Date: Mon, 19 Apr 2010 02:23:52 +0200 From: cinap_lenrek@gmx.de In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="upas-mbwxfaadlspqvtbbqhczknfumc" Subject: Re: [9fans] multiple pings cause panic Topicbox-Message-UUID: 07de1a44-ead6-11e9-9d60-3106f5b1d025 This is a multi-part message in MIME format. --upas-mbwxfaadlspqvtbbqhczknfumc Content-Disposition: inline Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit i dont think you need that. devip calls a protocol specific garbage collector procedure that will close these hanging connections for you if it runs out of connections. /sys/src/9/ip/tcp.c:/^tcpgc well, the test is a little bit more complicated as it takes a minimum inactivity time into account. made a patch that changes the panic into a print: /n/sources/patch/devip-allconvused-panic -- cinap --upas-mbwxfaadlspqvtbbqhczknfumc Content-Type: message/rfc822 Content-Disposition: inline Return-Path: <9fans-bounces+cinap_lenrek=gmx.de@9fans.net> X-Flags: 0000 Delivered-To: GMX delivery to cinap_lenrek@gmx.de Received: (qmail invoked by alias); 19 Apr 2010 00:02:35 -0000 Received: from gouda.swtch.com (EHLO gouda.swtch.com) [67.207.142.3] by mx0.gmx.net (mx045) with SMTP; 19 Apr 2010 02:02:35 +0200 Received: from localhost ([127.0.0.1] helo=gouda.swtch.com) by gouda.swtch.com with esmtp (Exim 4.69) (envelope-from <9fans-bounces@9fans.net>) id 1O3ePF-0008NM-Nn; Mon, 19 Apr 2010 00:00:05 +0000 Received: from ladd.quanstro.net ([69.55.170.73]) by gouda.swtch.com with esmtp (Exim 4.69) (envelope-from ) id 1O3ePB-0008NH-Je for 9fans@9fans.net; Mon, 19 Apr 2010 00:00:02 +0000 From: erik quanstrom Date: Sun, 18 Apr 2010 19:52:04 -0400 To: 9fans@9fans.net Message-ID: In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Subject: Re: [9fans] multiple pings cause panic X-BeenThere: 9fans@9fans.net X-Mailman-Version: 2.1.10 Precedence: list Reply-To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> List-Id: Fans of the OS Plan 9 from Bell Labs <9fans.9fans.net> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: 9fans-bounces@9fans.net Errors-To: 9fans-bounces+cinap_lenrek=gmx.de@9fans.net X-GMX-Antivirus: 0 (no virus found) X-GMX-Antispam: 0 (Sender is in whitelist: quanstro@quanstro.net); Detail=5D7Q89H36p4L00VTXC6D4q0N+AH0PUCnetdm6+jp8LEcjapYokC+U3v/81HGGfOKx+H8Q hsonGcD8c5YdwbU6cC26m7RS/IsV1; X-GMX-UID: 9fCpH5tBbXBtKJo1kTQ2DDEqLyUmZcjX On Sun Apr 18 16:41:17 EDT 2010, geoff@plan9.bell-labs.com wrote: > There are limits on the number of concurrent conversations per > protocol. For UDP, it's currently 1024, for TCP it's currently 1024 > on terminals and 4096 on cpu servers. For ICMP, it's currently 128; > you may want to raise that. To find the current limits, > > grep '>nc = ' /sys/src/9/ip/*.c it's surprisingly easy to burn through connections since connections can hang out in Finwait2 for a long time, burning up packets and connections: ; cpu -c 'cd /net.alt/tcp; x=1??? echo $x($#x)' 1175 i haven't had time to take a look at this issue, but i wonder if acks during Finwait2 are resetting the timer. this is definately related to smtp &/| pop. i sometimes use this script as hostowner to clear out these connections x=`{grep -l Finwait2 */status|sed 's:/status::g'} for(i in $x) if(~ `{cat $i^/local} *!110 *!25) >$i^/ctl echo hangup - erik --upas-mbwxfaadlspqvtbbqhczknfumc--