[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Duplicity-talk] Erring out when using cron, but working on the comm
From: |
edgar . soldin |
Subject: |
Re: [Duplicity-talk] Erring out when using cron, but working on the command line. |
Date: |
Wed, 13 May 2020 11:49:10 +0200 |
User-agent: |
Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:68.0) Gecko/20100101 Thunderbird/68.6.0 |
On 13.05.2020 05:32, Diagon via Duplicity-talk wrote:
> 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.
>
might depend on the gpg version you are using. which is it?
might be a bug in paramiko (python ssh module) like
https://github.com/paramiko/paramiko/issues/1317 . try
pexpect+sftp://
an alternative ssh backend, which uses the command line binaries, to verify.
are you sure that this is the crontab for 'me'? just asking;)
..ede/duply.net