[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: [tor-bugs] #27066 [Core Tor/Tor]: circuit_build_times_update_alpha(): Bug: Could not determine largest build time

#27066: circuit_build_times_update_alpha(): Bug: Could not determine largest build
time
---------------------------------------+-----------------------------------
 Reporter:  cstest                     |          Owner:  (none)
     Type:  defect                     |         Status:  new
 Priority:  Medium                     |      Milestone:  Tor:
                                       |  0.3.5.x-final
Component:  Core Tor/Tor               |        Version:  Tor: 0.3.3.9
 Severity:  Normal                     |     Resolution:
 Keywords:  034-backport 033-backport  |  Actual Points:
Parent ID:                             |         Points:
 Reviewer:                             |        Sponsor:
---------------------------------------+-----------------------------------

Comment (by cstest):

 There were aprox. 4000 lines of "No valid circuit build time data out of
 1000 times, 3 modes".

 Every couple of mins script was sending hup signal to tor and in log file
 there are just 3 lines repeating:
 {{{
 Received reload signal (hup). Reloading config and resetting internal
 state.
 Read configuration file ...........
 Tor 0.3.3.9 (git-ca1a436fa8e53a32) opening log file.
 }}}

 And sometime this appears in random order:
 {{{
 Your network connection speed appears to have changed. Resetting timeout
 to 60s after 18 timeouts and 143 buildtimes.
 }}}

 but above line could be related to single v2 hidden service running. Then
 almost 5 hours later new lines began to appear (hundreds probably due to
 large number of v3 domains in torrc):
 {{{
 Failed to launch rendezvous circuit to
 $835BDF974D1B6A324C15C48A95D49605AAAB51C1~ at ....
 Giving up on launching a rendezvous circuit to
 $D405FCCF06ADEDF898DF2F29C9348DCB623031BA~ at 5.45.111.149 for hidden
 service v3onion....................
 Giving up launching first hop of circuit to rendezvous point
 $A379AD9020BB119B53785888DACC63C7...........
 }}}

 and occasionaly
 {{{
 Extremely large value for circuit build timeout: 123s. Assuming clock
 jump. Purpose 14 (Measuring circuit timeout)
 Couldn't relaunch rendezvous circuit to
 '$0299F268FCA9D55CD157976D39AE92B4B.........
 }}}


 Single active v2 domain was working fine but not a single one v3. After
 reloading tor, v3 domains started to work fine (nothing else have been
 changed).

 Have not found any "No circuits are opened" lines. At start, v3 domains
 worked fine for several hours.

 {{{
 Aug 07 00:02:15.000 [notice] Our hidden services received 41808 v2 and 18
 v3 INTRODUCE2 cells and attempted to launch 42259 rendezvous circuits.
 ........
 Aug 07 06:02:15.000 [notice] Our hidden services received 42361 v2 and
 1813 v3 INTRODUCE2 cells and attempted to launch 45315 rendezvous
 circuits.
 ........
 Aug 07 12:02:15.000 [notice] Our hidden services received 42549 v2 and
 4072 v3 INTRODUCE2 cells and attempted to launch 48084 rendezvous
 circuits.
 ........
 Aug 07 18:02:16.000 [notice] Our hidden services received 43651 v2 and
 13413 v3 INTRODUCE2 cells and attempted to launch 60870 rendezvous
 circuits.
 }}}

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

_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs