We've been seeing it quite a lot recently, but I have not figured out
what it means yet. It *looks* like replication results in an error on
either the server or the client which does not return a nice (json
encodable) error message, but instead an erlang process id.
Could you maybe attach the
*** This bug is a duplicate of bug 665024 ***
https://bugs.launchpad.net/bugs/665024
Marking this as a duplicate, please add your logs at
https://bugs.launchpad.net/ubuntuone-servers/+bug/665024
** This bug has been marked a duplicate of bug 665024
Desktopcouch doesn't replicate with
Thanks for the tip, Eric!
One problem I'm having is that I can't seem to delete the
gwibber_accounts and gwibber_preferences databases. I know that
these are being blocked from replication, but they still get created on
all my machines, and desktopcouch still tries to replicate to/from these
DB.
Okay, another little tidbit I've observed: it looks like the replication
of dmedia is failing upon trying to replicate the first doc with
attachments... failing with a JSON encoding error:
Traceback (most recent call last):
File
One thing to note is that I can replicate from desktopcouch to the
system-wide CouchDB (I do this often for testing). So it doesn't seem
like the problem is CouchDB being fundamentally unable to replicate this
DB, but more an issue with network timeouts or something when
replicating to the remote
There are load problems on at least one of the couchdb servers, which we
are investigating with the assistance of couch one, so that could be one
possible cause, though I would expect less consistent failure in that
case. Note that what we have running on our servers is not 100% the same
as what
** Changed in: desktopcouch (Ubuntu)
Assignee: (unassigned) = Eric Casteleijn (thisfred)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/786456
Title:
desktopcouch wont replicate dmedia DB
--
All your machines should replicate completely independently from
eachother, yes. So if neither of your machines are replicating
successfully, while other databases are, something about the dmedia
database is breaking replication. You could try removing it locally, to
see if that has an effect, but
Hello,
It looks like occasionally dmedia database is synced (that's the output
of ubuntuone-desktopcouch-diag.py from ubuntuone-scripts):
--- dmedia ---
dmedia - https://couchdb.one.ubuntu.com/u%2F69b%2Fa53%2F210959%2Fdmedia:
8 attempts, 3 failed (3 seen), 5 succeeded (62%)
** Changed in: desktopcouch (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/786456
Title:
desktopcouch wont replicate dmedia DB
--
ubuntu-bugs mailing list
If it does keep consistently failing, you may want to look at recent
document edits/additions, to see whether you've hit this bug in couchdb
itself:
https://issues.apache.org/jira/browse/COUCHDB-1176
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Thanks Roman, thanks Eric.
To test again, I deleted the dmedia DB on my workstation.
desktopcouch recreated it the next time it tried to sync dmedia from
U1 (so I have an empty dmedia with update seq 0), and then I get this
error in the log:
ResourceNotFound: ('db_not_found', 'could not open
Oh, forgot to run ubuntuone-couchdb-query. Here's output:
jderose@jgd-ws:/tmp$ python ubuntuone-couchdb-query dmedia
** Attachment added: desktop-couch-replication.log
https://bugs.launchpad.net/bugs/786456/+attachment/2138294/+files/desktop-couch-replication.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Attached dmedia.couch as it currently exists on my laptop... not sure if
this is ever getting synced correctly to U1 in the first place.
** Attachment added: dmedia.couch.bz2
https://bugs.launchpad.net/ubuntu/+source/desktopcouch/+bug/786456/+attachment/2138325/+files/dmedia.couch.bz2
--
This is replication log from my laptop, can perhaps shed light on what
might be happening at other end.
** Attachment added: desktop-couch-replication.log
https://bugs.launchpad.net/ubuntu/+source/desktopcouch/+bug/786456/+attachment/2138339/+files/desktop-couch-replication.log
--
You
16 matches
Mail list logo
