From owner-freebsd-hackers@freebsd.org Fri Dec 11 21:00:30 2015 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CB4FC9D7136 for ; Fri, 11 Dec 2015 21:00:30 +0000 (UTC) (envelope-from nparhar@gmail.com) Received: from mail-pa0-x235.google.com (mail-pa0-x235.google.com [IPv6:2607:f8b0:400e:c03::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A36771F9E for ; Fri, 11 Dec 2015 21:00:30 +0000 (UTC) (envelope-from nparhar@gmail.com) Received: by pabur14 with SMTP id ur14so71034921pab.0 for ; Fri, 11 Dec 2015 13:00:30 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:date:from:to:cc:subject:message-id:mail-followup-to :references:mime-version:content-type:content-disposition :in-reply-to:user-agent; bh=1TBH1T3s1OcK9v4a8KnCEIdeY3YEfFP8sa/10feNzXQ=; b=XoQsoxoTRYJeJ4zKkYlSrcYZmXGMIiBf9fgirRgOEvsYp8KiAR8C+ObiTamtyBfJko NukjGmQZulgAMIpOzau5f02ayyjAxlt+afuMFC1c3o8DED3dYNFeroR848r9yrVqbsHX 1v8ywTJ5hFiiJCtZCcKAA4z1u6mnr1VSiW8DMaNdHmkaRkqUaHtCMd+HzwCAGupSItEE XuLEzeLmXWLJP7jHDXE+Sa0kd5omr03fCsBabViD8MQOm4Z3jT9D2GEw9/PTkRwuZ3NZ jg7tVaD72fi/LE3NsCuOQY9ZyuDBRfbi4KZ2s+ifkTsjnFpwAcP5LAfFVviw/OJxS6nS Gtuw== X-Received: by 10.66.155.8 with SMTP id vs8mr16935318pab.18.1449867630271; Fri, 11 Dec 2015 13:00:30 -0800 (PST) Received: from nparhar-pc (nat-198-95-226-228.netapp.com. [198.95.226.228]) by smtp.gmail.com with ESMTPSA id c20sm26994455pfd.17.2015.12.11.13.00.28 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 11 Dec 2015 13:00:28 -0800 (PST) Sender: Navdeep Parhar Date: Fri, 11 Dec 2015 13:00:24 -0800 From: Navdeep Parhar To: Steve Kargl Cc: freebsd-hackers@freebsd.org Subject: Re: sonewconn issue? Message-ID: <20151211210024.GA2613@nparhar-pc> Mail-Followup-To: Steve Kargl , freebsd-hackers@freebsd.org References: <20151211160354.GA1005@troutmask.apl.washington.edu> <566B06B0.5060809@FreeBSD.org> <20151211193034.GA3100@troutmask.apl.washington.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20151211193034.GA3100@troutmask.apl.washington.edu> User-Agent: Mutt/1.5.23 (2014-03-12) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Dec 2015 21:00:30 -0000 On Fri, Dec 11, 2015 at 11:30:34AM -0800, Steve Kargl wrote: > On Fri, Dec 11, 2015 at 09:24:00AM -0800, Navdeep Parhar wrote: > > On 12/11/2015 08:03, Steve Kargl wrote: > > > Last night my system became wedged. Inspection of/var/log/messages > > > revealed 290 messages of the form > > > > > > Dec 10 19:27:49 troutmask kernel: sonewconn: pcb 0xfffff8000a76c4b0: > > > Listen queue overflow: 16 already in queue awaiting > > > acceptance (1 occurrences) > > > > > > During this time, I could connect to the webserver on the system. > > > ssh into the box would connect, but I never got an actaul session. > > > This morning I found the console unresponse. > > > > > > Any suggestions for identifying the rogue process? > > > > > > > Try "netstat -aLnp tcp" and look at the "Listen" column to see which > > sockets are backlogged. Then "sockstat -4l" to identify the process > > that owns the socket. > > > > Thanks for the suggestions. I'll keep this in mind if the > problem re-appears. Unfortunately, I had no access to the > box. ssh didn't work. console was unresponse. No serial > console. If you can get into ddb after this happens then you can look up the 4 tuple from the inpcb (its address is in the message displayed by sonewconn). The local port is probably the interesting part if it's a server. db> show inpcb db> show tcpcb Regards, Navdeep > > I forgot to mention that this is FreeBSD-current circa > Nov 9th, 2015. The box gets updated about once a month > or so. > > -- > Steve