From owner-freebsd-stable@FreeBSD.ORG Thu Nov 18 03:19:22 2004 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 21D7016A4CE; Thu, 18 Nov 2004 03:19:22 +0000 (GMT) Received: from carver.gumbysoft.com (carver.gumbysoft.com [66.220.23.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0454843D46; Thu, 18 Nov 2004 03:19:22 +0000 (GMT) (envelope-from dwhite@gumbysoft.com) Received: by carver.gumbysoft.com (Postfix, from userid 1000) id F190872DD4; Wed, 17 Nov 2004 19:19:21 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by carver.gumbysoft.com (Postfix) with ESMTP id EC84B72DCB; Wed, 17 Nov 2004 19:19:21 -0800 (PST) Date: Wed, 17 Nov 2004 19:19:21 -0800 (PST) From: Doug White To: Zoltan Frombach In-Reply-To: <000401c4c95a$e6287ff0$e001a8c0@p4> Message-ID: <20041117191632.Y29048@carver.gumbysoft.com> References: <000401c4c95a$e6287ff0$e001a8c0@p4> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-stable@freebsd.org cc: simon@FreeBSD.org Subject: Re: sshd stops accepting connections X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Nov 2004 03:19:22 -0000 On Sat, 13 Nov 2004, Zoltan Frombach wrote: > > Today I suddenly couldn't log in via ssh to a server I upgraded to > > FreeBSD 5.3-RELEASE 4 days ago. When I tried connect to port 22 using > > telnet(1) the following just happend: > > > > [simon at zaphod:~] telnet 192.168.3.2 22 > > Trying 192.168.3.2... > > Connected to jet.nitro.dk. > > Escape character is '^]'. > > Connection closed by foreign host. > > > > The servar had been running FreeBSD 5.2.1 for a while without > > problems. ... > > I had the exact same problem yesterday!! I installad FreeBSD 5.3-RELEASE [...] > Nov 11 13:45:10 www kernel: ad0: WARNING - WRITE_DMA interrupt was seen but > timeout fired LBA=2928095 > Nov 11 13:49:52 www kernel: maxproc limit exceeded by uid 0, please see > tuning(7) and login.conf(5). This is the kicker -- sshd couldn't fork because somethnig went berzerk. > Nov 11 13:49:54 www kernel: Limiting closed port RST response from 212 to > 200 packets/sec This looks a lot like a SYN flood on some daemon that fork()s each connection but doesn't have any limits. The disk error could certainly be related, although I'm not sure why it would cause something to spike up and hit maxproc. -- Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org