Crashing in the background
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
| desktopcouch |
High
|
Chad Miller | ||
| desktopcouch (Ubuntu) |
High
|
Chad Miller | ||
| Lucid |
High
|
Chad Miller |
Bug Description
Binary package hint: desktopcouch
My desktopcouch is failing causing things not to sync. Here's what it spits out to the terminal.
jorge@bojack:~$ /usr/lib/
2009-11-02 17:17:23,717 - Skipping weird record. 'service_name'
2009-11-02 17:17:23,717 - Skipping weird record. 'service_name'
2009-11-02 17:17:23,717 - Skipping weird record. 'service_name'
2009-11-02 17:17:32,148 - can't replicate 'u/d67/
Traceback (most recent call last):
File "/usr/lib/
content=record)
File "/usr/lib/
**params)
File "/usr/lib/
resp, data = _make_request()
File "/usr/lib/
body=body, headers=headers)
File "/usr/lib/
(response, content) = self._request(conn, authority, uri, request_uri, method, body, headers, redirections, cachekey)
File "/usr/lib/
(response, content) = self._conn_
File "/usr/lib/
conn.
File "/usr/lib/
self.
File "/usr/lib/
self.
File "/usr/lib/
self.
File "/usr/lib/
self.send(msg)
File "/usr/lib/
self.
File "<string>", line 1, in sendall
error: [Errno 104] Connection reset by peer
ProblemType: Bug
Architecture: amd64
Date: Mon Nov 2 18:07:39 2009
DistroRelease: Ubuntu 9.10
NonfreeKernelMo
Package: desktopcouch 0.5-0ubuntu1
PackageArchitec
ProcEnviron:
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSign
SourcePackage: desktopcouch
Uname: Linux 2.6.31-14-generic x86_64
Jorge Castro (jorge) wrote : | #1 |
Changed in desktopcouch: | |
assignee: | nobody → Chad Miller (cmiller) |
importance: | Undecided → High |
Changed in desktopcouch: | |
status: | New → Triaged |
Changed in desktopcouch (Ubuntu): | |
status: | New → Triaged |
tags: | added: package |
Changed in desktopcouch (Ubuntu): | |
assignee: | nobody → Chad Miller (cmiller) |
Changed in desktopcouch (Ubuntu): | |
importance: | Undecided → High |
Changed in desktopcouch: | |
milestone: | none → lucid-final |
Changed in desktopcouch (Ubuntu): | |
milestone: | none → ubuntu-10.04 |
Chad Miller (cmiller) wrote : | #3 |
I don't see anything to fix.
We catch all exceptions there. That "error: [Errno 104] Connection reset by peer" percolated only up to the caller of the replication for this host. We still retry later, and maybe "connection reset" won't happen then.
Jorge, what do you say? I don't see this is anything. "Crashing" in the title isn't very accurate to describe anything here.
Changed in desktopcouch (Ubuntu Lucid): | |
status: | Triaged → Invalid |
Changed in desktopcouch: | |
status: | Triaged → Invalid |
This is probably in the upstream, but we should catch it and retry. :(