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