Perhaps there is another configuration line earlier in the file with the
same IP but no port? If you don't mind sharing your tahoe.cfg maybe we
can help find the error.
On 12/15/12 11:13 PM, Iantcho Vassilev wrote:
Yes, it is very weird..
I triple check tahoe.conf, restarted a million times with and without
the port included but the error stays the same.
I put the IP into hosts so i also tried domainname:port
It goes with the same error.
The tahoe version is as you said:
allmydata-tahoe: 1.9.2,
foolscap: 0.6.4,
pycryptopp: 0.6.0.1206569328141510525648634803928199668821045408958,
zfec: 1.4.7,
Twisted: 10.1.0,
Nevow: 0.10.0,
zope.interface: unknown,
python: 2.6.6,
platform: Linux-debian_6.0.6-x86_64-64bit_ELF,
pyOpenSSL: 0.10,
simplejson: 2.1.0rc3,
pycrypto: 2.1.0,
pyasn1: unknown,
mock: 1.0.1,
sqlite3: 2.4.1 [sqlite 3.7.3],
setuptools: 0.6c16dev3
I cannot think of something new to try ...
Iantcho
On Sat, Dec 15, 2012 at 10:40 PM, Brian <[email protected]
<mailto:[email protected]>> wrote:
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 <http://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 <http://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] <mailto:[email protected]>
https://tahoe-lafs.org/cgi-__bin/mailman/listinfo/tahoe-dev
<https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev>
_______________________________________________
tahoe-dev mailing list
[email protected]
https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev
_______________________________________________
tahoe-dev mailing list
[email protected]
https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev
