-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sun, Jan 10, 2016 at 07:17:26PM +0000, Sharon Kimble wrote: > <to...@tuxteam.de> writes: > > > On Sun, Jan 10, 2016 at 04:27:13PM +0000, Sharon Kimble wrote: > > > > [...] > > > >> But I can't ssh into it using 'ssh foo@fooserver'. Every time that I try > >> it appears not to connect, just leaving a blank access line and my ram > >> is gradually being eaten away which makes this machine slow down! Not > >> good really. I can access with 'ssh -v foo@fooserver' which shows the > >> remote ssh log, but aren't able to do anything else with it. And I can > >> ping it, but haven't been able to do much else. > > > > Let's recap: you can "ping fooserver" and it answers, but "ssh > > foo@fooserver" > > is dead --> have you made sure that fooserver has an ssh daemon installed > > and running? (in Debian that would be the package openssh-server). > > > > I don't understand a couple of things: > > > >> [...] my ram > >> is gradually being eaten away which makes this machine slow down! > > > > which one: the fooserver or the client you are trying to access it > > from? Most probably not related to your ssh problem, so it makes > > sense to tackle that separately anyway. > > On *this* machine only. > > > >> [...] I can access with 'ssh -v foo@fooserver' which shows the > >> remote ssh log, but aren't able to do anything else with it. And I can > > > > You can access it with "ssh -v ..." and not with "ssh ..."? That dosn't > > make sense for me. Is that possible that you are only seeing the attempt > > on your side? What's the output of this "ssh -v ..."? > > --8<---------------cut here---------------start------------->8--- > ssh -v boztu@norwich > OpenSSH_6.7p1 Debian-5, OpenSSL 1.0.1k 8 Jan 2015 > debug1: Reading configuration data /home/boudiccas/.ssh/config > debug1: /home/boudiccas/.ssh/config line 1: Applying options for norwich > debug1: Reading configuration data /etc/ssh/ssh_config > debug1: /etc/ssh/ssh_config line 19: Applying options for * > debug1: Executing proxy command: exec ssh userext@norwich nc norwich 22
Aha -- this looks suspicious: there seems to be, in your .ssh/config (line 19) a line, which basically says "to access any host, you have to hop via norwich) -- which ssh is dutifully trying... to access norwich. I don't know whether the ssh client has any loop protection for that case: this could explain the memory issue. I take back my last mumbling about "separate issues", it seems :-) OK. I'd recommend, for a first try either commenting out this line 19 in .ssh/config or even moving away .ssh/config altogether (put in a safe place, you'll most probably need it later!). Once you can access norwich, you/we can try to put the useful parts of your .ssh/config back. Regards - -- tomás -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlaSuFAACgkQBcgs9XrR2kbpdACfUll2290hbfF+7kL/KTqDeXdP WrgAn0KZ9DCQyRYy2eHn4gjeVzRESYyy =EV8F -----END PGP SIGNATURE-----
