Comment 3 for bug 1734144

That is the actual error. The others are all warnings. Do you want one with
-v 9? That will have to wait since I'll be able to access that machine next
week. What about the earlier mail thread where the file size difference is
discussed?

https://raymii.org

On Wed, Jan 3, 2018 at 2:55 PM, edso <email address hidden> wrote:

> can you supply a proper stacktrace to see where the fatal error
> originates?
>
> ..ede/duply.net
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1734144
>
> Title:
> swift $file was corrupted during upload even with retries
>
> Status in Duplicity:
> New
>
> Bug description:
> Command:
>
> duplicity --verbosity 4 --log-file /var/log/duplicity.log --volsize 25
> --tempdir="/tmp" --file-prefix="app1.server8." --name="app1.server8."
> --exclude-device-files --allow-source-mismatch --num-retries 100
> --exclude-filelist=/etc/cloudvps-boss/exclude.conf --full-if-older-
> than="7D" --no-encryption / swift://cloudvps-boss-backup
>
> The backup halts with this error:
>
> ERROR 44 'app1.server8.duplicity-full.20171122T021711Z.vol741.difftar.gz'
> 26197773 -1
> . File app1.server8.duplicity-full.20171122T021711Z.vol741.difftar.gz
> was corrupted during upload.
>
>
> I would suspect it to restart (due to --num-retries 100), but that does
> not happen.
>
> Duplicity version: 0.7.15 (from source)
> Ubuntu 16.04 with that default python (2.7..)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/duplicity/+bug/1734144/+subscriptions
>