getPort succeeds when desktopcouch isn't running

Bug #422127 reported by Ken VanDine
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Chad Miller
desktopcouch (Ubuntu)
Ken VanDine
Ken VanDine

Bug Description

desktopcouch 0.3 introduced getting the running port number from the desktop-couch.log file... Now desktopcouch reports that it is running and getPort succeeds and apps attempt to connect to a couch instance that is no longer running.

Changed in desktopcouch (Ubuntu):
importance: Undecided → Critical
assignee: nobody → Ken VanDine (ken-vandine)
milestone: none → karmic-alpha-5
Chad Miller (cmiller)
Changed in desktopcouch:
assignee: nobody → Chad Miller (cmiller)
Revision history for this message
Chad Miller (cmiller) wrote :

Reverting the log-file code to the /proc-searching code that we know works. This problem is avoided.

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package desktopcouch - 0.3.1-0ubuntu1

desktopcouch (0.3.1-0ubuntu1) karmic; urgency=low

  [Ken VanDine]
  * debian/control
    - Added depends on python-desktopcouch-records. (LP: #422179)
  [Chad Miller]
  * New upstream release.
  * Changed Vcs-Bzr links in control file.
  * Changed version dependency on couchdb.
  * Converting to a full-blown source-package branch.
  * Fix getPort failure. (LP: #420911, LP: #422127)
  * Check couchdb bind-port in replicator. (LP: #419973)
  * Change couchdb bind-port in pairing tool. (LP: #419969)

 -- Chad Miller <email address hidden> Tue, 01 Sep 2009 11:57:25 -0400

Changed in desktopcouch (Ubuntu Karmic):
status: New → Fix Released
Changed in desktopcouch:
status: New → Fix Released
Chad Miller (cmiller)
tags: added: cmiller-k-alpha6
Chad Miller (cmiller)
Changed in desktopcouch:
milestone: none → w21-karmic-alpha6
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers