As I cannot reopen this issue (which properly does not make sense
anyway) have I opened a new Bug #1294201 which explains the issue again
how I still experience it even with duplicity including bug fix provided
for this issue.
--
You received this bug notification because you are a member of Ubun
I have the same symptoms, after upgrading (downgrading?) from 12.04 to
13.10. My deja-dup backups to Ubuntu One are failing after 10 to 15
minutes, with the "after 5 attempts" disconnect message. This is really
annoying after it worked fine under 12.04. (3.11.0-17-generic #31-Ubuntu
SMP Mon Feb 3
I have the exact error described in this bug description even with this
fix included in duplicity.
I am using 13.10 with duplicity 0.6.21-0ubuntu4.1.
Is anyone else still experiencing this error?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** Changed in: duplicity
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1161599
Title:
Backup to Ubuntu one failed, after 5 attempts status 400 bad reques
** Branch linked: lp:ubuntu/raring-proposed/duplicity
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1161599
Title:
Backup to Ubuntu one failed, after 5 attempts status 400 bad request
To manage not
** Branch linked: lp:debian/duplicity
** Branch linked: lp:ubuntu/duplicity
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1161599
Title:
Backup to Ubuntu one failed, after 5 attempts status 400 bad
This bug was fixed in the package duplicity - 0.6.21-0ubuntu1.1
---
duplicity (0.6.21-0ubuntu1.1) raring; urgency=low
* debian/patches/01u1backend.dpatch:
- Backport some fixes for avoiding "400" errors when backing up to
Ubuntu One. Patch by Christopher Townsend. LP: #1
Just to add I have been getting this bug since I updated to 13.04. Just did the
install from "proposed" (hope I did it right) and testing now.
...it's also doing a restore test (I guess it's been a while)hmmm, looks
like I forgot my passwordok, got the password, but it seems to not be
So I have duplicity 0.6.21-0ubuntu1.1. Now my backup finished with an unknown
error:
Traceback (most recent call last):
File "/usr/bin/duplicity", line 1411, in
with_tempdir(main)
File "/usr/bin/duplicity", line 1404, in with_tempdir
fn()
File "/usr/bin/duplicity", line 1338, in ma
Can confirm that the fix works.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1161599
Title:
Backup to Ubuntu one failed, after 5 attempts status 400 bad request
To manage notifications about this
Verified. My backup was done and since my backup was due for a while it
even checked my existing backup. No troubles. Temme what to do if you
need more info.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ub
Hey Cho,
um. read the previous comment once more.
In short,
1) Goto software sources and add raring-proposed.
2) Then as per this link (https://wiki.ubuntu.com/Testing/EnableProposed) to
enable only partial update from the proposed channel create a
/etc/apt/preferences file with the given par
Hello everybody,
How can I update to this version?
Thank you,
Cho
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1161599
Title:
Backup to Ubuntu one failed, after 5 attempts status 400 bad request
Hello Colin, or anyone else affected,
Accepted duplicity into raring-proposed. The package will build now and
be available at
http://launchpad.net/ubuntu/+source/duplicity/0.6.21-0ubuntu1.1 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
http
This bug was fixed in the package duplicity - 0.6.21-0ubuntu2
---
duplicity (0.6.21-0ubuntu2) saucy; urgency=low
* debian/patches/01u1backend.dpatch:
- Backport some fixes for avoiding "400" errors when backing up to
Ubuntu One. Patch by Christopher Townsend. LP: #116159
Christopher Townsend wrote the patch, I'm just doing the paperwork of
uploading it. :)
I've uploaded to saucy and to raring. I've subscribed ubuntu-sru for
the raring one.
** Description changed:
+ [Impact]
+ Users on Ubuntu 13.04 can't reliably back up to Ubuntu One. Any hiccup in an
upload
Michael:
This fixed the problem for me. Thanks for your work.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1161599
Title:
Backup to Ubuntu one failed, after 5 attempts status 400 bad request
To m
If you put this file in
/usr/share/pyshared/duplicity/backends/u1backend.py does it work?
I've been dragging my feet on pushing this fix to Ubuntu, sorry. I've
had an unrelated problem that made testing difficult.
** Attachment added: "u1backend.py"
https://bugs.launchpad.net/ubuntu/+source/
Try using Back In Time instead of Deja Dup. It works perfectly.
On Sun, May 12, 2013 at 4:45 PM, Jacob Mischka wrote:
> For the record, I just now stumbled across this bug report after getting
> sick of closing deja-dup when it fails on every single boot. I am still
> receiving the 400 error. I'
For the record, I just now stumbled across this bug report after getting
sick of closing deja-dup when it fails on every single boot. I am still
receiving the 400 error. I'm not becoming impatient or anything, simply
reporting that it is affecting another person.
Thank you all.
--
You received t
** Changed in: duplicity (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1161599
Title:
Backup to Ubuntu one failed, after 5 attempts status 400 bad request
Hi All,
I fixed this in the Duplicity source code. The next step is to get it
in the Duplicity package and get it through the Stable Release Update
(SRU) process. I'm not sure what the maintainers of Duplicity plans are
on when they are going to get the SRU going, but I imagine they would be
get
Hi,
I'm just wondering whether there is any progress on this issue. Unfortunately,
this bug makes the Ubuntu backup system unusable for the affected users,
leaving them without a backup of their data. So I believe this creates a
certain level of pressure of eventually fixing this. Thanks!
--
Y
** Also affects: deja-dup
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1161599
Title:
Backup to Ubuntu one failed, after 5 attempts status 400 bad reques
** Changed in: duplicity
Importance: Undecided => Medium
** Changed in: duplicity
Status: In Progress => Fix Committed
** Changed in: duplicity
Milestone: None => 0.6.22
** Changed in: duplicity
Assignee: Christopher Townsend (townsend) => (unassigned)
--
You received this b
So testing with both of my merge proposals, I will still occasionally
see a '400 Bad Request' error or some other error such as a socket error
or a '502 Bad Gateway'. Most of the time, the retry is successful, but
on a rare occasion, I'm seeing all 5 retries fail which causes the
backup to fail.
** Branch linked: lp:~townsend/duplicity/fix-1161599-2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1161599
Title:
Backup to Ubuntu one failed, after 5 attempts status 400 bad request
To manage no
My proposed fix wasn't exactly complete. Will link a new branch to fix
that and submit another merge proposal.
** Changed in: duplicity
Status: Fix Committed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https
** Changed in: duplicity
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1161599
Title:
Backup to Ubuntu one failed, after 5 attempts status 400 bad request
** Branch linked: lp:~townsend/duplicity/fix-1161599
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1161599
Title:
Backup to Ubuntu one failed, after 5 attempts status 400 bad request
To manage noti
** Changed in: duplicity
Status: Confirmed => In Progress
** Changed in: duplicity
Assignee: (unassigned) => Christopher Townsend (townsend)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1
Hi Sidnei,
Great work! The file pointer position crossed my mind, but the 400 Bad
Request was throwing me off.
I now see the commit that broke this: http://bazaar.launchpad.net
/~duplicity-team/duplicity/0.6-series/revision/901 in
duplicity/backends/u1backend.py. It went from using a bytearray
** Also affects: duplicity
Importance: Undecided
Status: New
** Changed in: duplicity
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1161599
Title:
Backup t
Confirmed that this fixes the problem. When rewinding the file handle on
retry the subsequent PUT request *does* succeed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1161599
Title:
Backup to Ubunt
Actually it might be more obvious than it seems.
When the PUT request is done, an open file handle is passed as the
'body' argument to httplib2 request(). Since there was a timeout and
retry, the file handle was read from so the current position in the file
has moved. There's no seek() back to the
Looking at the way that httplib2 catches exceptions, if there's for
example a socket.timeout the conn object is not closed
(https://code.google.com/p/httplib2/source/browse/python2/httplib2/__init__.py#1257)
I suspect that might leave the conn object in a semi-broken state.
Since duplicity instant
We've managed to rule out an application error. Those '400 Bad Request'
are being returned by Apache, so we have great confidence than somehow a
malformed request is being sent, which Apache then rejects.
Here's a breakdown of Status 400 failures from the Apache logs over the
course of ~24h:
Pyth
Hi Colin,
Thanks! Knowing that 12.04 works today is a good data point.
I'm working with the U1 folks to help diagnose this. Hopefully they can
help shed some light on this.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bu
Hi Christopher
I use it on two machines, one running 12.04 and one 13.04 and have only seen it
on 13.04. I was not using it on 13.04 prior to 28 March when I reported this
bug so I don't know whether it was present in 13.04 prior to that date.
--
You received this bug notification because you
Hi Colin,
I started noticing this issue on 13.04 around the beginning to middle of
March or so. I have not tried this on 12.04 in some time. Are you able
to do a backup to U1 with 12.04 recently?
What is strange that a retry of the same PUT request gets the '400 Bad
Request' error every time.
It is interesting that I have never seen the problem on 12.04. That
suggests that it is not just a problem on the Ubuntu One server, unless
the error recovery in httlib2 has changed in a way that triggers the
problem on the server. Or perhaps the initial error is caused by a bug
in the client (or
I think there are two issues going on here.
The first issue that occurs during or right after a file is uploaded.
The python httplib code does a call to get a response from the server
for the packet sent. It appears there may be a transient error such a
socket timeout or something up with the res
I'm quite convinced this issue is not anything in Deja Dup, so I'm
setting that bug invalid.
I'm still not really sure what the real issue is. I've done quite a bit
of experimentation and still unable to pin this on duplicity, ssl, or
even the Ubuntu One server. I have gathered a Wireshark trace
After doing some research, it appears that when an "SSLError: The read
operation timed out" occurs, the connection is closed. In the code that
handles this, there is a retry loop, but the retry loop does not re-set
up the connection, so I believe this is the source of the "Bad Request".
It's not c
I upped the verbosity of the duplicity command, and here is the Python
backtrace of the read operation timeout:
Level 1:duplicity:Backtrace of previous error: Traceback (innermost last):
File "/usr/lib/python2.7/dist-packages/duplicity/backends/u1backend.py", line
80, in request
resp, conte
** Also affects: duplicity (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1161599
Title:
Backup to Ubuntu one failed, after 5 attempts status 400
Well, the duplicity only command failed as well with the "400 Bad
Request" error, so this seems to either be a problem in duplicity or how
Ubuntu One is handling something. It seems to prompted by a read
operation timeout.
Here is the snippet of duplicity output with the failure:
uploading file
Bah, it failed:(
I'm going to let the duplicity backup run and see if it fails anywhere
along the way.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1161599
Title:
Backup to Ubuntu one failed, afte
So after using the duplicity command line mentioned above and then
killing that backup and then running a backup through deja dup, it is
working so far now. It hasn't completed the backup yet, but it has
gotten farther than it had in quite some time.
--
You received this bug notification becaus
I've been having this problem in Raring for a few months now. I started
doing some investigating and tried running the same duplicity command
that deja-dup spawns. When I do that, duplicity asks for my Ubuntu One
email address and then password. I'm beginning to think that deja-dup
is not handli
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: deja-dup (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1161599
Title:
B
** Description changed:
- On Raring using deja-dup to backup to Ubuntu one, if the backup includes new
folders and is larger than a few tens of MB then the process apparently hangs
at the start of the upload operation for some tens of minutes and then fails
with a popup "Backup Failed. Giving u
52 matches
Mail list logo
