[tor-bugs] #15006 [Tor]: Improve error message "Connecting to a relay directory failed (no route to host)."

[Tor Bug Tracker & Wiki]

#15006: Improve error message "Connecting to a relay directory failed (no route to
host)."
--------------------------+--------------------------------
     Reporter:  krichter  |      Owner:  nickm
         Type:  defect    |     Status:  needs_review
     Priority:  normal    |  Milestone:  Tor: 0.2.6.x-final
    Component:  Tor       |    Version:
   Resolution:            |   Keywords:  026-deferrable
Actual Points:            |  Parent ID:
       Points:            |
--------------------------+--------------------------------

Comment (by mcs):

 Replying to [comment:9 atagar]:
 > To get the address/ORPort you can fetch the descriptor ('GETINFO
 desc/id/BD6A829255CB08E66FBE7D3748363586E46B3810' or 'GETINFO
 ns/id/BD6A829255CB08E66FBE7D3748363586E46B3810' should both do the trick
 for this).

 Thanks!  My problem was that I started with a completely clean tor data
 directory.  In that case, GETINFO desc/id/... seems to return:
   552 Unrecognized key "desc/id/$BD6A829255CB08E66FBE7D3748363586E46B3810"
 and GETINFO ns/id/... returns:
   250-ns/id/$BD6A829255CB08E66FBE7D3748363586E46B3810=
   250 OK
 I guess this ID is one of the directory servers and tor does not yet have
 any info to report.  But I admit I do not fully understand everything that
 happens during the Tor bootstrapping process.

 Would you be willing to always include ip:port?  Maybe tor could always
 include HOST="ip:port" but also include HOSTID="..." if it is available.

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/15006#comment:10>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online