From owner-freebsd-questions@FreeBSD.ORG Fri Jul 2 12:09:53 2010 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 199D61065670 for ; Fri, 2 Jul 2010 12:09:53 +0000 (UTC) (envelope-from jalmberg@identry.com) Received: from smtp-gw30.mailanyone.net (smtp-gw30.mailanyone.net [208.70.128.56]) by mx1.freebsd.org (Postfix) with ESMTP id D38D38FC1F for ; Fri, 2 Jul 2010 12:09:52 +0000 (UTC) Received: from mailanyone.net by smtp-gw30.mailanyone.net with esmtpa (MailAnyone extSMTP jalmberg@identry.com) id 1OUf43-0007UJ-MR for freebsd-questions@freebsd.org; Fri, 02 Jul 2010 07:09:52 -0500 Message-ID: <4C2DD70F.8040004@identry.com> Date: Fri, 02 Jul 2010 08:09:51 -0400 From: John Almberg User-Agent: Postbox 1.1.5 (Macintosh/20100613) MIME-Version: 1.0 To: freebsd-questions@freebsd.org References: <4C2DC4FC.7070004@identry.com> <4C2DCD58.3070103@identry.com> <4C2DCE9B.4090306@ose.nl> <4C2DD130.5070508@identry.com> <4C2DD599.5030101@infracaninophile.co.uk> In-Reply-To: <4C2DD599.5030101@infracaninophile.co.uk> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Re: ssh_exchange_identification: Connection closed by remote host X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Jul 2010 12:09:53 -0000 >> On that subject... does Ctrl-Alt-Del initiate an orderly shutdown? >> > > If you can't log in -- even on the console -- then rebooting is really > your only option. Ctrl-Alt-Del should bring the system down cleanly if > you haven't disabled that functionality. Otherwise, just toggle the power. > > The symptoms you're seeing could well be due to filesystem problems or > to some filesystem filling up (/tmp is a prime suspect) or due to > running out of memory+swap. Some sort of memory leak sounds pretty > likely actually. > > Probably best to bring the system up in single user mode and run fsck on > all the filesystems manually -- that will show if you've got h/w > problems with drives and possibly with disk controllers or cabling too. > Then check for overfull filesystems. You may not find any -- rebooting > can clear a number of conditions where disk space is not released back > to the OS properly after use. You may or may not find any clues as to > what went wrong in the system logs. In the absence of any other clues, > the only option is to monitor the server closely and wait for something > similar to happen again. Hopefully if there is a next time, you'll be > able to catch it and fix the underlying problem before it takes the > machine out a second time. > > Yes, I can't log in. I get a login prompt, but no password prompt. I'm going to try ctrl-alt-del and see what happens. Crossing fingers...