#649: Validation of configuration settings
----------------------------+-----------------------------------------------
Reporter: ndurner | Owner:
Type: enhancement | Status: new
Priority: minor | Milestone: undecided
Component: code-nodeadmin | Version: 1.3.0
Keywords: | Launchpad_bug:
----------------------------+-----------------------------------------------
Comment(by zooko):
Heh, I just hit this exact same problem. I cut and pasted the introducer
furl from the web archive of the mailing list and started tahoe. It said
"probably started". But it fails to connect to the introducer.
Investigation led me to the {{{logs/incidents}}} directory which had an
incident report .bz2. Running {{{flogtool dump}}} on that bz2 file
yielded a log which included:
{{{
File "/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5
/site-packages/foolscap-0.3.2-py2.5.egg/foolscap/referenceable.py", line
825, in _init_from_url
raise ValueError("unknown FURL prefix in %r" % (url,))
exceptions.ValueError: unknown FURL prefix in
'pb://6cypm5tfsv6ag43g3j5z74qx5nfxa2qq at
207.7.131.41:64228,nooxie.zooko.com:64228/introducer'
}}}
--
Ticket URL: <http://allmydata.org/trac/tahoe/ticket/649#comment:2>
tahoe-lafs <http://allmydata.org>
secure decentralized file storage grid
_______________________________________________
tahoe-dev mailing list
[email protected]
http://allmydata.org/cgi-bin/mailman/listinfo/tahoe-dev
