[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Duplicity-talk] Failures on backup jobs from cron
From: |
edgar . soldin |
Subject: |
Re: [Duplicity-talk] Failures on backup jobs from cron |
Date: |
Wed, 8 Mar 2023 12:57:27 +0100 |
User-agent: |
Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.6.1 |
On 07.03.2023 23:03, Russell Clemings wrote:
3) On the cron job, make sure all paths are set properly in crontab, and
make sure you don't have duplicate duplicity instances:
$ find /usr -name duplicity -type f
$ find /usr -name duplicity -type d
I do get multiple versions, but I've always included the full path in my
script, e.g.:
crontab: /home/newton/duplicity-0.8.12.1612/s3backup/backup.sh
backup.sh: /home/newton/duplicity-0.8.12.1612/bin/duplicity
that is irrelevant. installing python apps places parts of them in system
python library folders by default. having multiple versions may lead to one
version using modules from an incompatible version, hence to errors.
If you have more than one response from above, uninstall all, and
reinstall the one you want.
I'm kind of afraid to uninstall anything until I can get a replacement working.
Right now 0.8.12.1612 still works from the command line.
well, if that one works. remove all of the other ones and fix the cron issue
instead?
..ede/duply.net