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

Re: [tor-bugs] #26823 [Core Tor/Tor]: TOR doesn't work at all on slow connections. TOR is fully broken



#26823: TOR doesn't work at all on slow connections. TOR is fully broken
-------------------------------------------------+-------------------------
 Reporter:  white_supremacy_pedo                 |          Owner:  (none)
     Type:  defect                               |         Status:  new
 Priority:  Immediate                            |      Milestone:
Component:  Core Tor/Tor                         |        Version:  Tor:
                                                 |  unspecified
 Severity:  Blocker                              |     Resolution:
 Keywords:  slow connection, pedo, cp, tor,      |  Actual Points:
  broken                                         |
Parent ID:                                       |         Points:
 Reviewer:  pastly                               |        Sponsor:
                                                 |  SponsorR
-------------------------------------------------+-------------------------

Comment (by white_supremacy_pedo):

 When the bug happens TOR log is spammed with lines like this:
 [NOTICE] Rend stream is 120 seconds late. Giving up on address
 '[scrubbed].onion'.
 [NOTICE] Tried for 120 seconds to get a connection to [scrubbed]:80.
 Giving up.
 [NOTICE] Tried for 120 seconds to get a connection to [scrubbed]:443.
 Giving up. (waiting for circuit)
 [NOTICE] Tried for 120 seconds to get a connection to [scrubbed]:80.
 Giving up. (waiting for circuit)

 occasionally I get other lines like (not in order, just examples):
 [NOTICE] Have tried resolving or connecting to address '[scrubbed]' at 3
 different places. Giving up.
 [NOTICE] We tried for XX seconds to connect to '[scrubbed]' using exit XXX
 at XXX. Retrying on a new circuit.
 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.
 [NOTICE] Our IP address has changed.  Rotating keys...
 [NOTICE] No circuits are opened. Relaxed timeout for circuit XXX (a
 Measuring circuit timeout 3-hop circuit in state doing handshakes with
 channel state open) to XXXXms. However, it appears the circuit has timed
 out anyway.
 [NOTICE] Tor has not observed any network activity for the past XX
 seconds. Disabling circuit build timeout recording.
 [NOTICE] Your Guard XXX is failing more circuits than usual. Most likely
 this means the Tor network is overloaded. Success counts are XXX/XXX. Use
 counts are XX/XX. XXX circuits completed, XX were unusable, XX collapsed,
 and XX timed out. For reference, your timeout cutoff is XX seconds.
 [NOTICE] Your Guard XXX is failing to carry more streams on its circuits
 than usual. Most likely this means the Tor network is overloaded or your
 network connection is poor. Use counts are XX/XX. Success counts are
 XXX/XXX. XXX circuits completed, XX were unusable, XX collapsed, and XX
 timed out. For reference, your timeout cutoff is XX seconds.

 XXX - removed

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