topic Re: scp cron in Operating System - HP-UX

scp cron

Martin Wells — Thu, 08 Apr 2004 04:52:36 GMT

I'm trying to scp some files from one server to another via a script. This script works fine when run from the command line but when its in cron I get the following errors and no file transfer

Executing ssh2 failed. Command:' ssh2 -l oracle -x -a -o passwordprompt %U@%H's password: -o nodelay yes -o authenticationnotify yes rnssupa -s sftp' System error message: 'No such file or directory'

I'm using the full path for the scp command?

This is on a N-Class server running HPUX11 and ssh version 2.1.0

Thanks

Re: scp cron

RAC_1 — Thu, 08 Apr 2004 05:00:05 GMT

First thing, can you do ssh to other host without problems? Do you have private/public keys exchange set properly? If ssh has no problems, try as follows.

scp /dir/file user@otherhost:/path/where_to_copy.

Anil

Re: scp cron

Francisco J. Soler — Thu, 08 Apr 2004 05:00:50 GMT

Hi,
You must specify the full path of ssh2 or set the PATH variable at the begining of the script.

When execute from cron you must be careful with the enviroment variables.

Frank.

Re: scp cron

Martin Wells — Thu, 08 Apr 2004 05:03:08 GMT

I can ssh without issue and perform the scp command from the script when run manually and from the command line if I just use just the scp line of code?

Re: scp cron

Francisco J. Soler — Thu, 08 Apr 2004 05:11:29 GMT

Hi Martin, I don't understand very well your last query, but if it is a path problem, your command execution depends of path variable, if the user you are executing from, have the correct path you can execute they, if not you must specify the full path.

See the .profile (sh) or .login (csh) user files to know the user path variable.

Frank.

Re: scp cron

RAC_1 — Thu, 08 Apr 2004 05:40:56 GMT

What are the ssh versions installed on both systems?

Also did you try as I told you?

scp /dir/file user@otherhost:/path/where_to_copy.

Anil

Re: scp cron

Bill Hassell — Thu, 08 Apr 2004 07:31:33 GMT

Very common problem: works manually, fails in cron. cron does NOT login so your 'normal' environment is non-existant. This is your cron environment:

HOME=user's-home-directory
LOGNAME=user's-login-id
PATH=/usr/bin:/usr/sbin:.
SHELL=/usr/bin/sh

So your cron job must have everything explicitly coded: full pathnames for scp and any directories or files, all env variables replaced with actual values, etc.