#726 closed enhancement (fixed)

Manhole binding fails silently

Reported by: zandr Owned by: Lcstyle
Priority: minor Milestone: 1.12.0
Component: code-nodeadmin Version: 1.4.1
Keywords: usability availability easy error Cc:
Launchpad Bug:

Description (last modified by Lcstyle)

Starting a node where there's a port conflict causing the binding to fail is a silent failure.

Usually it's manhole that gets me, and while the twistd.log contains the error, all you get out of /bin/tahoe is "probably started"

It would be nice if this error was louder, it's an easy mistake to make.

Change History (8)

comment:1 Changed at 2009-06-30T18:08:03Z by zooko

  • Milestone changed from 1.5.0 to eventually

comment:2 Changed at 2009-08-22T19:44:18Z by warner

  • Component changed from unknown to code-nodeadmin
  • Owner nobody deleted

comment:3 Changed at 2009-12-13T02:29:39Z by davidsarah

  • Keywords usability availability added

comment:4 Changed at 2009-12-13T02:29:54Z by davidsarah

  • Keywords easy added

comment:5 Changed at 2010-01-16T01:19:54Z by davidsarah

  • Keywords error added

comment:6 Changed at 2014-09-27T02:56:26Z by Lcstyle

  • Description modified (diff)
  • Owner set to Lcstyle
  • Status changed from new to assigned

comment:7 Changed at 2014-09-27T03:20:54Z by Lcstyle

  • Milestone changed from eventually to soon

comment:8 Changed at 2016-04-28T05:13:19Z by warner

  • Milestone changed from soon to 1.12.0
  • Resolution set to fixed
  • Status changed from assigned to closed

I think this should be fixed, now that node startup is synchronous (#2491, landed in e187fba). Port failures like this will now be signalled to stderr, and "tahoe start" will exit with an error.

Also, manhole got removed entirely in #2367.

Note: See TracTickets for help on using tickets.