[tor-bugs] #19969 [Core Tor/Tor]: tor client does not immediately open new circuits after standby

Tor Bug Tracker & Wiki blackhole at torproject.org
Sun Nov 13 01:02:18 UTC 2016


#19969: tor client does not immediately open new circuits after standby
-------------------------------------------------+-------------------------
 Reporter:  weasel                               |          Owner:
     Type:  defect                               |         Status:
                                                 |  reopened
 Priority:  High                                 |      Milestone:  Tor:
                                                 |  0.2.8.x-final
Component:  Core Tor/Tor                         |        Version:  Tor:
                                                 |  0.2.8.6
 Severity:  Normal                               |     Resolution:
 Keywords:  regression 029-backport              |  Actual Points:
  028-backport                                   |
Parent ID:                                       |         Points:  2
 Reviewer:                                       |        Sponsor:
-------------------------------------------------+-------------------------

Comment (by viktorj):

 Replying to [comment:45 arma]:
 > In particular, does Tor 0.2.7.6 behave better in the case where your Tor
 client is asleep for only an hour? It's possible that this edge case was
 never handled well (and so isn't a regression).

 Tor 0.2.7.6 behaves much better in the sense that I never ran into the
 timeout in Thunderbird, although it usually takes a bit to connect to the
 mail servers. Here is a log from August when I compared different versions
 of Tor:

 {{{
 Aug 23 12:19:28.000 [notice] Your system clock just jumped 3622 seconds
 forward; assuming established circuits no longer work.
 Aug 23 12:19:42.000 [notice] Tor has successfully opened a circuit. Looks
 like client functionality is working.
 Aug 23 12:19:42.000 [notice] Tor has successfully opened a circuit. Looks
 like client functionality is working.
 }}}

 During the last days I always opened Thunderbird immediately after leaving
 standby and tried to connect to different mail servers, and strangely I
 didn't run into the Thunderbird timeout sometimes. Here are two examples
 of that with the shortest and the longest time of standby mode:

 {{{
 Nov 12 17:35:29.000 [notice] Your system clock just jumped 2533 seconds
 forward; assuming established circuits no longer work.
 Nov 12 17:37:35.000 [notice] No circuits are opened. Relaxed timeout for
 circuit 85 (a General-purpose client 3-hop circuit in state doing
 handshakes with channel state open) to 125338ms. However, it appears the
 circuit has timed out anyway. 13 guards are live. [2 similar message(s)
 suppressed in last 3600 seconds]
 Nov 12 17:37:37.000 [notice] Tor has successfully opened a circuit. Looks
 like client functionality is working.
 Nov 12 17:37:37.000 [notice] Tor has successfully opened a circuit. Looks
 like client functionality is working.

 Nov 11 18:11:32.000 [notice] Your system clock just jumped 26150 seconds
 forward; assuming established circuits no longer work.
 Nov 11 18:12:20.000 [notice] Tor has successfully opened a circuit. Looks
 like client functionality is working.
 Nov 11 18:12:20.000 [notice] Tor has successfully opened a circuit. Looks
 like client functionality is working.
 }}}

 But I got the timeout with shorter times of standby and with times in
 between the two above. If you are interested in more logs, I can give them
 to you.

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


More information about the tor-bugs mailing list