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

zooko commented

2011-03-11 20:20:02 +00:00

Owner

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'
$

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' $ ```

tahoe-lafs added the

labels 2011-03-11 20:20:02 +00:00

tahoe-lafs added this to the undecided milestone 2011-03-11 20:20:02 +00:00

davidsarah commented

2012-07-11 23:26:45 +00:00

Author

Owner

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.

tahoe-lafs added

code-nodeadmin

and removed

unknown

labels 2012-07-11 23:26:45 +00:00

tahoe-lafs modified the milestone from undecided to 1.11.0

2012-07-11 23:26:45 +00:00

davidsarah commented

2013-03-12 02:56:21 +00:00

Author

Owner

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

daira commented

2013-06-06 20:03:20 +00:00

Author

Owner

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

daira commented

2014-01-10 19:54:08 +00:00

Author

Owner

See also #2147: web.port can conflict

tahoe-lafs modified the milestone from soon to 1.12.0

2014-04-02 16:13:07 +00:00

zooko commented

2014-04-19 15:42:21 +00:00

Author

Owner

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

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

tahoe-lafs changed title 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

2014-04-19 15:42:21 +00:00

zooko commented

2015-02-10 17:51:25 +00:00

Author

Owner

(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.

daira commented

2015-02-11 16:01:14 +00:00

Author

Owner

(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.

tahoe-lafs modified the milestone from 1.12.0 to 1.11.0

2015-05-11 13:12:46 +00:00

warner commented

2016-03-22 05:02:52 +00:00

Author

Owner

Milestone renamed

tahoe-lafs modified the milestone from 1.11.0 to 1.12.0

2016-03-22 05:02:52 +00:00

warner commented

2016-06-28 18:20:37 +00:00

Author

Owner

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

tahoe-lafs modified the milestone from 1.12.0 to 1.13.0

2016-06-28 18:20:37 +00:00

Brian Warner <warner@lothar.com> commented

2017-09-19 17:20:49 +00:00

Author

Owner

In 04b34b6/trunk:

Merge PR417: rewrite tahoe start/stop/daemonize

* refs ticket:1148 (splits up startstop_node, improves coverage)
* refs ticket:275 ('start' probably doesn't exit until furl is written)
* refs ticket:1121 (probably improves coverage)
* refs ticket:1377 (probably fixed)
* refs ticket:2149 (might influence, probably won't fix)
* refs ticket:719 (probably improved)

In [04b34b6/trunk](/tahoe-lafs/trac-2024-07-25/commit/04b34b6fd2bb112942d2cb8ea41ef11ee4c72347): ``` Merge PR417: rewrite tahoe start/stop/daemonize * refs ticket:1148 (splits up startstop_node, improves coverage) * refs ticket:275 ('start' probably doesn't exit until furl is written) * refs ticket:1121 (probably improves coverage) * refs ticket:1377 (probably fixed) * refs ticket:2149 (might influence, probably won't fix) * refs ticket:719 (probably improved) ```

exarkun commented

2020-01-16 20:25:18 +00:00

Author

Owner

"tahoe start" is now deprecated

tahoe-lafs added the

wontfix

label 2020-01-16 20:25:18 +00:00

exarkun closed this issue

2020-01-16 20:25:18 +00:00

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