Manhole binding fails silently #726

New Issue

tahoe-lafs · 2009-06-01T19:34:10Z

zandr commented

2009-06-01 19:34:10 +00:00

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.

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.

tahoe-lafs added the

labels 2009-06-01 19:34:10 +00:00

tahoe-lafs added this to the 1.5.0 milestone 2009-06-01 19:34:10 +00:00

zooko modified the milestone from 1.5.0 to eventually

2009-06-30 18:08:03 +00:00

warner added

code-nodeadmin

and removed

unknown

labels 2009-08-22 19:44:18 +00:00

tahoe-lafs modified the milestone from eventually to soon

2014-09-27 03:20:54 +00:00

warner commented

2016-04-28 05:13:19 +00:00

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.

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.

warner added the

fixed

label 2016-04-28 05:13:19 +00:00

warner modified the milestone from soon to 1.12.0

2016-04-28 05:13:19 +00:00

warner closed this issue

2016-04-28 05:13:19 +00:00

Sign in to join this conversation.