SOLVED: Can't SSH in after redeploying my Linode

Question

SOLVED: Can't SSH in after redeploying my Linode

networking

forum:danielhutchison 14 years, 4 months ago

If this is a noob question, apologies and please direct me to the correct info!

I delete my disk image and configuration, and redeployed. After doing so, I am unable to SSH in using Putty (or pscp at the command line). I get a "Network Error: connection refused" message.

This happened to me before when I redeployed, but eventually I started to be able to connect again. Unfortunately, I don't know what I did. Since I just redeployed, it should be a default installation and I would expect the "Getting Starting" document in the Library to be completely applicable, including using Putty to SSH in for the first time… but apparently not after a redeploy?

Thanks in advance for your help!

Daniel

Ubuntu 10.04 LTS (Latest 2.6 Stable (2.6.18.8-linode22))

5 Replies

forum:danielhutchison · Answer 1 · July 1, 2010, 3:25 p.m.

forum:danielhutchison 14 years, 4 months ago

From my personal laptop the Putty error is different: "Network error: Connection timed out"

forum:Guspaz · Answer 2 · July 1, 2010, 3:28 p.m.

forum:Guspaz 14 years, 4 months ago

You can use LISH to connect directly to the node's virtual serial port and try to see why SSH isn't running.

forum:danielhutchison · Answer 3 · July 1, 2010, 3:48 p.m.

forum:danielhutchison 14 years, 4 months ago

I used LISH to login. Unfortunately, too n00b to know what to do next. I tried running "apt-get update" per the Getting Started documentation and received multiple errors along the lines of

"Temporary failure resolving 'security.ubuntu.com'",

"Temporary failure resolving 'us.archive.ubuntu.com'",

etc.

Hope that helps. (I also opened asupport ticket where I'm duplicating this… just in case!)

Thanks again.

forum:danielhutchison · Answer 4 · July 1, 2010, 3:57 p.m.

forum:danielhutchison 14 years, 4 months ago

When rebooting from LISH, I notice a couple things that seem unusual:

/etc/rc6.d/S31umountnfs.sh: 102: cannot open /etc/mtab: No such file

and

Deconfiguring network interfaces… [FAIL]

Don't know if they are normal, or not…?

forum:danielhutchison · Answer 5 · July 1, 2010, 4:14 p.m.

forum:danielhutchison 14 years, 4 months ago

From the Linode support staff:

> Ubuntu 10.04 needs to use the Latest paravirt kernel. Can you please edit your configuration settings to the latest paravirt kernel and reboot. Please let us know how it goes!

Which worked perfectly. That's what I get for seeing "Stable" on a recent kernel and getting too smart for my own good.

Compute

Storage

Networking

Databases

Services

Developer Tools

Industries

Pricing

Community

Engage With Us

SOLVED: Can't SSH in after redeploying my Linode

5 Replies

Reply

Tips: