[Rocks] [Rocks-Discuss] problem with ssh key only for a single user

[Luca Nannipieri]

I have a Rocks 5.1 (V.I) and for only one user I always get a password
prompt when launching a job or logging into the compute node.
Every time I do the following:

$ ssh-agent $SHELL
$ ssh-add

but the next login I do again the above procedure for password prompt
problem.

For only one user, for the other users there isn't this problem.

--
Ing. Luca Nannipieri
Istituto Nazionale di Geofisica e Vulcanologia
Sezione di Pisa
Via della Faggiola, 32 - 56126 Pisa - Italy
Tel. +39 050 8311926
fax: +39 050 8311942
http://www.pi.ingv.it/Pagine_personali/nannipieri.html

--
You received this message because you are subscribed to the Google Groups "Rocks Clusters" group.
To post to this group, send email to rocks-c...@googlegroups.com.
To unsubscribe from this group, send email to rocks-cluster...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/rocks-clusters?hl=en.

[Bart Brashers]

> I have a Rocks 5.1 (V.I) and for only one user I always get a password
> prompt when launching a job or logging into the compute node.
> Every time I do the following:
>
> $ ssh-agent $SHELL
> $ ssh-add
>
> but the next login I do again the above procedure for password prompt
> problem.
>
> For only one user, for the other users there isn't this problem.

Check permissions on /home/$user and /home/$user/.ssh (and contents).

Try "ssh -v compute-0-0" and read the output to see why it fails to use
the SSH keys. Try "ssh -vv compute-0-0" if you don't find anything.

Re-generate the SSH keys: "rm .ssh/id_rsa* ; ssh-keygen -t rsa" and
accept the defaults.

Bart






This message contains information that may be confidential, privileged or otherwise protected by law from disclosure. It is intended for the exclusive use of the Addressee(s). Unless you are the addressee or authorized agent of the addressee, you may not review, copy, distribute or disclose to anyone the message or any information contained within. If you have received this message in error, please contact the sender by electronic reply to em...@environcorp.com and immediately delete all copies of the message.

[David M Noriega]

I am having a similar issues though related to X forwarding, again
this only affects one user. They login with ssh -Y yet qlogin doesnt
work in regards to xforwarding:

-bash-3.2$ qlogin
Your job 683 ("QLOGIN") has been submitted
waiting for interactive job to be scheduled ...
Your interactive job 683 has been successfully scheduled.
Establishing /opt/gridengine/bin/rocks-qlogin.sh session to host
compute-2-3.local ...
Warning: untrusted X11 forwarding setup failed: xauth key data not generated
Warning: No xauth data; using fake authentication data for X11 forwarding.
Last login: Thu Apr 29 15:06:42 2010 from cheetah.local
Rocks Compute Node
Rocks 5.3 (Rolled Tacos)
Profile built 17:30 22-Apr-2010

Kickstarted 17:39 22-Apr-2010
-bash-3.2$ matlab
X11 connection rejected because of wrong authentication.


-bash-3.2$ ssh -Y -vv compute-1-1
OpenSSH_4.3p2, OpenSSL 0.9.8e-fips-rhel5 01 Jul 2008
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Applying options for *
debug2: ssh_connect: needpriv 0
debug1: Connecting to compute-1-1 [192.168.255.242] port 22.
debug1: Connection established.
debug1: identity file /home/daniel.polhamus/.ssh/identity type 0
debug2: key_type_from_name: unknown key type '-----BEGIN'
debug2: key_type_from_name: unknown key type '-----END'
debug1: identity file /home/daniel.polhamus/.ssh/id_rsa type 1
debug2: key_type_from_name: unknown key type '-----BEGIN'
debug2: key_type_from_name: unknown key type '-----END'
debug1: identity file /home/daniel.polhamus/.ssh/id_dsa type 2
debug1: loaded 3 keys
debug1: Remote protocol version 2.0, remote software version OpenSSH_4.3
debug1: match: OpenSSH_4.3 pat OpenSSH*
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_4.3
debug2: fd 4 setting O_NONBLOCK
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug2: kex_parse_kexinit:
diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1
debug2: kex_parse_kexinit: ssh-rsa,ssh-dss
debug2: kex_parse_kexinit:
aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour128,arcfour256,arcfour,aes192-cbc,aes256-cbc,rijnda...@lysator.liu.se,aes128-ctr,aes192-ctr,aes256-ctr
debug2: kex_parse_kexinit:
aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour128,arcfour256,arcfour,aes192-cbc,aes256-cbc,rijnda...@lysator.liu.se,aes128-ctr,aes192-ctr,aes256-ctr
debug2: kex_parse_kexinit:
hmac-md5,hmac-sha1,hmac-ripemd160,hmac-ri...@openssh.com,hmac-sha1-96,hmac-md5-96
debug2: kex_parse_kexinit:
hmac-md5,hmac-sha1,hmac-ripemd160,hmac-ri...@openssh.com,hmac-sha1-96,hmac-md5-96
debug2: kex_parse_kexinit: none,zl...@openssh.com,zlib
debug2: kex_parse_kexinit: none,zl...@openssh.com,zlib
debug2: kex_parse_kexinit:
debug2: kex_parse_kexinit:
debug2: kex_parse_kexinit: first_kex_follows 0
debug2: kex_parse_kexinit: reserved 0
debug2: kex_parse_kexinit:
diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1
debug2: kex_parse_kexinit: ssh-rsa,ssh-dss
debug2: kex_parse_kexinit:
aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour128,arcfour256,arcfour,aes192-cbc,aes256-cbc,rijnda...@lysator.liu.se,aes128-ctr,aes192-ctr,aes256-ctr
debug2: kex_parse_kexinit:
aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour128,arcfour256,arcfour,aes192-cbc,aes256-cbc,rijnda...@lysator.liu.se,aes128-ctr,aes192-ctr,aes256-ctr
debug2: kex_parse_kexinit:
hmac-md5,hmac-sha1,hmac-ripemd160,hmac-ri...@openssh.com,hmac-sha1-96,hmac-md5-96
debug2: kex_parse_kexinit:
hmac-md5,hmac-sha1,hmac-ripemd160,hmac-ri...@openssh.com,hmac-sha1-96,hmac-md5-96
debug2: kex_parse_kexinit: none,zl...@openssh.com
debug2: kex_parse_kexinit: none,zl...@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_init: found hmac-md5
debug1: kex: server->client aes128-cbc hmac-md5 none
debug2: mac_init: found hmac-md5
debug1: kex: client->server aes128-cbc hmac-md5 none
debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<1024<8192) sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP
debug2: dh_gen_key: priv key bits set: 139/256
debug2: bits set: 501/1024
debug1: SSH2_MSG_KEX_DH_GEX_INIT sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY
Warning: Permanently added 'compute-1-1' (RSA) to the list of known hosts.
debug2: bits set: 509/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
debug2: set_newkeys: mode 0
debug1: SSH2_MSG_NEWKEYS received
debug1: SSH2_MSG_SERVICE_REQUEST sent
debug2: service_accept: ssh-userauth
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug2: key: /home/daniel.polhamus/.ssh/id_rsa (0x2b407f3954b0)
debug2: key: /home/daniel.polhamus/.ssh/id_dsa (0x2b407f395ab0)
debug1: Authentications that can continue: publickey,gssapi-with-mic,password
debug1: Next authentication method: publickey
debug1: Offering public key: /home/daniel.polhamus/.ssh/id_rsa
debug2: we sent a publickey packet, wait for reply
debug1: Server accepts key: pkalg ssh-rsa blen 149
debug2: input_userauth_pk_ok: SHA1 fp
8a:bb:e1:df:0a:58:05:fa:f5:61:79:4f:0e:98:a0:63:9c:d4:7d:de
debug1: read PEM private key done: type RSA
debug1: Authentication succeeded (publickey).
debug1: channel 0: new [client-session]
debug2: channel 0: send open
debug1: Entering interactive session.
debug2: callback start
debug2: x11_get_proto: /usr/bin/xauth list unix:10.0 2>/dev/null
debug1: Requesting X11 forwarding with authentication spoofing.
debug2: channel 0: request x11-req confirm 0
debug2: client_session2_setup: id 0
debug2: channel 0: request pty-req confirm 0
debug2: channel 0: request shell confirm 0
debug2: fd 4 setting TCP_NODELAY
debug2: callback done
debug2: channel 0: open confirm rwindow 0 rmax 32768
debug2: channel 0: rcvd adjust 2097152

Rocks Compute Node
Rocks 5.3 (Rolled Tacos)
Profile built 17:39 22-Apr-2010

Kickstarted 17:45 22-Apr-2010

-bash-3.2$

Any ideas?

On Tue, May 4, 2010 at 10:43 AM, Bart Brashers
<bbra...@environcorp.com> wrote:
>> I have a Rocks 5.1 (V.I) and for only one user I always get a password
>> prompt when launching a job or logging into the compute node.
>> Every time I do the following:
>>
>>    $ ssh-agent $SHELL
>>    $ ssh-add
>>
>> but the next login I do again the above procedure for password prompt
>> problem.
>>
>> For only one user, for the other users there isn't this problem.
>
> Check permissions on /home/$user and /home/$user/.ssh (and contents).
>
> Try "ssh -v compute-0-0" and read the output to see why it fails to use
> the SSH keys.  Try "ssh -vv compute-0-0" if you don't find anything.
>
> Re-generate the SSH keys: "rm .ssh/id_rsa* ; ssh-keygen -t rsa" and
> accept the defaults.
>
> Bart
>
>
>
>
>
>
> This message contains information that may be confidential, privileged or otherwise protected by law from disclosure. It is intended for the exclusive use of the Addressee(s). Unless you are the addressee or authorized agent of the addressee, you may not review, copy, distribute or disclose to anyone the message or any information contained within. If you have received this message in error, please contact the sender by electronic reply to em...@environcorp.com and immediately delete all copies of the message.
>



--

Personally, I liked the university. They gave us money and facilities,
we didn't have to produce anything! You've never been out of college!
You don't know what it's like out there! I've worked in the private
sector. They expect results. -Ray Ghostbusters

[Bart Brashers]

Check the differences:

# su - user1
# ssh -Y -vv compute-1-1 >& /tmp/user1
# exit
# su - user2
# ssh -Y -vv compute-1-1 >& /tmp/user2
# exit
# diff /tmp/user1 /tmp/user2

I think you said you've already tried deleting ~/.Xauthority for the troublesome user, and re-creating it (see `man xauth`).

Do you get the same response from ALL compute nodes?

Bart

> cbc,arcfour128,arcfour256,arcfour,aes192-cbc,aes256-cbc,rijndael-
> c...@lysator.liu.se,aes128-ctr,aes192-ctr,aes256-ctr
> debug2: kex_parse_kexinit:
> aes128-cbc,3des-cbc,blowfish-cbc,cast128-
> cbc,arcfour128,arcfour256,arcfour,aes192-cbc,aes256-cbc,rijndael-
> c...@lysator.liu.se,aes128-ctr,aes192-ctr,aes256-ctr
> debug2: kex_parse_kexinit:
> hmac-md5,hmac-sha1,hmac-ripemd160,hmac-ri...@openssh.com,hmac-sha1-96,hmac-
> md5-96
> debug2: kex_parse_kexinit:
> hmac-md5,hmac-sha1,hmac-ripemd160,hmac-ri...@openssh.com,hmac-sha1-96,hmac-

> md5-96
> debug2: kex_parse_kexinit: none,zl...@openssh.com,zlib
> debug2: kex_parse_kexinit: none,zl...@openssh.com,zlib
> debug2: kex_parse_kexinit:
> debug2: kex_parse_kexinit:
> debug2: kex_parse_kexinit: first_kex_follows 0
> debug2: kex_parse_kexinit: reserved 0
> debug2: kex_parse_kexinit:
> diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-
> group1-sha1

> debug2: kex_parse_kexinit: ssh-rsa,ssh-dss
> debug2: kex_parse_kexinit:
> aes128-cbc,3des-cbc,blowfish-cbc,cast128-

