Hi everybody,
I'm trying to automate a box to box backup.
When I run the "scp" command from the command line it uses my public/private key pair and everything works well but if I execute the same command from a cron job the receiving end reports, "Failed password...".
Why does CLI use keys but the script use passwords?
Here is the command:
scp -r /home/mike/Backup/mysql 192.168.4.70:/home/mike/Backup
Thanks for any insight.
Happy Holidays to all, Mike Wright
12/21/2013 09:00 AM, Mike Wright wrote:
Hi everybody,
I'm trying to automate a box to box backup.
When I run the "scp" command from the command line it uses my public/private key pair and everything works well but if I execute the same command from a cron job the receiving end reports, "Failed password...".
Why does CLI use keys but the script use passwords?
Here is the command:
scp -r /home/mike/Backup/mysql 192.168.4.70:/home/mike/Backup
OK. For some reason scp needs to be told explicitly which key set to use. This is done using the -i switch:
scp -r -i /home/mike/.ssh/sql_rsa ...
On 21Dec2013 11:08, Mike Wright mike.wright@mailinator.com wrote:
12/21/2013 09:00 AM, Mike Wright wrote:
I'm trying to automate a box to box backup.
When I run the "scp" command from the command line it uses my public/private key pair and everything works well
I would guess: via an ssh-agent?
but if I execute the same command from a cron job the receiving end reports, "Failed password...".
Why does CLI use keys but the script use passwords? Here is the command: scp -r /home/mike/Backup/mysql 192.168.4.70:/home/mike/Backup
OK. For some reason scp needs to be told explicitly which key set to use. This is done using the -i switch:
scp -r -i /home/mike/.ssh/sql_rsa ...
Only if the key does not have the default name "id_rsa".
Alternatively you can make a .ssh/config clause to specify the name, eg:
Host backups Hostname 192.168.4.70 IdentityFile ~/.ssh/sql_rsa
Then:
scp -r -i /home/mike/Backup/mysql backups:/home/mike/Backup
Cheers,