Ticket #937: irclog.txt

 <Guest50815> hello everybody:  I'm having trouble creating an introducer.   The logs tell me the config file is missing the [client]introducer.furl entry.  This seems to be a chicken-egg type problem.
[11:20] <secorp> When you run an introducer, it automatically generates the introducer.furl
[11:20] <secorp> So, are you getting the error when trying to run the introducer?
[11:20] <Guest50815> yes
[11:20] <Guest50815> To construct an introducer, create a new base directory for it (the name of the directory is up to you), cd into it, and run "path-to-the-tahoe-bin-directory/tahoe create-introducer .". Now run the introducer using "tahoe run .". After it starts, it will write a file named introducer.furl in that base directory. This file contains the URL the other nodes must use in order to connect to this introducer.
[11:21] <Guest50815> I think I'm following these directions...
[11:21] <secorp> Yes, those look right
[11:21] <secorp> 1 sec, let me run through an installation with that step
[11:22] <Guest50815> blarsen@blarsen:~$ rm -rf tahoe
[11:22] <Guest50815> blarsen@blarsen:~$ mkdir tahoe
[11:22] <Guest50815> blarsen@blarsen:~$ cd tahoe
[11:22] <secorp> Ok, so, when I run through that
[11:22] <Guest50815> blarsen@blarsen:~/tahoe$ ~/build/allmydata-tahoe-1.6.0/bin/tahoe create-introducer .
[11:22] <Guest50815> Introducer created in .
[11:22] <Guest50815> b
[11:23] <Guest50815> blarsen@blarsen:~/tahoe$ ~/build/allmydata-tahoe-1.6.0/bin/tahoe run -C .
[11:23] <Guest50815> t then just returns
[11:24] <Guest50815> and logs/tahoesvc.log contains  allmydata.node.MissingConfigEntry: /home/blarsen/tahoe/tahoe.cfg is missing the [client]introducer.furl entry in its last line
[11:24] <secorp> Can you try the following
[11:24] <Guest50815> and I don't see an introducer.furl
[11:24] <secorp> right
[11:24] <secorp> Try this
[11:25] <secorp> $ tahoe create-introducer test_introducer_directory
[11:25] <secorp> $ tahoe start test_introducer_directory
[11:25] <secorp> Note the two differences, using a name for the directory and using "start", not "run"
[11:26] <secorp> Which platform are you on?
[11:26] <Guest50815> introducer node probably started
[11:26] <Guest50815> and furl created
[11:26] <secorp> Cool, I'll try out the steps that you first tried and see why they broke
[11:27] <secorp> I have a feeling that it's something to do with using "." as the target directory
[11:27] <secorp> Thanks for trying it out
[11:27] <secorp> Now that you have a running introducer
[11:27] <Guest50815> ubuntu 9.04 and 9.10.   Broke both using the Karmic ubuntu install, a 1.5 easy_install on 9.04 and a 1.6 build on 9.04
[11:27] <secorp> You can use:
[11:27] <secorp> $ tahoe create-client node01
[11:28] <secorp> Then, copy the introducer.furl contents into node01/tahoe.cfg
[11:28] <secorp> and then
[11:28] <secorp> $ tahoe start node01
[11:29] <secorp> Yeah, ubuntu karmic is one of our standard platforms, so I should be able to replicate it
[11:29] <secorp> one sec
[11:30] <secorp> Also, if you edit the test_introducer_directory/tahoe.cfg
[11:30] <secorp> you can configure a web port for it to be available on
[11:30] <secorp> and then if you hit that with a browser, you can see the status and connections of the introducer
[11:30] <secorp> Here's an example
[11:31] <secorp> (1 sec while I dig up the url)
[11:35] <secorp> http://secorp.net:9125/
[11:35] <secorp> I just brought that up
[11:35] <secorp> Now I'll start up a couple nodes on it
[11:37] <Guest50815> got a "connected to introducer" from a client node after fixing my firewall
[11:38] <secorp> Cool
[11:38] <secorp> if you hit: http://secorp.net:9125/
[11:38] <secorp> I just brought up a 3-node grid
[11:38] <secorp> That's the introducer
[11:39] <kpreid> boingboing commenter says: “Could this be a "mojonation" that's workable?”
[11:39] <kpreid> Someone answer that?
[11:39] <Guest50815> can anybody connect to my introducer now?   They can't get at my files, but they could store their own files on it, right?
[11:40] <secorp> If your introducer is publicly accessible, then people who guess the furl can get to it
[11:41] <secorp> that is very difficult to guess
[11:41] <Guest50815> ight, that looks pretty hard to guess.  :)
[11:41] <Guest50815> thanks very much for your help!
[11:41] <secorp> You'd have to guess a string like: thpthripvmzdh7vz4bapyoezxfludmpy
[11:41] <secorp> That's cool that you got it up and working
[11:41] <secorp> Let us know what you do with it (if anything)
[11:42] <Guest50815> friendnet backup
[11:42] <Guest50815> is the plan
[11:42] <secorp> We have this IRC channel, and also there is a tahoe-dev mailing list
[11:42] <secorp> Cool
[11:42] <secorp> http://allmydata.org has the details on the mailing list
[11:43] <Guest50815> perhaps  http://allmydata.org/source/tahoe/trunk/docs/running.html should be fixed
[11:43] <secorp> Let me look at it, 1 sec
[11:44] <secorp> I will follow the directions and see what breaks, then fix the doc
[11:44] <secorp> Thanks for finding that
[11:49] <Guest50815> as you said, it's either the "." or the use of "run" instead of "start"
[11:50] <secorp> Cool, I am getting the same error
[11:50] <secorp> It's the "tahoe run ." that is not working for some reason
[11:51] <secorp> I'll change the docs, and then we can try to figure out why that isn't working