[tahoe-dev] commands from the CLI fails [fixed]

Ed Kapitein ed at kapitein.org
Mon Feb 25 21:00:17 UTC 2013


As it turned out, the pi was listening on its normal, internal ip 
address, instead of on localhost,
so i had to use the  --node-url= option.
(the node.url file  in ~/.tahoe seems to be overwritten at every restart)

Sorry for the fuss...

Kind regards,
Ed

On 02/25/2013 12:20 AM, Ed Kapitein wrote:
> Hi all,
>
> I installed tahoe and successfully made a directory in the pubgrid, 
> named TestEd.
> And i did put some files in it, by uploading it with the wui.
>
> But if i try to 'ls' the files in the CLI i get an error:
>
> tahoe ls 
> URI:DIR2:xyixata7yq5lx5w755azwag5ni:jwdanyzc3sph2up6zndyhlvtx4eqv5jgqknhysiwqyqskyp6ozyq
>
> Traceback (most recent call last):
>   File "/usr/bin/tahoe", line 3, in <module>
>     runner.run()
>   File "/usr/lib/python2.7/dist-packages/allmydata/scripts/runner.py", 
> line 113, in run
>     rc = runner(sys.argv[1:], install_node_control=install_node_control)
>   File "/usr/lib/python2.7/dist-packages/allmydata/scripts/runner.py", 
> line 99, in runner
>     rc = cli.dispatch[command](so)
>   File "/usr/lib/python2.7/dist-packages/allmydata/scripts/cli.py", 
> line 522, in list
>     rc = tahoe_ls.list(options)
>   File 
> "/usr/lib/python2.7/dist-packages/allmydata/scripts/tahoe_ls.py", line 
> 31, in list
>     resp = do_http("GET", url)
>   File 
> "/usr/lib/python2.7/dist-packages/allmydata/scripts/common_http.py", 
> line 60, in do_http
>     c.endheaders()
>   File "/usr/lib/python2.7/httplib.py", line 958, in endheaders
>     self._send_output(message_body)
>   File "/usr/lib/python2.7/httplib.py", line 818, in _send_output
>     self.send(msg)
>   File "/usr/lib/python2.7/httplib.py", line 780, in send
>     self.connect()
>   File "/usr/lib/python2.7/httplib.py", line 761, in connect
>     self.timeout, self.source_address)
>   File "/usr/lib/python2.7/socket.py", line 571, in create_connection
>     raise err
> socket.error: [Errno 111] Connection refused
>
> I did a strace on the tahoe process and on closer inspection it seems 
> to try to connect to someones private address 192.168.1.101
> And that fails ofcourse.
>
> Is this a bug, or a configuration error? ( a filter out private 
> addresses setting )
> I did put the strace files in the same directory, they are named
> tahoe.44 
> <http://10.14.6.65:3456/file/URI%3ASSK%3Ajaogojw67ybcakzpnpgctv52la%3Am4o4y7xrit2qguzbkdgdo7kkw4e5vclbqhjm45sdxgjkqir2qd4q/@@named=/tahoe.4452>xx
>
> i am running the latest version on a raspberry pi (arm)
>
> Kind regards,
> Ed
>
> tahoe --version
> allmydata-tahoe: 1.9.2,
> foolscap: 0.6.4,
> pycryptopp: 0.5.29,
> zfec: 1.4.5,
> Twisted: 12.0.0,
> Nevow: 0.10.0,
> zope.interface: unknown,
> python: 2.7.3,
> platform: Linux-debian_7.0-armv6l-32bit_ELF,
> pyOpenSSL: 0.13,
> simplejson: 2.5.2,
> pycrypto: 2.6,
> pyasn1: unknown,
> mock: 0.8.0,
> sqlite3: 2.6.0 [sqlite 3.7.13],
> setuptools: 0.6 [distribute]
>
>
>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://tahoe-lafs.org/pipermail/tahoe-dev/attachments/20130225/cf156c48/attachment.html>


More information about the tahoe-dev mailing list