Support Questions
Find answers, ask questions, and share your expertise
Announcements
Alert: Welcome to the Unified Cloudera Community. Former HCC members be sure to read and learn how to activate your account here.

i am installing hortonworks single node cluster on google cloud, how can i generate ssh-keygen?

Highlighted

i am installing hortonworks single node cluster on google cloud, how can i generate ssh-keygen?

Explorer
 
12 REPLIES 12
Highlighted

Re: i am installing hortonworks single node cluster on google cloud, how can i generate ssh-keygen?

Contributor

@prswamy t

Please set the following permissions and try again.

# chmod 600 ~/.ssh/id_rsa.pub
Highlighted

Re: i am installing hortonworks single node cluster on google cloud, how can i generate ssh-keygen?

Explorer

hi Sayan, chmod the id_rsa.pub, and tried but its giving permission denied error

3396-root2.png

Highlighted

Re: i am installing hortonworks single node cluster on google cloud, how can i generate ssh-keygen?

Contributor

@prswamy t

Can you add the -vvv option when you ssh, to enable verbose logging. It should help debug the problem.

Have a look into this document as well, see if this helps.

https://docs.hortonworks.com/HDPDocuments/Ambari-2.2.0.0/bk_Installing_HDP_AMB/content/_set_up_passw...

Highlighted

Re: i am installing hortonworks single node cluster on google cloud, how can i generate ssh-keygen?

Explorer

how to solve this issue? plz help me [root@hadoop ~]# ssh -vvv root@104.155.93.101 OpenSSH_5.3p1, OpenSSL 1.0.1e-fips 11 Feb 2013 debug1: Reading configuration data /etc/ssh/ssh_config debug1: Applying options for * debug2: ssh_connect: needpriv 0 debug1: Connecting to 104.155.93.101 [104.155.93.101] port 22. debug1: Connection established. debug1: permanently_set_uid: 0/0 debug1: identity file /root/.ssh/identity type -1 debug1: identity file /root/.ssh/identity-cert type -1 debug3: Not a RSA1 key file /root/.ssh/id_rsa. debug2: key_type_from_name: unknown key type '-----BEGIN' debug3: key_read: missing keytype debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug2: key_type_from_name: unknown key type '-----END' debug3: key_read: missing keytype debug1: identity file /root/.ssh/id_rsa type 1 debug1: identity file /root/.ssh/id_rsa-cert type -1 debug1: identity file /root/.ssh/id_dsa type -1 debug1: identity file /root/.ssh/id_dsa-cert type -1 debug1: identity file /root/.ssh/id_ecdsa type -1 debug1: identity file /root/.ssh/id_ecdsa-cert type -1 debug1: Remote protocol version 2.0, remote software version OpenSSH_5.3 debug1: match: OpenSSH_5.3 pat OpenSSH* debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_5.3 debug2: fd 3 setting O_NONBLOCK debug1: SSH2_MSG_KEXINIT sent debug3: Wrote 960 bytes for a total of 981 debug1: SSH2_MSG_KEXINIT received debug2: kex_parse_kexinit: diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1 debug2: kex_parse_kexinit: ssh-rsa-cert-v01@openssh.com,ssh-dss-cert-v01@openssh.com,ssh-rsa-cert-v00@openssh.com,ssh-dss-cert-v00@openssh.com,ssh-rsa,ssh-dss debug2: kex_parse_kexinit: none,zlib@openssh.com debug2: kex_parse_kexinit: debug2: kex_parse_kexinit: debug2: kex_parse_kexinit: first_kex_follows 0 debug2: kex_parse_kexinit: reserved 0 debug2: mac_setup: found hmac-md5 debug1: kex: server->client aes128-ctr hmac-md5 none debug2: mac_setup: found hmac-md5 debug1: kex: client->server aes128-ctr hmac-md5 none debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<1024<8192) sent debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP debug3: Wrote 24 bytes for a total of 1005 debug2: dh_gen_key: priv key bits set: 128/256 debug2: bits set: 478/1024 debug1: SSH2_MSG_KEX_DH_GEX_INIT sent debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY debug3: Wrote 144 bytes for a total of 1149 debug3: check_host_in_hostfile: host 104.155.93.101 filename /root/.ssh/known_hosts debug3: check_host_in_hostfile: host 104.155.93.101 filename /root/.ssh/known_hosts debug3: check_host_in_hostfile: match line 1 debug1: Host '104.155.93.101' is known and matches the RSA host key. debug1: Found key in /root/.ssh/known_hosts:1 debug2: bits set: 527/1024 debug1: ssh_rsa_verify: signature correct debug2: kex_derive_keys debug2: set_newkeys: mode 1 debug1: SSH2_MSG_NEWKEYS sent debug1: expecting SSH2_MSG_NEWKEYS debug3: Wrote 16 bytes for a total of 1165 debug2: set_newkeys: mode 0 debug1: SSH2_MSG_NEWKEYS received debug1: SSH2_MSG_SERVICE_REQUEST sent debug3: Wrote 48 bytes for a total of 1213 debug2: service_accept: ssh-userauth debug1: SSH2_MSG_SERVICE_ACCEPT received debug2: key: /root/.ssh/identity ((nil)) debug2: key: /root/.ssh/id_rsa (0x7feeffc61030) debug2: key: /root/.ssh/id_dsa ((nil)) debug2: key: /root/.ssh/id_ecdsa ((nil)) debug3: Wrote 64 bytes for a total of 1277 debug1: Authentications that can continue: publickey,gssapi-keyex,gssapi-with-mic debug3: start over, passed a different list publickey,gssapi-keyex,gssapi-with-mic debug3: preferred gssapi-keyex,gssapi-with-mic,publickey,keyboard-interactive,password debug3: authmethod_lookup gssapi-keyex debug3: remaining preferred: gssapi-with-mic,publickey,keyboard-interactive,password debug3: authmethod_is_enabled gssapi-keyex debug1: Next authentication method: gssapi-keyex

------------------------------------------------------------------------------------------

------------------------------------------------------------------------------------------

debug1: Server accepts key: pkalg ssh-rsa blen 277 debug2: input_userauth_pk_ok: SHA1 fp 66:6c:15:5d:e3:50:66:f1:8a:66:91:0f:b5:82:ec:b7:8d:a0:e3:a7 debug3: sign_and_send_pubkey: RSA 66:6c:15:5d:e3:50:66:f1:8a:66:91:0f:b5:82:ec:b7:8d:a0:e3:a7 debug1: read PEM private key done: type RSA debug3: Wrote 640 bytes for a total of 2285 debug1: Authentications that can continue: publickey,gssapi-keyex,gssapi-with-mic debug1: Trying private key: /root/.ssh/id_dsa debug3: no such identity: /root/.ssh/id_dsa debug1: Trying private key: /root/.ssh/id_ecdsa debug3: no such identity: /root/.ssh/id_ecdsa debug2: we did not send a packet, disable method debug1: No more authentication methods to try. Permission denied (publickey,gssapi-keyex,gssapi-with-mic).

Highlighted

Re: i am installing hortonworks single node cluster on google cloud, how can i generate ssh-keygen?

Contributor

@prswamy t

Please try the following and see how it goes.

# ssh -i $HOME/.ssh/id_rsa.pub -v root@hostname

Additionally, check the permissions set for the directory ~/.ssh and the files in ~/.ssh/*

Highlighted

Re: i am installing hortonworks single node cluster on google cloud, how can i generate ssh-keygen?

Contributor

@prswamy t

Sorry, just realized we were using the public key to authenticate. We should use the private key there.

# ssh -i $HOME/.ssh/id_rsa -v root@hostname

Re: i am installing hortonworks single node cluster on google cloud, how can i generate ssh-keygen?

Explorer

i run the above cmd, still facing an issue

[root@hadoop .ssh]# ssh -i $HOME/.ssh/id_rsa -v root@104.155.93.101O

penSSH_5.3p1, OpenSSL 1.0.1e-fips 11 Feb 2013debug1: Reading configuration data /etc/ssh/ssh_configdebug1: Applying options for *debug1: Connecting to 104.155.93.101 [104.155.93.101] port 22.debug1: Connection established.debug1: permanently_set_uid: 0/0debug1: identity file /root/.ssh/id_rsa type 1debug1: identity file /root/.ssh/id_rsa-cert type -1debug1: Remote protocol version 2.0, remote software version OpenSSH_5.3debug1: match: OpenSSH_5.3 pat OpenSSH*debug1: Enabling compatibility mode for protocol 2.0debug1: Local version string SSH-2.0-OpenSSH_5.3debug1: SSH2_MSG_KEXINIT sentdebug1: SSH2_MSG_KEXINIT receiveddebug1: kex: server->client aes128-ctr hmac-md5 nonedebug1: kex: client->server aes128-ctr hmac-md5 nonedebug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<1024<8192) sentdebug1: expecting SSH2_MSG_KEX_DH_GEX_GROUPdebug1: SSH2_MSG_KEX_DH_GEX_INIT sentdebug1: expecting SSH2_MSG_KEX_DH_GEX_REPLYdebug1: Host '104.155.93.101' is known and matches the RSA host key.debug1: Found key in /root/.ssh/known_hosts:1debug1: ssh_rsa_verify: signature correctdebug1: SSH2_MSG_NEWKEYS sentdebug1: expecting SSH2_MSG_NEWKEYSdebug1: SSH2_MSG_NEWKEYS receiveddebug1: SSH2_MSG_SERVICE_REQUEST sentdebug1: SSH2_MSG_SERVICE_ACCEPT receiveddebug1: Authentications that can continue: publickey,gssapi-keyex,gssapi-with-micdebug1: Next authentication method: gssapi-keyexdebug1: No valid Key exchange contextdebug1: Next authentication method: gssapi-with-micdebug1: Unspecified GSS failure.  Minor code may provide more informationCredentials cache file '/tmp/krb5cc_0' not founddebug1: Unspecified GSS failure.  Minor code may provide more information
Credentials cache file '/tmp/krb5cc_0' not found

debug1: Unspecified GSS failure.  Minor code may provide more information


debug1: Unspecified GSS failure.  Minor code may provide more information
Credentials cache file '/tmp/krb5cc_0' not found

debug1: Next authentication method: publickey
debug1: Offering public key: /root/.ssh/id_rsa
debug1: Authentications that can continue: publickey,gssapi-keyex,gssapi-with-mic
debug1: No more authentication methods to try.Permission denied (publickey,gssapi-keyex,gssapi-with-mic).
Highlighted

Re: i am installing hortonworks single node cluster on google cloud, how can i generate ssh-keygen?

Super Guru

@prswamy t

1. Command to generate ssh keys

ssh-keygen

Note - Please press enter to keep all the locations to default values.

2. Please copy ~/.ssh/id_rsa.pub to ~/.ssh/authorized_keys file

cat ~/.ssh/id_rsa.pub >> ~/.ssh/authorized_keys

3. Please make sure that you have:

3.1. You have 700 permissions on ~/.ssh directory

3.2. 600 permissions on ~/.ssh/authorized_keys file

3.3. 600 to ~/.ssh/id_rsa

3.4. 644 to ~/.ssh/id_rsa.pub

Highlighted

Re: i am installing hortonworks single node cluster on google cloud, how can i generate ssh-keygen?

Explorer

Hi Kuldeep, i done above all steps but i got permission denied error, plz help me how to solve this issue

3431-14-2.png

Don't have an account?
Coming from Hortonworks? Activate your account here