Re: [Duplicity-talk] Erring out when using cron, but working on the command line.

[Diagon]

This I was able to figure out.  It's a standard issue in cron.  Somehow you 
have to get information on how to access encrypted ssh keys to the subshell.  
Typically that would be via making an ssh-agent accessible to the subshell.  
The following link describes three approaches:

https://stackoverflow.com/a/18041092

This is apparently basic enough, that I might suggest that it should be in a 
duplicity FAQ somewhere?  Maybe it is and I didn't see it.

/D

============ Forwarded message ============
From: Diagon <address@hidden>
To: "duplicity-talk"<address@hidden>
Date: Tue, 12 May 2020 20:32:17 -0700
Subject: Erring out when using cron, but working on the command line.
============ Forwarded message ============

 > I'm backing up to a remote location via cron.  The following command works 
 > on the command line, but fails in crontab:
 > 
 > */10 * * * * PASSPHRASE="mypassword" flock -n /tmp/backuplock 
 > /usr/bin/duplicity --log-file /home/me/duplicity.log --backend-retry-delay 
 > 60 --asynchronous-upload --name TEST --volsize 50 --full-if-older-than 6M 
 > --exclude '**.lock' /home/me/Desktop/TEST sftp://address@hidden/Backup
 > 
 > The error is:
 > 
 > ERROR 23 BackendException
 > . BackendException: ssh connection to address@hidden:22 failed: Private key 
 > file is encrypted
 > 
 > I'm confused because my understanding is that my crontab will run under my 
 > same uname.  
 > 
 > Is there something I need to do with ssh-agent or somesuch?  Does anyone 
 > have any suggestions?  I've never looked into this end of things.
 > 
 > Thanks! /D