Hi DJ,
I don't know. I can log in, other users reported they can't, too. The
sys admins will need to look into this.
Jens
On Sat, Nov 15, 2014 at 3:38 PM, Dhananjai Rao <[log in to unmask]> wrote:
> Hello,
>
> I have not been able to log onto Red Hawk head node from home since last
> night (I have been able to login without issues for years now). I am
> pretty sure I am entering the correct password. I am able to log onto
> mymaimi and niihka with my password. I will be thankful if you could
> help with troubleshooting the issue. Please see ssh handshake messages
> at the end of the email (in case they help).
>
> thanks
>
> with regards
> D.M.Rao
>
> $ ssh -v [log in to unmask]
> OpenSSH_6.1p1, OpenSSL 1.0.0-fips 29 Mar 2010
> debug1: Reading configuration data /home/raodm/.ssh/config
> debug1: /home/raodm/.ssh/config line 1: Applying options for *
> debug1: Reading configuration data /etc/ssh/ssh_config
> debug1: /etc/ssh/ssh_config line 50: Applying options for *
> debug1: Connecting to redhawk.hpc.miamioh.edu [134.53.247.245] port 22.
> debug1: Connection established.
> debug1: identity file /home/raodm/.ssh/id_rsa type -1
> debug1: identity file /home/raodm/.ssh/id_rsa-cert type -1
> debug1: identity file /home/raodm/.ssh/id_dsa type -1
> debug1: identity file /home/raodm/.ssh/id_dsa-cert type -1
> debug1: Remote protocol version 2.0, remote software version OpenSSH_5.3
> debug1: match: OpenSSH_5.3 pat OpenSSH_5*
> debug1: Enabling compatibility mode for protocol 2.0
> debug1: Local version string SSH-2.0-OpenSSH_6.1
> debug1: SSH2_MSG_KEXINIT sent
> debug1: SSH2_MSG_KEXINIT received
> debug1: kex: server->client aes128-ctr hmac-md5 none
> 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
> debug1: SSH2_MSG_KEX_DH_GEX_INIT sent
> debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY
> debug1: Server host key: RSA
> c3:95:89:0e:e8:c5:f1:11:35:1e:e7:88:1c:cb:dc:2c
> debug1: Host 'redhawk.hpc.miamioh.edu' is known and matches the RSA host
> key.
> debug1: Found key in /home/raodm/.ssh/known_hosts:16
> debug1: ssh_rsa_verify: signature correct
> 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,gssapi-keyex,gssapi-with-mic,password,keyboard-interactive,hostbased
> debug1: Next authentication method: gssapi-keyex
> debug1: No valid Key exchange context
> debug1: Next authentication method: gssapi-with-mic
> debug1: Unspecified GSS failure. Minor code may provide more
> information
> Credentials cache file
> '/run/user/1000/krb5cc_3990636ca8d860b864ba2f15545c06ac/tkt' not found
>
> debug1: Unspecified GSS failure. Minor code may provide more
> information
> Credentials cache file
> '/run/user/1000/krb5cc_3990636ca8d860b864ba2f15545c06ac/tkt' 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
> '/run/user/1000/krb5cc_3990636ca8d860b864ba2f15545c06ac/tkt' not found
>
> debug1: Next authentication method: publickey
> debug1: Trying private key: /home/dmadhava/.ssh/id_rsa
> debug1: Trying private key: /home/dmadhava/.ssh/id_dsa
> debug1: Next authentication method: keyboard-interactive
> Password:
> debug1: Authentications that can continue:
> publickey,gssapi-keyex,gssapi-with-mic,password,keyboard-interactive,hostbased
> debug1: Authentications that can continue:
> publickey,gssapi-keyex,gssapi-with-mic,password,keyboard-interactive,hostbased
> debug1: Authentications that can continue:
> publickey,gssapi-keyex,gssapi-with-mic,password,keyboard-interactive,hostbased
> debug1: Next authentication method: password
> [log in to unmask] password:
> Connection closed by 134.53.247.245
|
