duplicity jobs not working
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| | backupninja (Debian) |
Fix Released
|
Unknown
|
||
| | backupninja (Ubuntu) |
Low
|
Unassigned | ||
Bug Description
Binary package hint: backupninja
I get these error messages in the logs when there is already some data there:
Jul 15 01:24:20 Debug: duplicity --no-print-
n-key 83AF64BC --remove-older-than 60D --include '/home/
/home/lstewart/
Jul 15 01:24:50 Debug: Traceback (most recent call last): File "/usr/bin/
ain__": main() File "/usr/bin/
, in check_last_manifest last_backup_
ine 128, in check_manifests if local_manifest: remote_manifest = local_manifest UnboundLocalError: local variable 'local_manif
est' referenced before assignment
And this one when we are looking at the initial backup:
Jul 15 01:26:59 Debug: duplicity --no-print-
Jul 15 01:27:12 Debug: No signatures found, switching to full backup. Traceback (most recent call last): File "/usr/bin/
I know what you're gonna say: its a duplicity problem. The problem with that is that duplicity works with the same arguments from the command line, and in a simple scheduled cron job (what I've fallen back to). Everyone knows duplicity is a little bit unstable, but I think that this is really some issue with the environment the duplicity command is being executed in or something.
| Marco Rodrigues (gothicx) wrote : | #1 |
| Changed in backupninja: | |
| importance: | Undecided → Low |
| assignee: | nobody → gothicx |
| status: | New → Incomplete |
| lstewart (agrodellic) wrote : | #2 |
Nope. Now I get what you see below. I abandoned backup ninja a while back and went with my shell scripts, and then just last weekend I tried backupninja again, but had little luck.
Yep I'm using Gutsy... You want me to file a different report for this one?
Also I had gpg dump a list of available keys ( gpg --list-secret-keys ), and the required key shows up. Also, as with the previous problem, the duplicity command that backupninja spits out works fine from the command line, as-is.
Cheers!
Dec 12 23:14:37 Info: >>>> starting action /etc/backup.
Dec 12 23:14:37 Debug: yes
Dec 12 23:14:37 Debug: ssh -o IdentityFile=
Dec 12 23:14:38 Debug: Connected to mail.sevaserver.org as lstewart successfully
Dec 12 23:14:39 Debug: Data will be encrypted with the GnuPG key 83AF64BC.
Dec 12 23:14:39 Debug: Data won't be signed.
Dec 12 23:14:39 Debug: duplicity -v9 --allow-
Dec 12 23:14:42 Debug: Main action: inc Running 'sftp -o IdentityFile=
Dec 12 23:14:42 Fatal: Duplicity failed.
Dec 12 23:14:42...
| lstewart (agrodellic) wrote : | #3 |
"Also I had gpg dump a list of available keys ( gpg --list-secret-keys ), and the required key shows up. Also, as with the previous problem, the duplicity command that backupninja spits out works fine from the command line, as-is."
From within the dupl action, dupl.in, or w/e.
| Buttay (cyril-buttay) wrote : | #4 |
I also have a problem running duplicity via backupninja:
on its own, duplicity works:
$ export PASSPHRASE=
$ duplicity --full --no-print-
(the duplicity command is a copy of the one generated by the backupninja script)
however, running backupninja fails (line breaks added for readability):
backupninja --debug --run /etc/backup.
Debug: check_perms /etc/backup.d
Debug: perms: drwxrwx---
Debug: gperm: rwx
Debug: wperm: ---
Debug: check_perms /etc/backup.
Debug: perms: -rw-------
Debug: gperm: ---
Debug: wperm: ---
Info: >>>> starting action /etc/backup.
Debug: yes
Debug: ssh -o PasswordAuthent
Debug: Connected to host as login successfully
Debug: Data will be encrypted with the GnuPG key XXXXXXXX.
Debug: Data will be signed will the GnuPG key XXXXXXXX.
duplicity --full --no-print-
Debug: Warning, found incomplete backup sets, probably left from aborted session No signatures found, switching to full backup. Traceback (most recent call last):
File "/usr/bin/
File "/usr/bin/
File "/usr/bin/
File "/usr/bin/
File "/usr/lib/
File "/usr/lib/
File "/usr/lib/
File "/usr/lib/
File "/usr/lib/
| Buttay (cyril-buttay) wrote : | #5 |
I just noticed that the --ssh-command issue I mentionned at the end of the message above is already fixed by the latest version of backupninja upstream:
http://
regards
Cyril
| Changed in backupninja: | |
| assignee: | gothicx → nobody |
| Mark Edgington (edgimar) wrote : | #6 |
See http://
| Greg Grossmeier (greg.grossmeier) wrote : | #7 |
Marking as fix released as Jaunty has 0.9.6.4 (which is newer than the version which is said to fix this issue).
If you still have problems, please feel free to open a new bug report.
Thanks!
| Changed in backupninja: | |
| status: | Incomplete → Fix Released |
| Changed in backupninja (Debian): | |
| status: | Unknown → Fix Released |


Do you still have this problem ? You're using Gutsy ?