desktopcouch restart fails a lot on my n900
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
desktopcouch |
Confirmed
|
Undecided
|
Ubuntu One Client Engineering team |
Bug Description
example:
sbox-FREMANTLE_X86: ~] > run-standalone.sh dbus-send --session --dest=
method return sender=:1.71 -> dest=:1.72 reply_serial=2
int32 54490
[sbox-FREMANTLE
method return sender=:1.71 -> dest=:1.73 reply_serial=2
int32 54490
[sbox-FREMANTLE
[sbox-FREMANTLE
Desktop CouchDB is not running; starting it. Removing stale, deceptive pid file.
Apache CouchDB 0.10.0 (LogLevel=info) is starting.
Failure to start Mochiweb: eaddrinuse
[error] [<0.61.0>] {error_
[error] [<0.51.0>] {error_
{"init terminating in do_boot"
...waiting for couchdb to start...
...waiting for couchdb to start...
...waiting for couchdb to start...
...waiting for couchdb to start...
...waiting for couchdb to start...
...waiting for couchdb to start...
...waiting for couchdb to start...
...waiting for couchdb to start...
...waiting for couchdb to start...
...waiting for couchdb to start...
...waiting for couchdb to start...
...waiting for couchdb to start...
...waiting for couchdb to start...
...waiting for couchdb to start...
...waiting for couchdb to start...
...waiting for couchdb to start...
...waiting for couchdb to start...
...waiting for couchdb to start...
...waiting for couchdb to start...
...waiting for couchdb to start...
...waiting for couchdb to start...
...waiting for couchdb to start...
...waiting for couchdb to start...
...waiting for couchdb to start...
...waiting for couchdb to start...
...waiting for couchdb to start...
...waiting for couchdb to start...
...waiting for couchdb to start...
...waiting for couchdb to start...
...waiting for couchdb to start...
...waiting for couchdb to start...
...waiting for couchdb to start...
...waiting for couchdb to start...
...waiting for couchdb to start...
...waiting for couchdb to start...
...waiting for couchdb to start...
...waiting for couchdb to start...
...waiting for couchdb to start...
...waiting for couchdb to start...
...waiting for couchdb to start...
...waiting for couchdb to start...
...waiting for couchdb to start...
...waiting for couchdb to start...
...waiting for couchdb to start...
...waiting for couchdb to start...
...waiting for couchdb to start...
...waiting for couchdb to start...
...waiting for couchdb to start...
...waiting for couchdb to start...
...waiting for couchdb to start...
...waiting for couchdb to start...
...waiting for couchdb to start...
...waiting for couchdb to start...
I'm not sure why I'm getting eaddrinuse. I don't know what config desktopcouchis starting couchdb with; is it reusing the same port number from a previous run ? If so, that might explain, and is probably a mistake - it should be using a new, available port; ports can take a while to close.
As reported in a separate bug, it's pretty terrible that desktopcouch cannot properly wait for couchdb to either start up correctly or not. This is going to cause you guys no end of heisenbugs.
Changed in desktopcouch: | |
assignee: | nobody → Ubuntu One Desktop+ team (uone-desktop) |
status: | New → Confirmed |
tags: | added: desktop+ |