web.port can conflict #2147

New Issue

tahoe-lafs · 2014-01-08T20:24:04Z

joeyh commented

2014-01-08 20:24:04 +00:00

I created 2 separate tahoe nodes on my laptop, and got some very surprising behavior. It turned out that tahoe create-node puts in a default web.port, and if 2 nodes have the same port, any tahoe command will assume that, since it connects to the configured port, it's talking with the right node.

This impacts at least the git-annex tahoe special remote, which sets up a tahoe node for the user. Users sometimes have more than 1 git-annex repository, and so will try to set up separate tahoe special remotes (which might connect back to the same grid, or not).

It would be great if web.port could be set to something like tcp:any:interface=127.0.0.1, and then tahoe start could just pick any free port.

I created 2 separate tahoe nodes on my laptop, and got some very surprising behavior. It turned out that tahoe create-node puts in a default web.port, and if 2 nodes have the same port, any tahoe command will assume that, since it connects to the configured port, it's talking with the right node. This impacts at least the git-annex tahoe special remote, which sets up a tahoe node for the user. Users sometimes have more than 1 git-annex repository, and so will try to set up separate tahoe special remotes (which might connect back to the same grid, or not). It would be great if web.port could be set to something like tcp:any:interface=127.0.0.1, and then tahoe start could just pick any free port.

tahoe-lafs added the

labels 2014-01-08 20:24:04 +00:00

tahoe-lafs added this to the undecided milestone 2014-01-08 20:24:04 +00:00

zooko added

code-nodeadmin

and removed

unknown

labels 2014-01-08 23:32:39 +00:00

zooko commented

2014-01-08 23:36:26 +00:00

Note that the node currently does this desired behavior for client.port ([docs]source:trunk/docs/configuration.rst?rev=0bebbe3290614dcb26be2de1c0e9edc3951ac137#overall-node-configuration, [source]source:trunk/src/allmydata/node.py?rev=ff64a0fef5879d3651bc3db6ca0522d96b217d45#L372), so this ticket would be to make web.port behave similarly to client.port.

Note that the node currently does this desired behavior for `client.port` ([docs]source:trunk/docs/configuration.rst?rev=0bebbe3290614dcb26be2de1c0e9edc3951ac137#overall-node-configuration, [source]source:trunk/src/allmydata/node.py?rev=ff64a0fef5879d3651bc3db6ca0522d96b217d45#L372), so this ticket would be to make `web.port` behave similarly to `client.port`.

zooko commented

2014-01-08 23:49:05 +00:00

This is one of two issues blocking the git-annex↔LAFS integration, as mentioned here: http://source.git-annex.branchable.com/?p=source.git;a=commitdiff;h=85272d8a988b249d755ac3f8133e2bf8126fb271 . The other is #2149.

This is one of two issues blocking the git-annex↔LAFS integration, as mentioned here: <http://source.git-annex.branchable.com/?p=source.git;a=commitdiff;h=85272d8a988b249d755ac3f8133e2bf8126fb271> . The other is #2149.

daira commented

2014-01-10 19:52:58 +00:00

See also #1377: "tahoe start" claims to have started when it didn't (due to port number conflict)

joeyh commented

2014-04-01 01:02:26 +00:00

This is blocking adding easy point-n-click configuration of tahoe in the git-annex webapp.
I could arbitraily limit it to one tahoe remote to avoid the problem, but that doesn't feel right.

This is blocking adding easy point-n-click configuration of tahoe in the git-annex webapp. I could arbitraily limit it to one tahoe remote to avoid the problem, but that doesn't feel right.

tahoe-lafs modified the milestone from undecided to 1.12.0

2014-04-02 16:11:36 +00:00

warner commented

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

Milestone renamed

warner modified the milestone from 1.12.0 to 1.13.0

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

warner commented

2016-06-28 18:17:14 +00:00

renaming milestone

warner modified the milestone from 1.13.0 to 1.14.0

2016-06-28 18:17:14 +00:00