Re: [Duplicity-talk] Fwd: AssertionError on every attempt

[Rupert Levene]

Here are what I think are relevant extracts from my logs.

First backup (I have added extra logging to the pydrive code. The
size=-1 is the return value from _query)
all proceeds as expected until:
Jun 05 02:56:45 Start pydrive _put, source
/tmp/duplicity-dZ6gzc-tempdir/mktemp-NAK2b5-4755, remote
duplicity-full.20150604T160946Z.vol4754.difftar.gpg
Jun 05 02:56:47 End pydrive _put
Jun 05 02:56:47 Start pydrive _query, filename
duplicity-full.20150604T160946Z.vol4754.difftar.gpg
Jun 05 02:56:47 Start pydrive FilesList
Jun 05 02:57:19 End pydrive _query, size=-1
Jun 05 02:57:19 File
duplicity-full.20150604T160946Z.vol4754.difftar.gpg was corrupted
during upload.
Jun 05 02:57:19 02:57:19.669 Task 'FULL' failed with exit code '44'.
Jun 05 02:57:19 --- Finished state FAILED 'code 44' at 02:57:19.669 -
Runtime 09:47:38.163 ---
...
verify then completes successfully:
Jun 05 06:34:12 Verify complete: 40837 files compared, 0 differences found.
Jun 05 06:34:12 --- Finished state OK at 06:34:12.974 - Runtime 03:36:53.290 ---


Near beginning of next backup:
Jun 06 03:00:19 RESTART: Volumes 4754 to 4754 failed to upload before
termination
Jun 06 03:00:19          Restarting backup at volume 4754.
(then duplicity-full.20150604T160946Z.vol4754.difftar.gpg is uploaded,
probably creating a duplicate)
....
During subsequent verify, cutting out the middle of an immensely long line:
Jun 06 22:00:30 AssertionError: ({4754: 'dupli......83.difftar.gpg'},
'duplicity-full.20150604T160946Z.vol4754.difftar.gpg')

Rupert


On 9 June 2015 at 22:15,  <address@hidden> wrote:
> On 09.06.2015 22:47, Scott McKenzie wrote:
>>
>>
>> On 10 June 2015 at 06:38, <address@hidden <mailto:address@hidden>> wrote:
>>
>>     that seems to be the local file's size. and i don't see the return value 
>> of this put method reused anywhere.
>>
>>     ..ede/duply.net <http://duply.net>
>>
>>
>> The code would never reach that point.  That function calls validate_block 
>> after "putting" the file.  validate_block (which calls query() on the 
>> backend) will throw a fatal error if the file size returned by the backend 
>> does not equal the local file size.  I'm assuming fatal mean program 
>> execution stops.  If so this would be the crash Robert reported in his 
>> original email.
>>
>
> ic.. thanks! it'd be interesting to see the errorstack to determine what size 
> pydrive actually returned.
>
> @Rupert: do you have kept the logs?
>
> also the fatal error does not make sense there. in case of of a corrupted 
> upload the upload should be retried --num-retries times.
>
> ..ede/duply.net
>
> _______________________________________________
> Duplicity-talk mailing list
> address@hidden
> https://lists.nongnu.org/mailman/listinfo/duplicity-talk