#1377 closed defect (wontfix)

"tahoe start" claims to have started when it didn't

Reported by: zooko Owned by: daira
Priority: major Milestone: 1.13.0
Component: code-nodeadmin Version: 1.8.2
Keywords: cli tahoe-start error usability port conflict Cc:
Launchpad Bug:

Description (last modified by daira)

The problem that I reported in #1376 was caused by the gateway failing to start due to the port number already being taken. From its twistd.log:

2011-03-11 11:57:37-0500 [-]   File "/System/Library/Frameworks/Python.framework/Versions/2.6/Extras/lib/python/twisted/internet/tcp.py", line 858, in startListening
2011-03-11 11:57:37-0500 [-]     raise CannotListenError, (self.interface, self.port, le)
2011-03-11 11:57:37-0500 [-] twisted.internet.error.CannotListenError: Couldn't listen on any:9996: [Errno 48] Address already in use.

Looking back through my screen buffer, I see that it misled me into thinking that it had started:

$ tahoe start .
STARTING '/Users/zooko/tmp/d/tmp_create'
$ 

Change History (15)

comment:1 Changed at 2012-07-11T23:26:45Z by davidsarah

  • Component changed from unknown to code-nodeadmin
  • Milestone changed from undecided to 1.11.0
  • Owner changed from nobody to davidsarah
  • Status changed from new to assigned

stercor had this problem after accidentally configuring Apache to listen on port 3456, and I've also had it once or twice. Putting it into milestone 1.11.

comment:2 Changed at 2012-12-11T22:00:59Z by davidsarah

  • Keywords port conflict added

comment:3 Changed at 2013-03-12T02:56:21Z by davidsarah

Zancas just had this problem, and I've had it several times since the last comment. I'm increasingly annoyed by it.

comment:4 Changed at 2013-06-06T20:03:20Z by daira

  • Description modified (diff)

We're at a hack fest in Berlin and a new user is also having this problem. Now I'm annoyed enough to fix it :-)

comment:5 Changed at 2013-06-06T20:04:12Z by daira

  • Owner changed from davidsarah to daira
  • Status changed from assigned to new

comment:6 Changed at 2014-01-10T19:54:08Z by daira

See also #2147: web.port can conflict

comment:7 Changed at 2014-04-02T16:13:07Z by daira

  • Milestone changed from soon to 1.12.0
  • Status changed from new to assigned

comment:8 Changed at 2014-04-19T15:42:21Z by zooko

  • Summary changed from "tahoe start" claims to have started when it didn't (due to port number conflict) to "tahoe start" claims to have started when it didn't

Hey, does http://twistedmatrix.com/trac/ticket/823 fix this?? Or at least help?

comment:9 Changed at 2015-02-10T17:51:25Z by zooko

http://twistedmatrix.com/trac/ticket/823 has been fixed, so if it fixes this ticket, or at least makes it easier for us to fix this ticket, then someone should revisit this ticket.

comment:10 Changed at 2015-02-11T16:01:14Z by daira

http://twistedmatrix.com/trac/ticket/823 makes twistd wait by default, so there is nothing we need to do in Tahoe-LAFS to enable it. We should test whether it actually helps in cases such as #2147.

comment:11 Changed at 2015-05-11T13:12:46Z by daira

  • Milestone changed from 1.12.0 to 1.11.0

comment:12 Changed at 2016-03-22T05:02:52Z by warner

  • Milestone changed from 1.11.0 to 1.12.0

Milestone renamed

comment:13 Changed at 2016-06-28T18:20:37Z by warner

  • Milestone changed from 1.12.0 to 1.13.0

moving most tickets from 1.12 to 1.13 so we can release 1.12 with magic-folders

comment:14 Changed at 2017-09-19T17:20:49Z by Brian Warner <warner@…>

In 04b34b6/trunk:

Merge PR417: rewrite tahoe start/stop/daemonize

comment:15 Changed at 2020-01-16T20:25:18Z by exarkun

  • Resolution set to wontfix
  • Status changed from assigned to closed

"tahoe start" is now deprecated

Note: See TracTickets for help on using tickets.