[tor-bugs] #6341 [Tor Relay]: connection_or_flush_from_first_active_circuit() does wrong thing when ewma_enabled

[Tor Bug Tracker & Wiki]

#6341: connection_or_flush_from_first_active_circuit() does wrong thing when
ewma_enabled
-----------------------+----------------------------------------------------
 Reporter:  arma       |          Owner:                    
     Type:  defect     |         Status:  needs_review      
 Priority:  normal     |      Milestone:  Tor: 0.2.3.x-final
Component:  Tor Relay  |        Version:                    
 Keywords:             |         Parent:                    
   Points:             |   Actualpoints:                    
-----------------------+----------------------------------------------------

Comment(by robgjansen):

 Replying to [comment:54 arma]:

 > You still have a few percent of relays who don't bootstrap for a while.
 Another smaller bug, or what?

 After checking through some log files, there doesn't seem to be any trend
 for the relays who take a while to bootstrap (e.g., its not mostly from
 relays with high link latency, or from slow relays). Sadly, I think there
 might be another smaller bug somewhere.

 > I wonder what the one socks failure was. :) I guess it could have simply
 been a normal 120 second timeout.

 It was a timeout, but the notice level logs don't give me enough
 information to tell which relay in the circuit was to blame.

 {{{
 [tor-notice] connection_ap_expire_beginning() We tried for 15 seconds to
 connect to '70.1.0.0' using exit
 $A011BB1F2B1359E989ACF13C1DEB8768C6919734~exit20 at 140.1.0.0. Retrying on
 a new circuit.
 [tor-notice] connection_ap_expire_beginning() We tried for 15 seconds to
 connect to '70.1.0.0' using exit
 $A011BB1F2B1359E989ACF13C1DEB8768C6919734~exit20 at 140.1.0.0. Retrying on
 a new circuit.
 [tor-notice] connection_ap_expire_beginning() We tried for 15 seconds to
 connect to '70.1.0.0' using exit
 $A011BB1F2B1359E989ACF13C1DEB8768C6919734~exit20 at 140.1.0.0. Retrying on
 a new circuit.
 [tor-notice] connection_ap_expire_beginning() We tried for 15 seconds to
 connect to '70.1.0.0' using exit
 $A011BB1F2B1359E989ACF13C1DEB8768C6919734~exit20 at 140.1.0.0. Retrying on
 a new circuit.
 [tor-notice] connection_ap_expire_beginning() Tried for 120 seconds to get
 a connection to 70.1.0.0:80. Giving up. (waiting for circuit)
 }}}

 I checked exit20, but it seemed to be functioning correctly. Looks like
 some additional debugging fun is in order.

 > Does that mean it's time to try the actual #6341 experiment again?

 Not sure, but
 [https://trac.torproject.org/projects/tor/attachment/ticket/6341/20120909-ec2
 -brokenewma-combined.pdf I already did anyway]. Does this provide any more
 answers than
 [https://trac.torproject.org/projects/tor/attachment/ticket/6341/20120813-ec2
 -brokenewma-combined.pdf last set of graphs]?

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