| 2009-02-02 22:16:56 |
Tobias Baldauf |
bug |
|
|
added bug |
| 2009-02-03 01:27:51 |
Michael Terry |
deja-dup: status |
New |
Incomplete |
|
| 2009-02-03 01:27:51 |
Michael Terry |
deja-dup: importance |
Undecided |
Medium |
|
| 2009-02-03 01:27:51 |
Michael Terry |
deja-dup: statusexplanation |
|
Thank you for the bug report!
Hmm, it stops halfway through? Here's a way to get a log: set the DEJA_DUP_DEBUG environment variable to 1:
export DEJA_DUP_DEBUG=1
deja-dup > /tmp/deja-dup.log
Now, that will create a giant, incredibly verbose log with lots of information about your files. Only the very end is probably interesting. Last 50 lines or so? Almost certainly, duplicity is aborting with a Python exception. I should probably make the exception visible so users like you that have a problem can more easily report it.
It's also bad that we create zombie duplicities... Hrm. |
|
| 2009-02-03 01:28:05 |
Michael Terry |
deja-dup: importance |
Medium |
High |
|
| 2009-02-03 01:28:05 |
Michael Terry |
deja-dup: statusexplanation |
Thank you for the bug report!
Hmm, it stops halfway through? Here's a way to get a log: set the DEJA_DUP_DEBUG environment variable to 1:
export DEJA_DUP_DEBUG=1
deja-dup > /tmp/deja-dup.log
Now, that will create a giant, incredibly verbose log with lots of information about your files. Only the very end is probably interesting. Last 50 lines or so? Almost certainly, duplicity is aborting with a Python exception. I should probably make the exception visible so users like you that have a problem can more easily report it.
It's also bad that we create zombie duplicities... Hrm. |
|
|
| 2009-02-03 12:07:11 |
Tobias Baldauf |
bug |
|
|
added attachment 'deja-dup.log' (deja-dup.log) |
| 2009-02-03 13:43:30 |
Michael Terry |
deja-dup: status |
Incomplete |
Confirmed |
|
| 2009-02-03 13:43:30 |
Michael Terry |
deja-dup: assignee |
|
mterry |
|
| 2009-02-03 13:43:30 |
Michael Terry |
deja-dup: statusexplanation |
|
OK, I think I understand the sequence now.
It seems you have files left over from an incomplete/cancelled backup on your sever.
When Deja Dup starts up, it first connects and scans the files in the target location.
Seeing unused backup files (from the cancelled backup), it initiates a 'cleanup' operation before continuing with the backup.
For some reason, it can't connect to the SSH server for the 'cleanup' operation, and bails on you.
You say you cleaned up the files on the backend and tried again, with a fresh slate. Then, Deja Dup stopped halfway through with an error. I'd also be interested in a log for this error. It may be a different problem than this one.
But after it stopped halfway through on that fresh backup, the next time Deja Dup runs, it will try to clean up those leftover files (since it can't resume currently), and thus you get back into the cleanup loop.
Basically, it seems Deja Dup isn't correctly passing the password that it clearly knows (because it can log in to do the initial 'ls'). I'm looking into it. It's conceivable I introduced this in a recent version, which explains why it used to work for you.
Thanks for the log, and if you could get me a log for the other stops-halfway-through issue, I'd appreciate it! |
|
| 2009-02-04 01:51:24 |
Michael Terry |
deja-dup: status |
Confirmed |
Fix Released |
|
| 2009-02-04 01:51:24 |
Michael Terry |
deja-dup: statusexplanation |
OK, I think I understand the sequence now.
It seems you have files left over from an incomplete/cancelled backup on your sever.
When Deja Dup starts up, it first connects and scans the files in the target location.
Seeing unused backup files (from the cancelled backup), it initiates a 'cleanup' operation before continuing with the backup.
For some reason, it can't connect to the SSH server for the 'cleanup' operation, and bails on you.
You say you cleaned up the files on the backend and tried again, with a fresh slate. Then, Deja Dup stopped halfway through with an error. I'd also be interested in a log for this error. It may be a different problem than this one.
But after it stopped halfway through on that fresh backup, the next time Deja Dup runs, it will try to clean up those leftover files (since it can't resume currently), and thus you get back into the cleanup loop.
Basically, it seems Deja Dup isn't correctly passing the password that it clearly knows (because it can log in to do the initial 'ls'). I'm looking into it. It's conceivable I introduced this in a recent version, which explains why it used to work for you.
Thanks for the log, and if you could get me a log for the other stops-halfway-through issue, I'd appreciate it! |
OK, I found the problem. I had made a change in 7.0 that caused the SSH backend to not correctly tell duplicity the SSH password. I need better testing before a release. :-/
I just released 7.3 to fix it. That may have also fixed your 'halfway' issue, because that may have been when we stopped preparing and start backing up. That would also have run into this bug. Let me know if you have further issues. |
|
| 2009-02-04 01:51:24 |
Michael Terry |
deja-dup: milestone |
|
7.0 |
|
