[tahoe-lafs-trac-stream] [tahoe-lafs] #974: provide user-friendly error message if the CLI can't connect to the gateway

tahoe-lafs trac at tahoe-lafs.org
Sat May 14 15:41:16 PDT 2011


#974: provide user-friendly error message if the CLI can't connect to the gateway
----------------------------+----------------------------------------------
     Reporter:  zooko       |      Owner:  guyzmo
         Type:  defect      |     Status:  new
     Priority:  major       |  Milestone:  1.9.0
    Component:  code-       |    Version:  1.6.0
  frontend-cli              |   Keywords:  usability easy error test-needed
   Resolution:              |
Launchpad Bug:              |
----------------------------+----------------------------------------------

Comment (by davidsarah):

 More IRC discussion of a problem where this ticket would have helped:

 > <secorp> so if you do something like "tahoe ls -d directory/ --dir-
 cap=<dircap>"

 > <secorp> That gives the socket error?

 > <bj0> yup

 > <secorp> What does the "node.url" file look like on the node that
 doesn't work?

 > <secorp> Meaning, is it something like:

 > <secorp> http://127.0.0.1:9001 ?

 > <bj0> it's throwing it at: resp = do_http("GET", url)
 ...
 > <secorp> Does the exception print out the url it is trying to use in the
 do_http call?
 ...
 > <bj0> no it doesn't

 > <bj0> would that be in a log somewhere?

 > <secorp> I'm not sure, it might be in the <directory>/logs/twistd.log
 file

 > <bj0> na it just something like 'port opened' 'port closed'
 ...
 > <zooko> Did you ever figure out your problem with a port not being open?

 > <bj0> no, can't figure out whats wrong

 > <bj0> the weird part is it's only the cli  that has the problem

 > <bj0> i can browse the files with the webui

 > <zooko> Sounds like it is the connection from the tahoe cli to the wapi
 that is failing, right?

 > <bj0> the GET request fails

 > <zooko> So I guess the HTTP GET request is not aimed at the right
 host+port pair.

 > <bj0> secorp was out of ideas and i got nothing :/

 > <zooko> Should be the same host+port that your web browser is hitting.

 > <bj0> yea, it doesn't print out what url it's trying to connect to

 > <bj0> i wonder

 > <bj0> node.url has 127.0.0.1 as the ip, but in .cfg i changed the ip to
 eth0's ip, would that break it?

 > <zooko> #974

 > <zooko> Yes I think that would prevent connections to the wapi/wui over
 localhost. IIUC

 > <bj0> i'll try changing it back

 > <bj0> if i drop 'interface=' it should bind to 0.0.0.0 right?

 > <bj0> hah that fixed it

-- 
Ticket URL: <http://tahoe-lafs.org/trac/tahoe-lafs/ticket/974#comment:10>
tahoe-lafs <http://tahoe-lafs.org>
secure decentralized storage


More information about the tahoe-lafs-trac-stream mailing list