[tahoe-dev] Troubleshooting node connectivity
Shawn Willden
shawn at willden.org
Wed Sep 9 09:37:31 PDT 2009
On Tuesday 08 September 2009 05:40:56 pm Peter Secor wrote:
> Hi Shawn, I've had a Windows Tahoe node running pretty reliably as a
> service for quite some time. You can download the stable production
> client here:
>
> http://allmydata.com/downloads/Allmydata321Setup.exe
>
> Just edit the introducer and helper to point to your grid and the client
> should work fine.
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.
> 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.
Shawn.
More information about the tahoe-dev
mailing list