[tor-bugs] #17147 [Tor]: long-running client path-selection not seeing some (fast) exit nodes

[Tor Bug Tracker & Wiki]

#17147: long-running client path-selection not seeing some (fast) exit nodes
---------------------------+-------------------------------
     Reporter:  starlight  |      Owner:
         Type:  defect     |     Status:  needs_information
     Priority:  normal     |  Milestone:  Tor: 0.2.???
    Component:  Tor        |    Version:  Tor: 0.2.6.10
   Resolution:             |   Keywords:
Actual Points:             |  Parent ID:
       Points:             |    Sponsor:
---------------------------+-------------------------------

Comment (by starlight):

 Looked through the second trace and it does not say
 much of interest except
 {{{
 [debug] circuit_remove_handled_ports(): Port 110 is not handled.
 [info] circuit_predict_and_launch_new(): Have 0 clean circs (0 internal),
 need another exit circ.
 [debug] new_route_len(): Chosen route length 3 (6588/7334 routers
 suitable).
 [info] choose_good_exit_server_general(): Found 0 servers that might
 support 0/0 pending connections.
 [info] choose_good_exit_server_general(): We couldn't find any live, fast
 routers; falling back to list of all routers.
 [info] choose_good_exit_server_general(): Found 0 servers that might
 support 0/0 pending connections.
 [notice] All routers are down or won't exit -- choosing a doomed exit at
 random.
 [debug] circuit_remove_handled_ports(): Port 110 is not handled.
 [info] compute_weighted_bandwidths(): Empty routerlist passed in to
 consensus weight node selection for rule weight as exit
 [info] compute_weighted_bandwidths(): Empty routerlist passed in to
 consensus weight node selection for rule weight as exit
 [warn] No specified exit routers seem to be running: can't choose an exit.
 [warn] Failed to choose an exit server
 }}}

 Spent a few minutes looking at the code and it seems
 that ascii exit policies are converted into a binary
 format for use by the path selection logic.

 So--just guessing--perhaps the binary version
 of an exit policy is not updated when the ascii form
 changes in the published consensus and/or descriptor?

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