Date: Fri, 11 Dec 2015 23:30:42 +0200 From: Konstantin Belousov <kostikbel@gmail.com> To: Steve Kargl <sgk@troutmask.apl.washington.edu>, freebsd-hackers@freebsd.org Subject: Re: sonewconn issue? Message-ID: <20151211213042.GK82577@kib.kiev.ua> In-Reply-To: <20151211210024.GA2613@nparhar-pc> References: <20151211160354.GA1005@troutmask.apl.washington.edu> <566B06B0.5060809@FreeBSD.org> <20151211193034.GA3100@troutmask.apl.washington.edu> <20151211210024.GA2613@nparhar-pc>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Dec 11, 2015 at 01:00:24PM -0800, Navdeep Parhar wrote: > 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 <addr> > db> show tcpcb <inp_pcb from above> > > 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. I believe that the network messages are the consequences of some deadlock which stopped the usermode. If you do get at the ddb prompt, start with the ps command.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20151211213042.GK82577>