Shell Programming and Scripting

From your logs, it is clear that the login is taking place:
The problem is probably with the command/script that you are running on the remote system. What are you running on the remote system? Can you change the remote command to something like 'touch /tmp/testfile' - basically anything to confirm that login is taking place on remote system?

Thanks for the reply.

Just tried that. Basically i changed the script on the 2 remote servers to just touch a file in a directory on the remote server.

I then let cron run the script on my server to execute the script with the change above.

The file was created on the remote server 1 but hasnt got to the 2nd server yet- as far as my server is concerned, its still executing the remote script on server1.. when I do a ps -ef | grep for the script I get the following:

bash-2.05# ps -ef | grep daily
root 27707 27701 0 10:43:00 ? 0:00 ssh -v user@server1 /pathtoremotedir/script.sh root 27701 27698 0 10:43:00 ? 0:00 /usr/bin/ksh /localserver/script.sh root 27698 231 0 10:43:00 ? 0:00 sh -c /localserver/script.sh > /tmp/sshcron 2>&1


The last few lines in my debug after this are:
debug1: cb_fn 2677c cb_event 91
debug1: channel 0: rcvd close
debug1: channel 0: full closed2
debug1: channel_free: channel 0: status: The following connections are open:
#0 client-session (t4 r0 i8/0 o128/0 fd -1/-1)

debug1: channel_free: channel 0: dettaching channel user


Idea's?

we have all 3 variants of your cron jobs in our cron tables and they all work fine ...

if the command runs normally on the command line but doesn't run properly through cron --- i don't think the issue is with the keys itself (of course, i could be wrong too) ... you may have a process that is looking for input or at least checking stdin/stdout/stderr or having the incorrect path or checking some environment variable that is not being set in your script prior to it running in cron ... maybe you can run a script in cron that just records the output from "env" and then you can compare that to the output of "env" in your interactive login ...

btw, you might want to check both the local and the remote scripts ...

I tried this now. I compared cron env and interactive env. There were differences so I set these in my script to be set before I run remote ssh... No difference in processing script - I still hit the same issue.

I also checked the env settings on the remote server when I run the script from cron or int - only difference is the port that it used when SSH connects to execute the script. I am at a loss...

in that case, try echoing all the variables and their values on the remote script to a file you can read when it is run from cron ... see if the same variables and values are showing up in the interactive run ... from what i gather from all the posts, there's a line in your remote script that's making it hang --- my experience says this is most likely something that needs to read a file ...

btw, what does the remote script do?

They all appear to be the same.

I was getting the remote script to check processes running etc.
But I have removed all of this and changed the remote script to just touch a file... thats all. And it still hangs.. although the file is created the ssh cron job on my side appears to be hanging...

it seems the remote script is not exiting properly ... do you have an exit on the last line of the remote script? ... the ssh connection is probably staying open because the shell your script was running in is still open ...