Date: Thu, 29 Jan 2009 13:53:47 -0900 From: Mel <fbsd.questions@rachie.is-a-geek.net> To: freebsd-questions@freebsd.org Cc: joe park <hjjp76@yahoo.com> Subject: Re: ssh login problem Message-ID: <200901291353.47467.fbsd.questions@rachie.is-a-geek.net> In-Reply-To: <745210.79886.qm@web81503.mail.mud.yahoo.com> References: <745210.79886.qm@web81503.mail.mud.yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thursday 29 January 2009 12:48:03 joe park wrote:
> $ ssh -vvv user2@192.168.1.2
> OpenSSH_4.5p1 FreeBSD-20061110, OpenSSL 0.9.8e 23 Feb 2007
> debug1: Reading configuration data /etc/ssh/ssh_config
> debug2: ssh_connect: needpriv 0
> debug1: Connecting to 192.168.1.2 [192.168.1.2] port 22.
> debug1: Connection established.
> debug1: identity file /home/user1/.ssh/identity type -1
> debug1: identity file /home/user1/.ssh/id_rsa type -1
> debug1: identity file /home/user1/.ssh/id_dsa type -1
>
> It just waits infinitely at this point. There is no other way to access
> and troubleshoot the machine B remotely (telnet is not enabled) and only
> thing I can do is call and ask for hard reset.
I/O problems on B. Disk blocks all processes needing it. Console login would
not work either. grep TIMEOUT /var/log/messages on B should provide some
insight.
--
Mel
Problem with today's modular software: they start with the modules
and never get to the software part.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200901291353.47467.fbsd.questions>