Not able to SSH from my local machine to the VM

Balaji Purushothaman

unread,

Feb 17, 2016, 12:39:27 PM2/17/16

to cloudlab-users

Greetings,

Not able to ssh from my local machine to the VMs in the Cloudlab.

Project - Cord-testdrive using openstack profile.

I am able to access the ctl and compute nodes from the browser.

I was trying to do ssh using the following command

ssh -p 22 mylog...@pc-c220m4-r03-20.wisc.cloudlab.us

I used the randomly generated password mentioned in the Instructions.

But able to ping the VMs from my local machine.

I am not sure what i am missing here.

What is the login and Password I should use for SSH ??

Can someone help me in this regards.

Best Regards,
Balaji

Log:

$ssh -v -p 22 myl...@ctl.balacloud2.cord-testdrive-pg0.wisc.cloudlab.us
OpenSSH_6.7p1 Ubuntu-5ubuntu1.3, OpenSSL 1.0.1f 6 Jan 2014
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 19: Applying options for *
debug1: Connecting to ctl.balacloud2.cord-testdrive-pg0.wisc.cloudlab.us [128.104.222.70] port 22.
debug1: Connection established.
debug1: identity file /home/mylocallogin/.ssh/id_rsa type 1
debug1: key_load_public: No such file or directory
debug1: identity file /home/mylocallogin/.ssh/id_rsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/mylocallogin/.ssh/id_dsa type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/mylocallogin/.ssh/id_dsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/mylocallogin/.ssh/id_ecdsa type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/mylocallogin/.ssh/id_ecdsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/mylocallogin/.ssh/id_ed25519 type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/mylocallogin/.ssh/id_ed25519-cert type -1
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_6.7p1 Ubuntu-5ubuntu1.3
debug1: Remote protocol version 2.0, remote software version OpenSSH_6.7p1 Ubuntu-5ubuntu1.3
debug1: match: OpenSSH_6.7p1 Ubuntu-5ubuntu1.3 pat OpenSSH* compat 0x04000000
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: server->client aes128-ctr umac-...@openssh.com none
debug1: kex: client->server aes128-ctr umac-...@openssh.com none
debug1: sending SSH2_MSG_KEX_ECDH_INIT
debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
debug1: Server host key: RSA 1f:f4:d6:18:e3:4d:18:04:89:19:af:90:53:dd:90:0b
debug1: Host 'ctl.balacloud2.cord-testdrive-pg0.wisc.cloudlab.us' is known and matches the RSA host key.
debug1: Found key in /home/mylocallogin/.ssh/known_hosts:41
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug1: Roaming not allowed by server
debug1: SSH2_MSG_SERVICE_REQUEST sent
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: Authentications that can continue: publickey,password
debug1: Next authentication method: publickey
debug1: Offering RSA public key: /home/mylocallogin/.ssh/id_rsa
debug1: Authentications that can continue: publickey,password
debug1: Trying private key: /home/mylocallogin/.ssh/id_dsa
debug1: Trying private key: /home/mylocallogin/.ssh/id_ecdsa
debug1: Trying private key: /home/mylocallogin/.ssh/id_ed25519
debug1: Next authentication method: password
myl...@ctl.balacloud2.cord-testdrive-pg0.wisc.cloudlab.us's password:
debug1: Authentications that can continue: publickey,password
Permission denied, please try again.
myl...@ctl.balacloud2.cord-testdrive-pg0.wisc.cloudlab.us's password:
debug1: Authentications that can continue: publickey,password
Permission denied, please try again.
myl...@ctl.balacloud2.cord-testdrive-pg0.wisc.cloudlab.us's password:
debug1: Authentications that can continue: publickey,password
debug1: No more authentication methods to try.
Permission denied (publickey,password).

Leigh Stoller

unread,

Feb 17, 2016, 12:47:02 PM2/17/16

to Balaji Purushothaman, cloudlab-users

> Greetings,
>
> Not able to ssh from my local machine to the VMs in the Cloudlab.

Hi, have you uploaded the public part of your private keys via the
web interface? Click on the Actions menu, then Manage SSH Keys. But
you will want to see yesterday's message to cloudlab-users about
adding keys after your experiment has been started.

Leigh

David M. Johnson

unread,

Feb 17, 2016, 12:54:56 PM2/17/16

to cloudla...@googlegroups.com

On 02/17/16 10:39, Balaji Purushothaman wrote:
> Greetings,
>
> Not able to ssh from my local machine to the VMs in the Cloudlab.
>
> Project - Cord-testdrive using openstack profile.
>
> I am able to access the ctl and compute nodes from the browser.
>
> I was trying to do ssh using the following command
>
> ssh -p 22 mylog...@pc-c220m4-r03-20.wisc.cloudlab.us

> <ssh://bala...@pc-c220m4-r03-20.wisc.cloudlab.us:22/>

That is an ssh command that will connect to one of the physical machines
in your experiment, not to a VM hosted on them. You cannot login to
Cloudlab physical machines via password; you must use your ssh keypair.

The random password you mention is for use when logging into the
Openstack Dashboard as the 'admin' user, or for password login to
OpenStack VMs as the 'ubuntu' user.

If you are trying to access OpenStack VMs you have created via the
Dashboard, you'll need to assign them a floating IP. When you create
them, you should also choose the ssh key name that corresponds to your
ssh keypair -- then you can login without typing a password, which is
best. But if you didn't do that, you can still login to the VMs using
the 'ubuntu' user and the random admin password, as the instructions say.

> I used the randomly generated password mentioned in the Instructions.
>
> But able to ping the VMs from my local machine.
>
> I am not sure what i am missing here.
>
> What is the login and Password I should use for SSH ??
>
> Can someone help me in this regards.
>
> Best Regards,
> Balaji

David

David M. Johnson

unread,

Feb 17, 2016, 2:27:12 PM2/17/16

to Balaji Purushothaman, cloudlab-users

On 02/17/16 12:09, Balaji Purushothaman wrote:
> Thanks for the quick reply David,

Sure, please keep cloudlab-users cc'd on your replies...

> To clarify, I am trying to ssh the physical machines in my experiment
> from my local machine.
>
> In my case, trying to access the controller
> ctl.balacloud2.cord-testdrive-pg0.wisc.cloudlab.us
> <http://ctl.balacloud2.cord-testdrive-pg0.wisc.cloudlab.us>
>
> As you mentioned in your reply, password doesn't not work so I added my
> local machines public key to the
> ctl.balacloud2.cord-testdrive-pg0.wisc.cloudlab.us
> <http://ctl.balacloud2.cord-testdrive-pg0.wisc.cloudlab.us> through
> "Actions/ Manage SSH keys" submenu.

But if you added a new public key since you created your experiment,
you'll need to terminate your current experiment and instantiate a new
one to get the new key on experiment nodes. This is part of the other
mail Leigh sent to you earlier where he mentioned you should look at
yesterday's message about how Cloudlab currently handles SSH pubkeys
(see https://groups.google.com/forum/#!topic/cloudlab-users/_zQhxso0Qcw
for the full message thread). We hope to support pubkey updates at
nodes soon.

David

> I tried with different login in name such ubuntu/myloginname etc. But
>
> still i can't do ssh to the virtual machine.
>
> But as i said earlier, i was able to ping.
>
> $ssh -v -p 22
> logi...@ctl.balacloud2.cord-testdrive-pg0.wisc.cloudlab.us
> <mailto:logi...@ctl.balacloud2.cord-testdrive-pg0.wisc.cloudlab.us>

> OpenSSH_6.7p1 Ubuntu-5ubuntu1.3, OpenSSL 1.0.1f 6 Jan 2014
> debug1: Reading configuration data /etc/ssh/ssh_config
> debug1: /etc/ssh/ssh_config line 19: Applying options for *
> debug1: Connecting to ctl.balacloud2.cord-testdrive-pg0.wisc.cloudlab.us

> <http://ctl.balacloud2.cord-testdrive-pg0.wisc.cloudlab.us>

> [128.104.222.70] port 22.
> debug1: Connection established.

> debug1: identity file /home/localLoginName/.ssh/id_rsa type 1