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

Re: [tor-bugs] #28962 [Core Tor/Tor]: circuits are not both ready. Stalling conn.

To: undisclosed-recipients: ;
Subject: Re: [tor-bugs] #28962 [Core Tor/Tor]: circuits are not both ready. Stalling conn.
From: "Tor Bug Tracker & Wiki" <blackhole@xxxxxxxxxxxxxx>
Date: Sun, 30 Dec 2018 20:06:46 -0000
Auto-submitted: auto-generated
Delivered-to: archiver@xxxxxxxx
Delivery-date: Wed, 02 Jan 2019 22:10:46 -0500
In-reply-to: <051.c08bae8e55f93eac4968a887508b7ad5@torproject.org>
List-archive: <http://lists.torproject.org/pipermail/tor-bugs/>
List-help: <mailto:tor-bugs-request@lists.torproject.org?subject=help>
List-id: "auto: Tor bug tracker status mails" <tor-bugs.lists.torproject.org>
List-post: <mailto:tor-bugs@lists.torproject.org>
List-subscribe: <https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs>, <mailto:tor-bugs-request@lists.torproject.org?subject=subscribe>
List-unsubscribe: <https://lists.torproject.org/cgi-bin/mailman/options/tor-bugs>, <mailto:tor-bugs-request@lists.torproject.org?subject=unsubscribe>
References: <051.c08bae8e55f93eac4968a887508b7ad5@torproject.org>
Reply-to: no-reply@xxxxxxxxxxxxxx, tor-assistants@xxxxxxxxxxxxxx
Sender: "tor-bugs" <tor-bugs-bounces@xxxxxxxxxxxxxxxxxxxx>

#28962: circuits are not both ready. Stalling conn.
--------------------------+----------------------------------
 Reporter:  traumschule   |          Owner:  (none)
     Type:  defect        |         Status:  new
 Priority:  Medium        |      Milestone:  Tor: unspecified
Component:  Core Tor/Tor  |        Version:
 Severity:  Normal        |     Resolution:
 Keywords:                |  Actual Points:
Parent ID:                |         Points:
 Reviewer:                |        Sponsor:
--------------------------+----------------------------------

Comment (by traumschule):

 Above info log also shows {{{Network is unreachable}}} a lot as proof for
 using a poor wireless connection. On the same computer Tor Browser with
 Tor 0.3.5.5-alpha using obfs4 shows more tolerance to connection issues.

 Comparing notice logs of both they share
 > Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up.
 (waiting for circuit)
 while system tor also has the {{{waiting for rendezvous desc}}} variant
 and TB‘s tor instead quite often shows:
 > [WARN] Proxy Client: unable to connect to $address ("general SOCKS
 server failure")

 Is it possible that
 [http://jqs44zhtxl2uo6gk.onion/tor.git/log/?qt=range&q=master+release-0.3.5
 latest code changes] (0.3.5.5-alpha vs 0.4.0-alpha) made tor less robust
 or are PT connections better in handling dropped packets?

 == system tor
 {{{
 Dec 30 07:02:12.000 [notice] Tor 0.4.0.0-alpha-dev opening new log file.
 Dec 30 07:04:03.000 [warn] Failed to find node for hop #1 of our path.
 Discarding this circuit.
 Dec 30 07:04:03.000 [notice] Our circuit 0 (id: 1257) died due to an
 invalid selected path, purpose General-purpose client. This may be a torrc
 configuration issue, or a bug.
 Dec 30 07:05:40.000 [notice] Tried for 120 seconds to get a connection to
 [scrubbed]:22. Giving up. (waiting for circuit)
 Dec 30 07:08:49.000 [warn] Failed to find node for hop #1 of our path.
 Discarding this circuit.
 Dec 30 07:11:40.000 [notice] Tried for 120 seconds to get a connection to
 [scrubbed]:42. Giving up. (waiting for circuit)
 Dec 30 07:13:02.000 [warn] Failed to find node for hop #1 of our path.
 Discarding this circuit.
 Dec 30 07:14:21.000 [notice] Heartbeat: Tor's uptime is 17:59 hours, with
 2 circuits open. I've sent 15.65 MB and received 177.38 MB.
 Dec 30 07:14:21.000 [notice] Average packaged cell fullness: 16.099%. TLS
 write overhead: 5%
 Dec 30 07:15:48.000 [notice] Tried for 120 seconds to get a connection to
 [scrubbed]:22. Giving up. (waiting for circuit)
 Dec 30 07:17:29.000 [notice] Tried for 120 seconds to get a connection to
 [scrubbed]:993. Giving up. (waiting for rendezvous desc)
 Dec 30 07:17:36.000 [warn] Failed to find node for hop #1 of our path.
 Discarding this circuit.
 Dec 30 07:19:30.000 [notice] Tried for 120 seconds to get a connection to
 [scrubbed]:993. Giving up. (waiting for rendezvous desc)
 Dec 30 07:21:45.000 [warn] Failed to find node for hop #1 of our path.
 Discarding this circuit.
 Dec 30 07:21:48.000 [notice] Tried for 120 seconds to get a connection to
 [scrubbed]:42. Giving up. (waiting for circuit)
 Dec 30 07:25:54.000 [warn] Failed to find node for hop #1 of our path.
 Discarding this circuit.
 Dec 30 07:25:55.000 [notice] Tried for 120 seconds to get a connection to
 [scrubbed]:22. Giving up. (waiting for circuit)
 Dec 30 07:26:31.000 [notice] Tried for 120 seconds to get a connection to
 [scrubbed]:993. Giving up. (waiting for rendezvous desc)
 Dec 30 07:28:31.000 [notice] Tried for 120 seconds to get a connection to
 [scrubbed]:993. Giving up. (waiting for rendezvous desc)
 Dec 30 07:30:33.000 [warn] Failed to find node for hop #1 of our path.
 Discarding this circuit.
 Dec 30 07:31:55.000 [notice] Tried for 120 seconds to get a connection to
 [scrubbed]:42. Giving up. (waiting for circuit)
 Dec 30 07:34:41.000 [warn] Failed to find node for hop #1 of our path.
 Discarding this circuit.
 Dec 30 07:35:31.000 [notice] Tried for 120 seconds to get a connection to
 [scrubbed]:993. Giving up. (waiting for rendezvous desc)
 Dec 30 07:36:02.000 [notice] Tried for 120 seconds to get a connection to
 [scrubbed]:22. Giving up. (waiting for circuit)
 Dec 30 07:37:31.000 [notice] Tried for 120 seconds to get a connection to
 [scrubbed]:993. Giving up. (waiting for rendezvous desc)
 Dec 30 07:39:49.000 [warn] Failed to find node for hop #1 of our path.
 Discarding this circuit.
 Dec 30 07:42:02.000 [notice] Tried for 120 seconds to get a connection to
 [scrubbed]:42. Giving up. (waiting for circuit)
 Dec 30 07:44:00.000 [warn] Failed to find node for hop #1 of our path.
 Discarding this circuit.
 Dec 30 07:44:32.000 [notice] Tried for 120 seconds to get a connection to
 [scrubbed]:993. Giving up. (waiting for rendezvous desc)
 Dec 30 07:50:46.000 [notice] Your system clock just jumped 288 seconds
 forward; assuming established circuits no longer work.
 Dec 30 07:50:46.000 [notice] Tried for 397 seconds to get a connection to
 [scrubbed]:22. Giving up. (waiting for circuit)
 Dec 30 07:50:46.000 [notice] Tried for 374 seconds to get a connection to
 [scrubbed]:993. Giving up. (waiting for rendezvous desc)
 Dec 30 09:32:02.000 [notice] We tried for 15 seconds to connect to
 '[scrubbed]' using exit $relay at $address. Retrying on a new circuit.
 Dec 30 10:28:24.000 [notice] We tried for 15 seconds to connect to
 '[scrubbed]' using exit $relay at $address. Retrying on a new circuit.
 Dec 30 10:29:49.000 [notice] Tried for 120 seconds to get a connection to
 [scrubbed]:22. Giving up. (waiting for circuit)
 Dec 30 10:30:19.000 [notice] Tried for 120 seconds to get a connection to
 [scrubbed]:80. Giving up. (waiting for circuit)
 Dec 30 10:30:24.000 [notice] Tried for 120 seconds to get a connection to
 [scrubbed]:80. Giving up. (waiting for circuit)
 Dec 30 10:30:29.000 [notice] Tried for 120 seconds to get a connection to
 [scrubbed]:80. Giving up. (waiting for circuit)
 Dec 30 10:30:39.000 [notice] Tried for 120 seconds to get a connection to
 [scrubbed]:80. Giving up. (waiting for circuit)
 Dec 30 10:37:59.000 [notice] Tried for 120 seconds to get a connection to
 [scrubbed]:80. Giving up. (waiting for circuit)
 Dec 30 10:38:05.000 [notice] Rend stream is 120 seconds late. Giving up on
 address '[scrubbed].onion'.
 Dec 30 10:38:19.000 [notice] Tried for 120 seconds to get a connection to
 [scrubbed]:80. Giving up. (waiting for circuit)
 Dec 30 10:49:33.000 [notice] Tried for 120 seconds to get a connection to
 [scrubbed]:80. Giving up. (waiting for circuit)
 Dec 30 11:10:19.000 [notice] Tried for 120 seconds to get a connection to
 [scrubbed]:80. Giving up. (waiting for circuit)
 }}}

 == tor browser
 {{{
 12/30/18, 12:37:31.860 [NOTICE] Application request when we haven't
 received a consensus with exits. Optimistically trying known bridges
 again.
 12/30/18, 12:37:31.860 [WARN] Proxy Client: unable to connect to
 $address:13764 ("$relay)
 12/30/18, 12:37:32.198 [WARN] Proxy Client: unable to connect to
 $address:10527 ("$relay)
 12/30/18, 12:37:32.198 [WARN] Proxy Client: unable to connect to
 $address:443 ("$relay)
 12/30/18, 12:37:32.638 [NOTICE] Delaying directory fetches: No running
 bridges
 12/30/18, 12:38:02.637 [NOTICE] Tried for 120 seconds to get a connection
 to [scrubbed]:22. Giving up. (waiting for circuit)
 12/30/18, 12:38:02.742 [NOTICE] Application request when we haven't
 received a consensus with exits. Optimistically trying known bridges
 again.
 12/30/18, 12:38:02.751 [WARN] Proxy Client: unable to connect to
 $address:13764 ("$relay)
 12/30/18, 12:38:03.852 [WARN] Proxy Client: unable to connect to
 $address:10527 ("$relay)
 12/30/18, 12:38:04.850 [WARN] Proxy Client: unable to connect to
 $address:443 ("$relay)
 12/30/18, 12:38:05.638 [NOTICE] Delaying directory fetches: No running
 bridges
 12/30/18, 12:39:31.637 [NOTICE] Tried for 120 seconds to get a connection
 to [scrubbed]:993. Giving up. (waiting for circuit)
 12/30/18, 12:40:02.636 [NOTICE] Tried for 120 seconds to get a connection
 to [scrubbed]:22. Giving up. (waiting for circuit)
 12/30/18, 12:42:02.345 [NOTICE] Application request when we haven't
 received a consensus with exits. Optimistically trying known bridges
 again.
 12/30/18, 12:42:02.775 [WARN] Proxy Client: unable to connect to
 $address:13764 ("$relay)
 12/30/18, 12:42:03.358 [WARN] Proxy Client: unable to connect to
 $address:10527 ("$relay)
 12/30/18, 12:42:03.358 [WARN] Proxy Client: unable to connect to
 $address:443 ("$relay)
 12/30/18, 12:42:03.637 [NOTICE] Delaying directory fetches: No running
 bridges
 12/30/18, 12:44:02.644 [NOTICE] Tried for 120 seconds to get a connection
 to [scrubbed]:42. Giving up. (waiting for circuit)
 12/30/18, 12:50:46.689 [NOTICE] Your system clock just jumped 289 seconds
 forward; assuming established circuits no longer work.
 12/30/18, 12:50:46.842 [NOTICE] Application request when we haven't
 received a consensus with exits. Optimistically trying known bridges
 again.
 12/30/18, 12:50:47.116 [WARN] Proxy Client: unable to connect to
 $address:13764 ("$relay)
 12/30/18, 12:50:47.849 [WARN] Proxy Client: unable to connect to
 $address:443 ("$relay)
 12/30/18, 12:50:47.849 [WARN] Proxy Client: unable to connect to
 $address:10527 ("$relay)
 12/30/18, 12:50:48.636 [NOTICE] Delaying directory fetches: No running
 bridges
 12/30/18, 12:52:46.632 [NOTICE] Tried for 120 seconds to get a connection
 to [scrubbed]:22. Giving up. (waiting for circuit)
 12/30/18, 12:52:46.726 [NOTICE] Application request when we haven't
 received a consensus with exits. Optimistically trying known bridges
 again.
 12/30/18, 12:52:47.728 [NOTICE] Tried for 120 seconds to get a connection
 to [scrubbed]:993. Giving up. (waiting for circuit)
 12/30/18, 13:01:36.187 [NOTICE] We tried for 15 seconds to connect to
 '[scrubbed]' using exit $relay at $address Retrying on a new circuit.
 12/30/18, 13:04:45.187 [NOTICE] Delaying directory fetches: No running
 bridges
 12/30/18, 13:05:13.455 [NOTICE] Application request when we haven't
 received a consensus with exits. Optimistically trying known bridges
 again.
 12/30/18, 14:43:59.659 [NOTICE] Have tried resolving or connecting to
 address '[scrubbed]' at 3 different places. Giving up.
 12/30/18, 14:58:54.968 [NOTICE] Have tried resolving or connecting to
 address '[scrubbed]' at 3 different places. Giving up.
 12/30/18, 14:59:12.218 [NOTICE] Have tried resolving or connecting to
 address '[scrubbed]' at 3 different places. Giving up.
 12/30/18, 14:59:26.990 [WARN] Your application (using socks5 to port 42)
 gave Tor a malformed hostname: [scrubbed]. Rejecting the connection.
 12/30/18, 15:01:49.203 [NOTICE] We tried for 15 seconds to connect to
 '[scrubbed]' using exit $relay at $address Retrying on a new circuit.
 12/30/18, 15:02:04.276 [NOTICE] We tried for 15 seconds to connect to
 '[scrubbed]' using exit $relay at $address Retrying on a new circuit.
 12/30/18, 15:02:19.256 [NOTICE] We tried for 15 seconds to connect to
 '[scrubbed]' using exit $relay at $address Retrying on a new circuit.
 12/30/18, 15:02:36.288 [WARN] Your application (using socks5 to port 42)
 gave Tor a malformed hostname: [scrubbed]. Rejecting the connection.
 12/30/18, 15:02:40.167 [WARN] Your application (using socks5 to port 42)
 gave Tor a malformed hostname: [scrubbed]. Rejecting the connection.
 12/30/18, 15:07:27.238 [NOTICE] new bridge descriptor 'frosty' (fresh):
 $relay at $address
 12/30/18, 15:20:32.719 [WARN] Proxy Client: unable to connect to
 $address:443 ("$relay)
 12/30/18, 15:27:10.202 [NOTICE] Heartbeat: Tor's uptime is 4 days 6:01
 hours, with 5 circuits open.
 12/30/18, 15:27:10.203 [NOTICE] Average packaged cell fullness: 27.161%.
 TLS write overhead: 5%
 12/30/18, 15:35:28.328 [NOTICE] We tried for 15 seconds to connect to
 '[scrubbed]' using exit $relay at $address Retrying on a new circuit.
 12/30/18, 15:35:54.328 [NOTICE] Tor has not observed any network activity
 for the past 92 seconds. Disabling circuit build timeout recording.
 12/30/18, 15:35:55.562 [NOTICE] Tor now sees network activity. Restoring
 circuit build timeout recording. Network was down for 93 seconds during 1
 circuit attempts.
 12/30/18, 15:39:47.558 [NOTICE] new bridge descriptor 'ndnop3' (fresh):
 $relay at $address
 12/30/18, 15:47:26.543 [WARN] Proxy Client: unable to connect to
 $address:80 ("$relay)
 }}}

 (timestamps differ by 5 hours)

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

References:
- Re: [tor-bugs] #28962 [Core Tor/Tor]: circuits are not both ready. Stalling conn.
  - From: Tor Bug Tracker & Wiki

Prev by Author: Re: [tor-bugs] #28020 [Core Tor/Tor]: Run another memory profile in late 0.4.0 to figure out how much memory we saved.
Next by Author: Re: [tor-bugs] #26698 [Core Tor/Tor]: Authorities should put a hash of the bandwidth file in their votes
Next by thread: Re: [tor-bugs] #28823 [Applications/Tor Browser]: Every web page crashes on Windows 7 with Tor Browser 8
Index(es):
- Author
- Thread