SSH key works from CMD line not script

UNIX for Advanced & Expert Users
1

OK , ..
This is an odd one. I have a new server and I need to have a tunnel open to it.
I have this exact process running on a few others but this new one I just got is not allowing the script to connect.
I set up my users account and ssh keys

from the server that will host the tunneling i type

ssh user_name@server_to_connect_to.com

it reads my key and lets me in .....
Now if I run my tunnel script it fails

/usr/bin/ssh -oKeepAlive=yes -i /home/path/to/ssh_tunnel_rsa_privatekey -C user_name@server_to_connect_to.com  -L3333:*:3306 -g -N &

in /var/log/secure i see

Failed password for user_name from xx.xx.xxx.x port 48443 ssh2
Any thoughts or suggestions ??
Thanks
Jeff

2 
/usr/bin/ssh -oKeepAlive=yes -i /home/path/to/ssh_tunnel_rsa_privatekey -C user_name@server_to_connect_to.com  -L3333:*:3306 -g -N &

have you tried this on the command line itself? in post you only tried

ssh user_name@server_to_connect_to.com

and if you may add -v.

3

Yes I was running that from CMD line and added a -v

debug1: Authentications that can continue: publickey,gssapi-with-mic,password
debug1: Next authentication method: gssapi-with-mic
debug1: Unspecified GSS failure.  Minor code may provide more information
No credentials cache found

debug1: Unspecified GSS failure.  Minor code may provide more information
No credentials cache found

debug1: Unspecified GSS failure.  Minor code may provide more information
No credentials cache found

debug1: Next authentication method: publickey
debug1: Trying private key: /home/path/to/ssh_tunnel_rsa_privatekey 
debug1: read PEM private key done: type DSA
debug1: Authentications that can continue: publickey,gssapi-with-mic,password
debug1: Next authentication method: password
4

i think you are pointing to the wrong private key file. make sure the path after the -i points to the private keys for the user. usually, this is located at /home/<user>/.ssh directory.

5

I just checked , the remote server I am trying to connect to I copied the private key to my tunnel server and that is the name and path

/home/path/to/ssh_tunnel_rsa_privatekey

I just checked it again.... and its good chmod 600 like the rest .... i know i am missing something but its been 2 years since i first did this and cannot for the life of me remember what i am missing
< frustrating >

6

hmmm it shouldn't be the private key that you will copy. you have to put your public key on the authorized_keys file on the remote server. This will be helpful. Read on the advance ssh part. Simple SSH Tutorial Outline

7

OK .... some how for some reason someone updated SSH and any new tunnel that was not established you have to do this with the -g switch

/usr/bin/ssh -oKeepAlive=yes -i /home/path/to/ssh_tunnel_rsa_privatekey -C user_name@server_to_connect_to.com  -L172.36.x.xx:3318:*:3306 -g -N &

With the x.xx being the ip of the server hosting the tunnel

All our others are working fine since they have been established. We updated them in the event they drop .

Anyway who ever can close this Thanks everyone
Jeff