From owner-freebsd-questions@FreeBSD.ORG Wed Apr 19 19:11:52 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8C36216A400 for ; Wed, 19 Apr 2006 19:11:52 +0000 (UTC) (envelope-from reitz@eecs.cwru.edu) Received: from beta.eecs.cwru.edu (beta.EECS.CWRU.Edu [129.22.150.110]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1D20743D46 for ; Wed, 19 Apr 2006 19:11:51 +0000 (GMT) (envelope-from reitz@eecs.cwru.edu) Received: from bender ([::ffff:129.22.151.243]) (TLS: TLSv1/SSLv3,168bits,DES-CBC3-SHA) by beta.eecs.cwru.edu with esmtp; Wed, 19 Apr 2006 15:11:51 -0400 id 000ABEF5.44468B77.000010F9 Date: Wed, 19 Apr 2006 15:11:26 -0400 (EDT) From: Andy Reitz X-X-Sender: reitz@bender To: Ben and Jen In-Reply-To: <000801c663c4$3370d410$0200a8c0@WINDOWS> Message-ID: References: <000801c663c4$3370d410$0200a8c0@WINDOWS> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: freebsd-questions@freebsd.org Subject: Re: SYSTEM HANG - NATD running FINE 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: Wed, 19 Apr 2006 19:11:52 -0000 On Wed, 19 Apr 2006, Ben and Jen wrote: > My system has recently "locked up" after 65 days uptime, running only > natd for my local network. Natd still works fine and routes information > properly - but I am no longer able to telnet or login to my machine even > from a local console(alt f1-fx). After I enter my root or user name at > the login - it just hangs there. When I telnet in, it does not even > prompt me with a login. > > Anybody ever had this problem before? Any suggestions on how to recover > my system without rebooting? Hi Ben, Since you are unable to get a shell, it is unlikely that you will be able to recover without rebooting. However, you can try dropping into the online Kernel debugger, to try and get more information about what is going on: http://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug-online-ddb.html I think from there you can force a panic, which could provide you with some post-mortem information to go over: http://www.onlamp.com/pub/a/bsd/2002/03/21/Big_Scary_Daemons.html Good luck, -Andy.