> cbc,arcfour128,arcfour256,arcfour,aes192-cbc,aes256-cbc,rijndael-
> c...@lysator.liu.se,aes128-ctr,aes192-ctr,aes256-ctr
> debug2: kex_parse_kexinit:
> aes128-cbc,3des-cbc,blowfish-cbc,cast128-
> cbc,arcfour128,arcfour256,arcfour,aes192-cbc,aes256-cbc,rijndael-
> c...@lysator.liu.se,aes128-ctr,aes192-ctr,aes256-ctr
> debug2: kex_parse_kexinit:
> hmac-md5,hmac-sha1,hmac-ripemd160,hmac-ri...@openssh.com,hmac-sha1-96,hmac-
> md5-96
> debug2: kex_parse_kexinit:
> hmac-md5,hmac-sha1,hmac-ripemd160,hmac-ri...@openssh.com,hmac-sha1-96,hmac-

[Luca Nannipieri]

thanks for answer,
I tried to remove id_rsa* and do rsa key again, but I still get a

password prompt when launching a job or logging into the compute node.

Below the output about ssh -vv command:

[meteo@tinyhpc .ssh]$ ssh -vv compute-0-0
OpenSSH_4.3p2, OpenSSL 0.9.8b 04 May 2006

debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Applying options for *
debug2: ssh_connect: needpriv 0

debug1: Connecting to compute-0-0 [192.168.255.254] port 22.
debug1: Connection established.
debug1: identity file /home/meteo/.ssh/identity type -1

debug2: key_type_from_name: unknown key type '-----BEGIN'
debug2: key_type_from_name: unknown key type '-----END'

debug1: identity file /home/meteo/.ssh/id_rsa type 1
debug1: identity file /home/meteo/.ssh/id_dsa type -1

debug1: loaded 3 keys
debug1: Remote protocol version 2.0, remote software version OpenSSH_4.3
debug1: match: OpenSSH_4.3 pat OpenSSH*
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_4.3

debug2: fd 3 setting O_NONBLOCK

debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug2: kex_parse_kexinit:
diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1
debug2: kex_parse_kexinit: ssh-rsa,ssh-dss
debug2: kex_parse_kexinit:

aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour128,arcfour256,arcfour,aes192-cbc,aes256-cbc,rijnda...@lysator.liu.se,aes128-ctr,aes192-ctr,aes256-ctr
debug2: kex_parse_kexinit:
aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour128,arcfour256,arcfour,aes192-cbc,aes256-cbc,rijnda...@lysator.liu.se,aes128-ctr,aes192-ctr,aes256-ctr
debug2: kex_parse_kexinit:
hmac-md5,hmac-sha1,hmac-ripemd160,hmac-ri...@openssh.com,hmac-sha1-96,hmac-md5-96
debug2: kex_parse_kexinit:
hmac-md5,hmac-sha1,hmac-ripemd160,hmac-ri...@openssh.com,hmac-sha1-96,hmac-md5-96

debug2: kex_parse_kexinit: none,zl...@openssh.com,zlib
debug2: kex_parse_kexinit: none,zl...@openssh.com,zlib
debug2: kex_parse_kexinit:
debug2: kex_parse_kexinit:
debug2: kex_parse_kexinit: first_kex_follows 0
debug2: kex_parse_kexinit: reserved 0
debug2: kex_parse_kexinit:
diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1

debug2: kex_parse_kexinit: ssh-rsa,ssh-dss
debug2: kex_parse_kexinit:

aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour128,arcfour256,arcfour,aes192-cbc,aes256-cbc,rijnda...@lysator.liu.se,aes128-ctr,aes192-ctr,aes256-ctr
debug2: kex_parse_kexinit:
aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour128,arcfour256,arcfour,aes192-cbc,aes256-cbc,rijnda...@lysator.liu.se,aes128-ctr,aes192-ctr,aes256-ctr
debug2: kex_parse_kexinit:
hmac-md5,hmac-sha1,hmac-ripemd160,hmac-ri...@openssh.com,hmac-sha1-96,hmac-md5-96
debug2: kex_parse_kexinit:
hmac-md5,hmac-sha1,hmac-ripemd160,hmac-ri...@openssh.com,hmac-sha1-96,hmac-md5-96

debug2: kex_parse_kexinit: none,zl...@openssh.com
debug2: kex_parse_kexinit: none,zl...@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_init: found hmac-md5
debug1: kex: server->client aes128-cbc hmac-md5 none
debug2: mac_init: found hmac-md5
debug1: kex: client->server aes128-cbc hmac-md5 none
debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<1024<8192) sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP

debug2: dh_gen_key: priv key bits set: 131/256
debug2: bits set: 518/1024

debug1: SSH2_MSG_KEX_DH_GEX_INIT sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY

debug1: Host 'compute-0-0' is known and matches the RSA host key.
debug1: Found key in /home/meteo/.ssh/known_hosts:1
debug2: bits set: 493/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
debug2: set_newkeys: mode 0
debug1: SSH2_MSG_NEWKEYS received
debug1: SSH2_MSG_SERVICE_REQUEST sent
debug2: service_accept: ssh-userauth
debug1: SSH2_MSG_SERVICE_ACCEPT received

debug2: key: /home/meteo/.ssh/id_rsa (0x40ff4748)
debug2: key: /home/meteo/.ssh/identity ((nil))
debug2: key: /home/meteo/.ssh/id_dsa ((nil))

debug1: Authentications that can continue:
publickey,gssapi-with-mic,password
debug1: Next authentication method: publickey

debug1: Offering public key: /home/meteo/.ssh/id_rsa

debug2: we sent a publickey packet, wait for reply

debug1: Authentications that can continue:
publickey,gssapi-with-mic,password

debug1: Trying private key: /home/meteo/.ssh/identity
debug1: Trying private key: /home/meteo/.ssh/id_dsa
debug2: we did not send a packet, disable method
debug1: Next authentication method: password
meteo@compute-0-0's password:


Bart Brashers ha scritto:

>> I have a Rocks 5.1 (V.I) and for only one user I always get a password
>> prompt when launching a job or logging into the compute node.
>> Every time I do the following:
>>
>> $ ssh-agent $SHELL
>> $ ssh-add
>>
>> but the next login I do again the above procedure for password prompt
>> problem.
>>
>> For only one user, for the other users there isn't this problem.
>>
>
> Check permissions on /home/$user and /home/$user/.ssh (and contents).
>
> Try "ssh -v compute-0-0" and read the output to see why it fails to use
> the SSH keys. Try "ssh -vv compute-0-0" if you don't find anything.
>
> Re-generate the SSH keys: "rm .ssh/id_rsa* ; ssh-keygen -t rsa" and
> accept the defaults.
>
> Bart
>
>
>
>
>
>
> This message contains information that may be confidential, privileged or otherwise protected by law from disclosure. It is intended for the exclusive use of the Addressee(s). Unless you are the addressee or authorized agent of the addressee, you may not review, copy, distribute or disclose to anyone the message or any information contained within. If you have received this message in error, please contact the sender by electronic reply to em...@environcorp.com and immediately delete all copies of the message.
>
>


--

Ing. Luca Nannipieri
Istituto Nazionale di Geofisica e Vulcanologia
Sezione di Pisa
Via della Faggiola, 32 - 56126 Pisa - Italy
Tel. +39 050 8311926
fax: +39 050 8311942
http://www.pi.ingv.it/Pagine_personali/nannipieri.html

[barış akay]

First of all

You have to backup your ssh folder that located on the user folder. You can
see those files with show hidden files options.Then on the terminal execute
ssh-keygen -t rsa command. This command generates ssh-rsa-public file. Copy
content of this file then paste end of ssh-rsa file and save.After all
restart ssh service with /etc/init.d/sshd restart command.

That's all

2010/5/4 Luca Nannipieri <nanni...@pi.ingv.it>

> I have a Rocks 5.1 (V.I) and for only one user I always get a password
> prompt when launching a job or logging into the compute node.
> Every time I do the following:
>
> $ ssh-agent $SHELL
> $ ssh-add
>
> but the next login I do again the above procedure for password prompt
> problem.
>
> For only one user, for the other users there isn't this problem.
>
> --
> Ing. Luca Nannipieri
> Istituto Nazionale di Geofisica e Vulcanologia
> Sezione di Pisa
> Via della Faggiola, 32 - 56126 Pisa - Italy
> Tel. +39 050 8311926
> fax: +39 050 8311942
> http://www.pi.ingv.it/Pagine_personali/nannipieri.html
>
>


--

Barış AKAY
Istanbul Technical University
Institute of Science and Technology
Aeronautical and Astronautical Engineering MSc. Student
e-mail: baris...@gmail.com
baris...@itu.edu.tr
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://lists.sdsc.edu/pipermail/npaci-rocks-discussion/attachments/20100505/d4f40a85/attachment.html

[Greg Bruno]

On Wed, May 5, 2010 at 2:10 AM, Luca Nannipieri <nanni...@pi.ingv.it> wrote:
> thanks for answer,
> I tried to remove id_rsa* and do rsa key again, but I still get a password
> prompt when launching a job or logging into the compute node.
> Below the output about ssh -vv command:

it is most likely a permissions problem.

what is the output of:

# ls -ld /home/meteo
# ls -ld /home/meteo/.ssh
# ls -l /home/meteo/.ssh/*

- gb

[barış akay]

i wanna ask some question

1) does your home folder located on the nfs drive (for example
/export/home/user)
2) Did you execute command (ssh-keygen -t rsa) on compute node when login
with correct user (not root)
if your user folder not located nfs disk or nfs runs not correctly, your
ssh-rsa-public file doesn't include compute node ssh key



2010/5/5 Greg Bruno <greg....@gmail.com>

> On Wed, May 5, 2010 at 2:10 AM, Luca Nannipieri <nanni...@pi.ingv.it>
> wrote:
> > thanks for answer,
> > I tried to remove id_rsa* and do rsa key again, but I still get a
> password
> > prompt when launching a job or logging into the compute node.
> > Below the output about ssh -vv command:
>
> it is most likely a permissions problem.
>
> what is the output of:
>
> # ls -ld /home/meteo
> # ls -ld /home/meteo/.ssh
> # ls -l /home/meteo/.ssh/*
>
> - gb
>



--

Barış AKAY
Istanbul Technical University
Institute of Science and Technology
Aeronautical and Astronautical Engineering MSc. Student
e-mail: baris...@gmail.com
baris...@itu.edu.tr
-------------- next part --------------
An HTML attachment was scrubbed...

URL: https://lists.sdsc.edu/pipermail/npaci-rocks-discussion/attachments/20100505/9f52fdea/attachment.html

[Luca Nannipieri]

"1) does your home folder located on the nfs drive (for
example/export/home/user)"

YES

"2) Did you execute command (ssh-keygen -t rsa) on compute node when
login with correct user (not root)"

YES

...but the problem persists

barış akay ha scritto:

> i wanna ask some question
>
> 1) does your home folder located on the nfs drive (for example
> /export/home/user)
> 2) Did you execute command (ssh-keygen -t rsa) on compute node when login
> with correct user (not root)
> if your user folder not located nfs disk or nfs runs not correctly, your
> ssh-rsa-public file doesn't include compute node ssh key
>
>
>
> 2010/5/5 Greg Bruno <greg....@gmail.com>
>
>
>> On Wed, May 5, 2010 at 2:10 AM, Luca Nannipieri <nanni...@pi.ingv.it>
>> wrote:
>>
>>> thanks for answer,
>>> I tried to remove id_rsa* and do rsa key again, but I still get a
>>>
>> password
>>
>>> prompt when launching a job or logging into the compute node.
>>> Below the output about ssh -vv command:
>>>
>> it is most likely a permissions problem.
>>
>> what is the output of:
>>
>> # ls -ld /home/meteo
>> # ls -ld /home/meteo/.ssh
>> # ls -l /home/meteo/.ssh/*
>>
>> - gb
>>
>>
>
>
>
>


--

Ing. Luca Nannipieri
Istituto Nazionale di Geofisica e Vulcanologia
Sezione di Pisa
Via della Faggiola, 32 - 56126 Pisa - Italy
Tel. +39 050 8311926
fax: +39 050 8311942
http://www.pi.ingv.it/Pagine_personali/nannipieri.html

[barış akay]

1) Delete all ssh files after backup them if you don't have permission for
these process in the terminal screen you can change permissions with chmod
-r 755 /export/home/user/.ssh command
2) When you login node these files created again by os
3) create ssh keys both master node and compute node with default setting

i hope that solves your problem



06 Mayıs 2010 11:14 tarihinde Luca Nannipieri <nanni...@pi.ingv.it> yazdı:

Barış AKAY
Istanbul Technical University
Institute of Science and Technology
Aeronautical and Astronautical Engineering MSc. Student
e-mail: baris...@gmail.com
baris...@itu.edu.tr
-------------- next part --------------
An HTML attachment was scrubbed...

URL: https://lists.sdsc.edu/pipermail/npaci-rocks-discussion/attachments/20100506/d0735a24/attachment.html

[Luca Nannipieri]

How to "3) create ssh keys both master node and compute node with
default setting" ?


barış akay ha scritto:

> 1) Delete all ssh files after backup them if you don't have permission for
> these process in the terminal screen you can change permissions with chmod
> -r 755 /export/home/user/.ssh command
> 2) When you login node these files created again by os
> 3) create ssh keys both master node and compute node with default setting
>
> i hope that solves your problem
>
>
>
> 06 Mayıs 2010 11:14 tarihinde Luca Nannipieri <nanni...@pi.ingv.it> yazdı:
>
>
>> "1) does your home folder located on the nfs drive (for
>> example/export/home/user)"
>>
>> YES
>>
>>
>> "2) Did you execute command (ssh-keygen -t rsa) on compute node when login
>> with correct user (not root)"
>>
>> YES
>>
>> ...but the problem persists
>>
>> barış akay ha scritto:
>>
>> i wanna ask some question
>>
>>> 1) does your home folder located on the nfs drive (for example
>>> /export/home/user)

>>> 2) Did you execute command () on compute node when login

[Bart Brashers]

To create SSH keys for user joe, do the following:

# su - joe
# ssh-keygen -t rsa -f ~/.ssh/id_rsa -N ""

But that won't fix your problem. Greg asked earlier about permissions:

> >>>> what is the output of:
> >>>>
> >>>> # ls -ld /home/meteo
> >>>> # ls -ld /home/meteo/.ssh
> >>>> # ls -l /home/meteo/.ssh/*

We suspect you have the wrong permissions.

The user's home directory must show drwx------ when you do "ls -lFd /home/joe".
The user's .ssh directory must show drwx------
~/.ssh/authorized_keys must be -rw-r--r--
~/.ssh/id_rsa must be -rw-------
~/.ssh/id_rsa.pub must be -rw-r--r--
~/.ssh/known_hosts must be -rw-r--r--

I suspect you have too loose permissions on /home/joe/.

Bart

This message contains information that may be confidential, privileged or otherwise protected by law from disclosure. It is intended for the exclusive use of the Addressee(s). Unless you are the addressee or authorized agent of the addressee, you may not review, copy, distribute or disclose to anyone the message or any information contained within. If you have received this message in error, please contact the sender by electronic reply to em...@environcorp.com and immediately delete all copies of the message.

[barış akay]

execute ssh-keygen -t rsa on master node it ask you password it must
be blank and repeat that for compute node after connect the compute
node with ssh
ps:after when you created ssh key on master node ssh files generated
by os.After that on compute node when you execute command that ask you
a question (overwrite the file =yes ) then copy the information in
ssh-rsa-public file and paste to end of ssh-rsa file on master node.

07 Mayıs 2010 17:24 tarihinde Luca Nannipieri <nanni...@pi.ingv.it> yazdı:

Barış AKAY
Istanbul Technical University
Institute of Science and Technology
Aeronautical and Astronautical Engineering MSc. Student
e-mail: baris...@gmail.com
baris...@itu.edu.tr