On 12/14/12 11:51 PM, Iantcho Vassilev wrote:
I installed tahoe and run it as a client for a private grid but here
what twistd.log says:
location_hints = decode_location_hints(hints)
File
"/home/tahoe/allmydata-tahoe-1.9.2/support/lib/python2.6/site-packages/foolscap-0.6.4-py2.6.egg/foolscap/referenceable.py",
line 787, in decode_location_hints
"(hostname, but no port)" % hint_s)
foolscap.referenceable.BadFURLError: bad connection hint
'5.39.92.231' (hostname, but no port)
2012-12-15 08:47:55+0100 [-] Node._startService failed, aborting
2012-12-15 08:47:55+0100 [-] [Failure instance: Traceback: <class
'foolscap.referenceable.BadFURLError'>: bad connection hint
'5.39.92.231' (hostname, but no port)
Huh, that's weird. You're right, it's complaining that the connection
hint is malformed. "tub.location" is supposed to be a comma-separated
list of HOST:PORT pairs, where HOST is specifically allowed to be either
a DNS name or an ipv4 address.
Basically it says that there is no port configure but here is the conf:
tub.port = 56777
tub.location = 5.39.92.231:56777
That seems ok to me. The error suggests that it thought
tub.location="5.39.92.231" instead of tub.location="5.39.92.231:56777".
Is it possible that you hadn't yet saved tahoe.cfg when you restarted
the node? You might also double-check that there is only one copy of
tub.location in your config file (maybe it's getting overridden by a
stray duplicate).
"tahoe --version" reports tahoe-1.9.2 and foolscap-0.6.4, right? I tried
a similar tub.location on my system (but running tahoe trunk instead of
1.9.2) and didn't get an error. If we can rule out a tahoe.cfg problem,
I'll get a 1.9.2 checkout from darcs and try to reproduce it again.
thanks,
-Brian
_______________________________________________
tahoe-dev mailing list
[email protected]
https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev
