Date: Fri, 02 Jul 2010 13:03:37 +0100 From: Matthew Seaman <m.seaman@infracaninophile.co.uk> To: John Almberg <jalmberg@identry.com> Cc: Bas Smeelen <b.smeelen@ose.nl>, freebsd-questions@freebsd.org Subject: Re: ssh_exchange_identification: Connection closed by remote host Message-ID: <4C2DD599.5030101@infracaninophile.co.uk> In-Reply-To: <4C2DD130.5070508@identry.com> References: <4C2DC4FC.7070004@identry.com> <AANLkTinNCKfwgHf-ha0cys9cdTSk-rcYznWO3zcK2r0H@mail.gmail.com> <4C2DCD58.3070103@identry.com> <4C2DCE9B.4090306@ose.nl> <4C2DD130.5070508@identry.com>
next in thread | previous in thread | raw e-mail | index | archive | help
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 02/07/2010 12:44:48, John Almberg wrote:
> I'm on the console, now. Looks like a swapspace problem...
>
> The first terminal is scrolling by the swapspace messages really fast
> (it kills httpd, but then starts again).
> I tried logging in on the 2nd and 3rd virtual console, but hangs after I
> type root - never prompts for password.
>
> Is there anything I can do besides rebooting?
>
> 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.
Cheers,
Matthew
- --
Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard
Flat 3
PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate
JID: matthew@infracaninophile.co.uk Kent, CT11 9PW
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.14 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAkwt1ZkACgkQ8Mjk52CukIwRVgCfXTHymgNMOwMN69H5NxwdTUsV
OjwAn2TPAgiHgW94+4swodm4mQbKhYIg
=iWlM
-----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4C2DD599.5030101>