[tahoe-dev] Troubleshooting node connectivity

[Peter Secor]

Shawn Willden wrote:
> 
> How can I edit those FURLs?  There's no tahoe.cfg file.  I looked for registry 
> keys, but only found the "Base Dir Path", which points to the 'noderoot' dir.
> 
The default installation directory is C:\Program 
Files\Allmydata\noderoot. Underneath that directory you should see an 
old but familiar directory structure with introducer.furl, helper.furl, 
etc. You can also use a tahoe.cfg file, but this installer uses the old 
style at this point. If you want, that would be a great issue to stick 
into the windows client Trac instance 
(http://allmydata.org/trac/tahoe-w32-client/wiki). Hmmm, it looks like 
it doesn't have tickets enabled, now I need a meta-ticket for that :)

>> I'm also almost ready with the latest trunk build here:
>>
>> http://allmydata.org/tahoe-w32-client/
>>
>> I still have to get the script set up in a cron job and I cannot attest
>> to the build that is currently in that directory, but it soon should
>> start updating with the latest builds.
> 
> The build in that directory doesn't appear to work.  It doesn't create 
> anything under the noderoot directory.  Attempting to manually start the 
> service gives "Error 1067:  The process terminated unexpectedly".  
> Running 'tahoe' from the command line fails with an ImportError.  It can't 
> find the 'resource' module.
> 
The build in that directory is of unknown quality. I've now removed it 
and replaced it with the production build.

Ps

> 	Shawn.
> _______________________________________________
> tahoe-dev mailing list
> tahoe-dev at allmydata.org
> http://allmydata.org/cgi-bin/mailman/listinfo/tahoe-dev