Comment 2 for bug 1588503
Revision history for this message
| Kenneth Loafman (kenneth-loafman) wrote Re: [Bug 1588503] Re: b2: large uploads fail due to expired auth token | #2 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
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:/
>
> 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-
> Attempt 1 failed. HTTPError: HTTP Error 401: Unauthorized
> Writing duplicity-
> Attempt 2 failed. HTTPError: HTTP Error 401: Unauthorized
> Writing duplicity-
> Attempt 3 failed. HTTPError: HTTP Error 401: Unauthorized
> Writing duplicity-
> Attempt 4 failed. HTTPError: HTTP Error 401: Unauthorized
> Writing duplicity-
> 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:/
>