b2: large uploads fail due to expired auth token

Bug #1588503 reported by Markus on 2016-06-02
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Duplicity
Medium
Unassigned

Bug Description

duplicity against b2 backend fails after 24 hours (and 2,5 mins due to retrys and waits) with http status 401
It looks very much as the auth token expires and duplicity does not reauthenticate against b2.

Duplicity version: 0.7.07.1
Python version 2.7
OS Distro and version: OSX 10.11.5 / homebrew installation

AsyncScheduler: running task synchronously (asynchronicity disabled)
Writing duplicity-full.20160601T075948Z.vol2013.difftar.gpg
Attempt 1 failed. HTTPError: HTTP Error 401: Unauthorized
Writing duplicity-full.20160601T075948Z.vol2013.difftar.gpg
Attempt 2 failed. HTTPError: HTTP Error 401: Unauthorized
Writing duplicity-full.20160601T075948Z.vol2013.difftar.gpg
Attempt 3 failed. HTTPError: HTTP Error 401: Unauthorized
Writing duplicity-full.20160601T075948Z.vol2013.difftar.gpg
Attempt 4 failed. HTTPError: HTTP Error 401: Unauthorized
Writing duplicity-full.20160601T075948Z.vol2013.difftar.gpg
Giving up after 5 attempts. HTTPError: HTTP Error 401: Unauthorized
Backup: 1442 minutes and 10 seconds elapsed.

Tags: b2 Edit Tag help

Related branches

Markus (mstoll-de) wrote :

I think I have a working fix for this, I am going to test this for some days
(and have to fight with bazaar to get a branch uploaded)

Please propose for merge when you are done testing.

On Sat, Jun 4, 2016 at 2:08 PM, Markus <email address hidden> wrote:

> ** Branch linked: lp:~mstoll-de/duplicity/b2-reautch
>
> ** Branch linked: lp:~mstoll-de/duplicity/b2-reauth
>
> --
> You received this bug notification because you are subscribed to
> Duplicity.
> https://bugs.launchpad.net/bugs/1588503
>
> Title:
> b2: large uploads fail due to expired auth token
>
> Status in Duplicity:
> New
>
> Bug description:
> duplicity against b2 backend fails after 24 hours (and 2,5 mins due to
> retrys and waits) with http status 401
> It looks very much as the auth token expires and duplicity does not
> reauthenticate against b2.
>
> Duplicity version: 0.7.07.1
> Python version 2.7
> OS Distro and version: OSX 10.11.5 / homebrew installation
>
> AsyncScheduler: running task synchronously (asynchronicity disabled)
> Writing duplicity-full.20160601T075948Z.vol2013.difftar.gpg
> Attempt 1 failed. HTTPError: HTTP Error 401: Unauthorized
> Writing duplicity-full.20160601T075948Z.vol2013.difftar.gpg
> Attempt 2 failed. HTTPError: HTTP Error 401: Unauthorized
> Writing duplicity-full.20160601T075948Z.vol2013.difftar.gpg
> Attempt 3 failed. HTTPError: HTTP Error 401: Unauthorized
> Writing duplicity-full.20160601T075948Z.vol2013.difftar.gpg
> Attempt 4 failed. HTTPError: HTTP Error 401: Unauthorized
> Writing duplicity-full.20160601T075948Z.vol2013.difftar.gpg
> Giving up after 5 attempts. HTTPError: HTTP Error 401: Unauthorized
> Backup: 1442 minutes and 10 seconds elapsed.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/duplicity/+bug/1588503/+subscriptions
>

Never mind.

Changed in duplicity:
importance: Undecided → Medium
milestone: none → 0.7.08
status: New → Fix Committed
Changed in duplicity:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers