Opened at 2011-03-11T20:20:02Z

Last modified at 2020-01-16T20:25:18Z

#1377 closed defect

"tahoe start" claims to have started when it didn't (due to port number conflict) — at Version 4

Reported by: zooko Owned by: davidsarah
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 (4)

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 :-)

Note: See TracTickets for help on using tickets.