- Mark as New
- Bookmark
- Subscribe
- Mute
- RSS Feed
- Permalink
- Report Inappropriate Content
I am getting the following error message when I try to sftp from SAS EG:
SAS Host key verification failed. Couldn't read packet: Connection reset by peer
This is when I execute the sftp command using the x command e.g.
x "sftp my_user@mytest.vvv.sss.xxxxxx.com.aa"; XCMD is enabled as I can issue other x commands successfully.
This is even though I am logged on in EG as the same user that has been set up with the public and private keys on the Unix server and my code is submitted to run on that server.
If I log on to the unix server directly with the same account id as in EG using Putty, and issue the same command, sftp my_user@mytest.vvv.sss.xxxxxx.com.aa it works, and connects successfully to the remote sftp server.
Any suggestions welcome.
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- RSS Feed
- Permalink
- Report Inappropriate Content
ok the problem is solved. It turned out that because we are operating in a grid environment, the keys need to be verified on all 4 grid hosts and a known_hosts file created on each. Once this was done and a few underlying permission changed made by the unix admin guy the code worked like a dream and all was good in the world. Thanks to all those who tried to help with this tricky issue.
- Mark as New
- Bookmark
- Subscribe
- Mute
- RSS Feed
- Permalink
- Report Inappropriate Content
Just a hunch: immediately before you try the sftp, do
x 'cd $HOME';
Also, retrieve all responses to the sftp command:
filename oscmd pipe 'sftp my_user@mytest.vvv.sss.xxxxxx.com.aa 2>&1';
data _null_;
infile oscmd;
input;
put _infile_;
run;
- Mark as New
- Bookmark
- Subscribe
- Mute
- RSS Feed
- Permalink
- Report Inappropriate Content
ok the problem is solved. It turned out that because we are operating in a grid environment, the keys need to be verified on all 4 grid hosts and a known_hosts file created on each. Once this was done and a few underlying permission changed made by the unix admin guy the code worked like a dream and all was good in the world. Thanks to all those who tried to help with this tricky issue.
- Mark as New
- Bookmark
- Subscribe
- Mute
- RSS Feed
- Permalink
- Report Inappropriate Content
"Working in a grid" is always important information, as it often explains "intermittent" failures caused by different configurations on the individual nodes.