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

["Tor Bug Tracker & Wiki" <blackhole@xxxxxxxxxxxxxx>]

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

Comment (by viktorj):

 Unfortunately the bug is not fixed for me in 0.2.9.5-alpha. Here is the
 log after my PC woke up from standby:

 Nov 09 13:58:52.000 [notice] Your system clock just jumped 3622 seconds
 forward; assuming established circuits no longer work.
 Nov 09 14:01:09.000 [notice] Tried for 120 seconds to get a connection to
 [scrubbed]:993. Giving up. (waiting for circuit)
 Nov 09 14:01:59.000 [notice] Tried for 120 seconds to get a connection to
 [scrubbed]:993. Giving up. (waiting for circuit)
 Nov 09 14:03:43.000 [notice] Tried for 120 seconds to get a connection to
 [scrubbed]:993. Giving up. (waiting for circuit)
 Nov 09 14:04:18.000 [notice] Tried for 120 seconds to get a connection to
 [scrubbed]:995. Giving up. (waiting for circuit)
 Nov 09 14:04:58.000 [notice] No circuits are opened. Relaxed timeout for
 circuit 21 (a General-purpose client 3-hop circuit in state doing
 handshakes with channel state open) to 348450ms. However, it appears the
 circuit has timed out anyway. 14 guards are live.
 Nov 09 14:04:59.000 [notice] Tor has not observed any network activity for
 the past 4200 seconds. Disabling circuit build timeout recording.
 Nov 09 14:05:57.000 [notice] Tor now sees network activity. Restoring
 circuit build timeout recording. Network was down for 4258 seconds during
 2 circuit attempts.
 Nov 09 14:06:01.000 [notice] Tried for 120 seconds to get a connection to
 [scrubbed]:993. Giving up. (waiting for circuit)
 Nov 09 14:08:10.000 [notice] Tried for 120 seconds to get a connection to
 [scrubbed]:993. Giving up. (waiting for circuit)
 Nov 09 14:09:27.000 [notice] Tried for 120 seconds to get a connection to
 [scrubbed]:993. Giving up. (waiting for circuit)
 Nov 09 14:10:33.000 [notice] Tried for 120 seconds to get a connection to
 [scrubbed]:993. Giving up. (waiting for circuit)
 Nov 09 14:10:47.000 [notice] Tor has successfully opened a circuit. Looks
 like client functionality is working.
 Nov 09 14:10:47.000 [notice] Tor has successfully opened a circuit. Looks
 like client functionality is working.

 During these connection attempts to my mail providers, I could use the Tor
 Browser for surfing, which in my case directly connects to the Tor network
 (no bridges or something else), so there should not be a network
 connectivity problem here.

 Since the bug is of course annoying for me, tell me if I can give you
 further information or if I can help you in any other way.

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/19969#comment:41>
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