On 5/16/2012 1:20 PM, Aaron Whiteman wrote:
I can no longer connect to the Tor Network. I used to be able to use it
perfectly well.
I would be very grateful for any help. I've spent several hours trying to deal
with this issue!
My ISP has either irrationally started to block Tor or there is some weird
configuration error. I can use Tor fine on different networks (e.g. at cafes
with wireless networks).
I am using the latest version of the Tor Browser bundle under Ubuntu 10.04.
The logs below should explain what happens. I suspect that the key error is:
[Info] circuit_build_times_set_timeout_worker(): Circuit build timeout of
50800279ms is beyond the maximum build time we have ever observed. Capping it
to 32175ms.
[Info] circuit_build_times_set_timeout_worker(): Circuit build measurement
period of 2147483647ms is more than twice the maximum build time we have ever
observed. Capping it to 64350ms.
This error does not appear when I am on a different network and can connect.
How can I resolve this problem? The fuller logs below may help.
Thanks.
---------------
May 12 09:46:24.392 [Notice] Tor v0.2.2.35 (git-b04388f9e7546a9f). This is
experimental software. Do not rely on it for strong anonymity. (Running on
Linux i686)
May 12 09:46:24.395 [Notice] Initialized libevent version 2.0.18-stable using
method epoll. Good.
May 12 09:46:24.396 [Notice] Opening Socks listener on 127.0.0.1:0
May 12 09:46:24.397 [Notice] Socks listener listening on port 50364.
May 12 09:46:24.397 [Notice] Opening Control listener on 127.0.0.1:0
May 12 09:46:24.398 [Notice] Control listener listening on port 43936.
May 12 09:46:24.398 [Notice] Parsing GEOIP file ./Data/Tor/geoip.
May 12 09:46:29.102 [Notice] OpenSSL OpenSSL 1.0.1b 26 Apr 2012 looks like
version 0.9.8m or later; I will try SSL_OP to enable renegotiation
May 12 09:46:29.103 [Notice] We now have enough directory information to build
circuits.
May 12 09:46:29.103 [Notice] Bootstrapped 80%: Connecting to the Tor network.
May 12 09:46:29.103 [Notice] New control connection opened.
May 12 09:46:29.104 [Notice] Bootstrapped 85%: Finishing handshake with first
hop.
May 12 09:47:06.903 [Debug] tor_version_is_obsolete(): Checking whether version
'0.2.2.35' is in
'0.2.1.32,0.2.2.35,0.2.3.10-alpha,0.2.3.11-alpha,0.2.3.12-alpha,0.2.3.13-alpha,0.2.3.14-alpha,0.2.3.15-alpha'
May 12 09:47:06.906 [Info] handle_control_takeownership(): Control connection 9
has taken ownership of this Tor instance.
May 12 09:47:29.073 [Info] update_consensus_router_descriptor_downloads(): 0
router descriptors downloadable. 0 delayed; 2897 present (0 of those were in
old_routers); 0 would_reject; 2 wouldnt_use; 0 in progress.
May 12 09:47:29.075 [Info] mark_my_descriptor_dirty(): Decided to publish new
relay descriptor: time for new descriptor
May 12 09:47:29.075 [Info] routerlist_remove_old_routers(): We have 2897 live
routers and 0 old router descriptors.
May 12 09:47:34.076 [Debug] circuit_build_times_add_time(): Adding circuit
build time 2147483646
May 12 09:47:34.077 [Info] circuit_build_times_get_xm(): Xm mode #0: 2675 6
May 12 09:47:34.078 [Info] circuit_build_times_set_timeout_worker(): Circuit
build timeout of 48449808ms is beyond the maximum build time we have ever
observed. Capping it to 32175ms.
May 12 09:47:34.079 [Info] circuit_build_times_set_timeout_worker(): Circuit
build measurement period of 2147483647ms is more than twice the maximum build
time we have ever observed. Capping it to 64350ms.
May 12 09:47:34.079 [Info] circuit_build_times_set_timeout(): Set circuit build
timeout to 32s (32175.000000ms, 64350.000000ms, Xm: 2675, a: 0.164156, r:
0.702128) based on 564 circuit times
May 12 09:47:34.080 [Info] circuit_expire_building(): Abandoning circ 0 (state
2:connecting to server, purpose 13)
May 12 09:47:34.081 [Info] exit circ (length 3, last hop RoxSoft):
Ramsgate(closed) $94FE9A780109D3C5856A7A2B3333329B8F31A23C(closed)
RoxSoft(closed)
May 12 09:47:34.081 [Info] circuit_build_failed(): Our circuit died before the
first hop with no connection
May 12 09:47:34.156 [Debug] entry_guard_register_connect_status(): Failed to
connect to unreachable entry guard 'Ramsgate'
(896FCE19CB53A73A21DC874977C06B28FC9A8BBA). It has been unreachable since
2012-05-12 07:40:01.
May 12 09:47:34.160 [Debug] router_set_status(): Marking router
$896FCE19CB53A73A21DC874977C06B28FC9A8BBA=Ramsgate at 38.229.70.61 as down.
May 12 09:47:34.161 [Debug] count_usable_descriptors(): 2894 usable, 2894
present.
May 12 09:47:35.104 [Debug] circuit_build_times_add_time(): Adding circuit
build time 2147483646
May 12 09:47:35.106 [Info] circuit_build_times_get_xm(): Xm mode #0: 2675 6
May 12 09:47:35.106 [Info] circuit_build_times_set_timeout_worker(): Circuit
build timeout of 49611125ms is beyond the maximum build time we have ever
observed. Capping it to 32175ms.
May 12 09:47:35.107 [Info] circuit_build_times_set_timeout_worker(): Circuit
build measurement period of 2147483647ms is more than twice the maximum build
time we have ever observed. Capping it to 64350ms.
May 12 09:47:35.108 [Info] circuit_build_times_set_timeout(): Set circuit build
timeout to 32s (32175.000000ms, 64350.000000ms, Xm: 2675, a: 0.163760, r:
0.702655) based on 565 circuit times
May 12 09:47:35.108 [Info] circuit_expire_building(): Abandoning circ 0 (state
2:connecting to server, purpose 13)
May 12 09:47:35.109 [Info] exit circ (length 3, last hop RoxSoft):
Ramsgate(closed) fejk(closed) RoxSoft(closed)
May 12 09:47:35.109 [Info] circuit_build_failed(): Our circuit died before the
first hop with no connection
May 12 09:47:35.109 [Debug] entry_guard_register_connect_status(): Failed to
connect to unreachable entry guard 'Ramsgate'
(896FCE19CB53A73A21DC874977C06B28FC9A8BBA). It has been unreachable since
2012-05-12 07:40:01.
May 12 09:47:35.110 [Debug] router_set_status(): Marking router
$896FCE19CB53A73A21DC874977C06B28FC9A8BBA=Ramsgate at 38.229.70.61 as down.
May 12 09:47:35.111 [Debug] count_usable_descriptors(): 2894 usable, 2894
present.
May 12 09:47:35.111 [Debug] circuit_remove_handled_ports(): Port 80 is not
handled.
May 12 09:47:35.112 [Info] circuit_predict_and_launch_new(): Have 3 clean circs
(2 internal), need another exit circ.
May 12 09:47:35.112 [Debug] new_route_len(): Chosen route length 3 (2894/2897
routers suitable).
May 12 09:47:35.112 [Info] choose_good_exit_server_general(): Found 1 servers
that might support 0/0 pending connections.
May 12 09:47:35.113 [Debug] circuit_remove_handled_ports(): Port 80 is not
handled.
May 12 09:47:35.113 [Debug] smartlist_choose_by_bandwidth_weights(): Choosing
node for rule weight as exit based on weights Wg=0.628700 Wm=1.000000
We=1.000000 Wd=0.628700 with total bw 5000.000000
May 12 09:47:35.114 [Info] choose_good_exit_server_general(): Chose exit server
'$E6D515A77E068D3504FEDCD3DFB1ED0756437741=RoxSoft at 80.177.246.35'
May 12 09:47:35.114 [Debug] onion_extend_cpath(): Path is 0 long; we want 3
May 12 09:47:35.115 [Debug] onion_extend_cpath(): Chose router
$43BE706E24143AB6B3B86DBF7CD4FDE1E0C4CAF1~nixnix at 149.9.0.58 for hop 1 (exit
is RoxSoft)
May 12 09:47:35.115 [Debug] onion_extend_cpath(): Path is 1 long; we want 3
May 12 09:47:35.116 [Debug] choose_good_middle_server(): Contemplating
intermediate hop: random choice.
May 12 09:47:35.116 [Debug] smartlist_choose_by_bandwidth_weights(): Choosing
node for rule weight as middle node based on weights Wg=0.311600 Wm=1.000000
We=0.000000 Wd=0.185600 with total bw 3297241353.599997
May 12 09:47:35.203 [Debug] onion_extend_cpath(): Chose router
$A0914B17C661D268F9C644F250FD11CB7DE40531~EveryLittleThing at 93.174.93.82 for
hop 2 (exit is RoxSoft)
May 12 09:47:35.207 [Debug] onion_extend_cpath(): Path is 2 long; we want 3
May 12 09:47:35.208 [Debug] onion_extend_cpath(): Chose router
$E6D515A77E068D3504FEDCD3DFB1ED0756437741~RoxSoft at 80.177.246.35 for hop 3
(exit is RoxSoft)
May 12 09:47:35.208 [Debug] onion_extend_cpath(): Path is complete: 3 steps long
May 12 09:47:35.209 [Debug] circuit_handle_first_hop(): Looking for firsthop
'149.9.0.58:9001'
May 12 09:47:35.210 [Info] circuit_handle_first_hop(): Next router is
[scrubbed]: Connection in progress; waiting.
May 12 09:47:35.210 [Debug] circuit_handle_first_hop(): connecting in progress
(or finished). Good.
May 12 09:47:36.105 [Debug] circuit_build_times_add_time(): Adding circuit
build time 2147483646
May 12 09:47:36.107 [Info] circuit_build_times_get_xm(): Xm mode #0: 2675 6
May 12 09:47:36.108 [Info] circuit_build_times_set_timeout_worker(): Circuit
build timeout of 50800279ms is beyond the maximum build time we have ever
observed. Capping it to 32175ms.
May 12 09:47:36.108 [Info] circuit_build_times_set_timeout_worker(): Circuit
build measurement period of 2147483647ms is more than twice the maximum build
time we have ever observed. Capping it to 64350ms.
May 12 09:47:36.109 [Info] circuit_build_times_set_timeout(): Set circuit build
timeout to 32s (32175.000000ms, 64350.000000ms, Xm: 2675, a: 0.163366, r:
0.703180) based on 566 circuit times
May 12 09:47:36.110 [Info] circuit_expire_building(): Abandoning circ 0 (state
2:connecting to server, purpose 13)
May 12 09:47:36.110 [Info] internal (high-uptime) circ (length 3, last hop
gurgle): nixnix(closed) gpfTOR4(closed) gurgle(closed)
May 12 09:47:36.111 [Info] circuit_build_failed(): Our circuit died before the
first hop with no connection
May 12 09:47:36.111 [Debug] entry_guard_register_connect_status(): Failed to
connect to unreachable entry guard 'nixnix'
(43BE706E24143AB6B3B86DBF7CD4FDE1E0C4CAF1). It has been unreachable since
2012-05-12 07:40:35.
May 12 09:47:36.112 [Debug] router_set_status(): Marking router
$43BE706E24143AB6B3B86DBF7CD4FDE1E0C4CAF1=nixnix at 149.9.0.58 as down.
The circuit building is definitely timing out. I'm no expert.
Socks listener listening on port 50364
Is this correct? Shouldn't it be Socks listening on port 9050; control
listener on port 9051 - or does that matter?
Are you using the same machine / same TBB installation at home as at the
cafe wifi?
How many times has this happened at home - is it a regular thing now?
If not, possible the home ISP server's just busy. How fast is your
connection?
If you haven't, try closing TBB, make sure that all Tor services are
stopped - then restart TBB. I've had Tor / TBB fail to connect in the
past & wasn't my ISP. Occasionally, reinstalling (or in this case,
re-extracting files to new folder) solved the problem. Have you looked
at TBB Firefox network proxy settings to check they are correct?
_______________________________________________
tor-talk mailing list
[email protected]
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk
