Dear Riccardo, Here is the output:
(elasticluster)vagrant@controller:~$ ssh -v -i /home/vagrant/.ssh/id_rsa [email protected] OpenSSH_6.6.1, 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 172.16.100.10 [172.16.100.10] port 22. debug1: Connection established. debug1: identity file /home/vagrant/.ssh/id_rsa type 1 debug1: identity file /home/vagrant/.ssh/id_rsa-cert type -1 debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_6.6.1p1 Ubuntu-2ubuntu2.6 debug1: Remote protocol version 2.0, remote software version OpenSSH_6.6.1p1 Ubuntu-2ubuntu2.8 debug1: match: OpenSSH_6.6.1p1 Ubuntu-2ubuntu2.8 pat OpenSSH_6.6.1* compat 0x04000000 debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug1: kex: server->client aes128-ctr [email protected] none debug1: kex: client->server aes128-ctr [email protected] none debug1: sending SSH2_MSG_KEX_ECDH_INIT debug1: expecting SSH2_MSG_KEX_ECDH_REPLY debug1: Server host key: ECDSA 2b:0c:50:94:59:04:2c:52:04:21:3b:4e:2d:3f:28:17 The authenticity of host '172.16.100.10 (172.16.100.10)' can't be established. ECDSA key fingerprint is 2b:0c:50:94:59:04:2c:52:04:21:3b:4e:2d:3f:28:17. Are you sure you want to continue connecting (yes/no)? yes Warning: Permanently added '172.16.100.10' (ECDSA) to the list of known hosts. debug1: ssh_ecdsa_verify: signature correct debug1: SSH2_MSG_NEWKEYS sent debug1: expecting SSH2_MSG_NEWKEYS debug1: SSH2_MSG_NEWKEYS received debug1: SSH2_MSG_SERVICE_REQUEST sent debug1: SSH2_MSG_SERVICE_ACCEPT received debug1: Authentications that can continue: publickey debug1: Next authentication method: publickey debug1: Offering RSA public key: /home/vagrant/.ssh/id_rsa debug1: Authentications that can continue: publickey debug1: No more authentication methods to try. Permission denied (publickey). Thanks, Ana On Sunday, 15 January 2017 10:54:40 UTC+1, Riccardo Murri wrote: > > Forgot to mention: you should run the "ssh" command on the same machine > where you run "elasticluster". > > Ciao, > R > > Il 15 gen 2017 10:15 AM, "Riccardo Murri" <[email protected] > <javascript:>> ha scritto: > >> Dear Ana: >> >> > 2017-01-14 23:06:34 controller gc3.elasticluster[2308] *DEBUG* Trying to >> > connect to host frontend001 (172.16.100.10) >> > >> > 2017-01-14 23:06:34 controller gc3.elasticluster[2308] *DEBUG* Ignoring >> > error Authentication failed. connecting to frontend001 >> >> The key message should be "Authentication failed". This seems to point >> in the direction of a wrong SSH identity file or connection user name. >> >> Can you please try running the following command and post the output here? >> >> ssh -v -i "$HOME/.ssh/id_rsa" [email protected] <javascript:> >> >> You should replace "$HOME/.ssh/id_rsa" with the actual path to the SSH >> private key that you set as parameter `user_key_private` in >> `.elasticluster/config` >> >> Ciao, >> R >> >> -- >> Riccardo Murri, Schwerzenbacherstrasse 2, CH-8606 Nänikon, Switzerland >> > -- You received this message because you are subscribed to the Google Groups "elasticluster" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
