Been at it for 8 days, rebooted the node 3 times.
Why not have the option to first sync on clearnet.?
Tor logs
Attaching to tor
tor | Sep 09 13:48:01.000 [notice] Guard torstreiktnet ($0C93559D6D7E95B41561424345B0B176FBE66F00) is failing more circuits than usual. Most likely this means the Tor network is overloaded. Success counts are 101/202. Use counts are 2/5. 177 circuits completed, 3 were unusable, 73 collapsed, and 89 timed out. For reference, your timeout cutoff is 143 seconds.
tor | Sep 09 13:48:10.000 [notice] Failed to find node for hop #1 of our path. Discarding this circuit.
tor | Sep 09 13:57:45.000 [notice] Guard Casper03 ($B4E8E0047B36CF1FA76E5C61091D8A479227D81C) 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 16/21. Success counts are 107/218. 197 circuits completed, 1 were unusable, 90 collapsed, and 106 timed out. For reference, your timeout cutoff is 199 seconds.
tor | Sep 09 13:57:58.000 [notice] Have tried resolving or connecting to address ‘[scrubbed]’ at 3 different places. Giving up.
tor | Sep 09 13:58:23.000 [notice] Have tried resolving or connecting to address ‘[scrubbed]’ at 3 different places. Giving up.
tor | Sep 09 13:58:42.000 [notice] Have tried resolving or connecting to address ‘[scrubbed]’ at 3 different places. Giving up.
tor | Sep 09 14:04:11.000 [notice] Failed to find node for hop #1 of our path. Discarding this circuit.
tor | Sep 09 14:10:48.000 [notice] Have tried resolving or connecting to address ‘[scrubbed]’ at 3 different places. Giving up.
tor | Sep 09 14:19:19.000 [notice] Have tried resolving or connecting to address ‘[scrubbed]’ at 3 different places. Giving up.
tor | Sep 09 14:25:57.000 [notice] Have tried resolving or connecting to address ‘[scrubbed]’ at 3 different places. Giving up.
Attaching to tor
tor | Sep 12 03:57:10.000 [notice] While not bootstrapping, fetched this many bytes: 3170318 (consensus network-status fetch); 1864360 (microdescriptor fetch)
tor | Sep 12 03:57:10.000 [notice] Average packaged cell fullness: 74.856%. TLS write overhead: 4%
tor | Sep 12 04:05:22.000 [notice] Failed to find node for hop #1 of our path. Discarding this circuit.
tor | Sep 12 04:09:02.000 [notice] No circuits are opened. Relaxed timeout for circuit 277764 (a Measuring circuit timeout 3-hop circuit in state waiting to see how other guards perform with channel state open) to 65443ms. However, it appears the circuit has timed out anyway. [467 similar message(s) suppressed in last 3660 seconds]
tor | Sep 12 04:17:55.000 [notice] Have tried resolving or connecting to address ‘[scrubbed]’ at 3 different places. Giving up.
tor | Sep 12 04:20:14.000 [notice] Failed to find node for hop #1 of our path. Discarding this circuit.
tor | Sep 12 04:22:18.000 [notice] Your network connection speed appears to have changed. Resetting timeout to 60000ms after 18 timeouts and 1000 buildtimes.
tor | Sep 12 04:37:06.000 [notice] Failed to find node for hop #1 of our path. Discarding this circuit.
tor | Sep 12 04:38:12.000 [notice] Have tried resolving or connecting to address ‘[scrubbed]’ at 3 different places. Giving up.
App logs
bitcoin
tor_server_1 | Sep 19 14:40:20.000 [notice] No circuits are opened. Relaxed timeout for circuit 320411 (a Hidden service: Establishing introduction point 4-hop circuit in state doing handshakes with channel state open) to 60000ms. However, it appears the circuit has timed out anyway. [83 similar message(s) suppressed in last 4320 seconds]
tor_server_1 | Sep 19 15:33:36.000 [notice] Your network connection speed appears to have changed. Resetting timeout to 60000ms after 18 timeouts and 1000 buildtimes.
tor_server_1 | Sep 19 15:49:50.000 [notice] Your network connection speed appears to have changed. Resetting timeout to 60000ms after 18 timeouts and 369 buildtimes.
tor_server_1 | Sep 19 15:49:51.000 [notice] No circuits are opened. Relaxed timeout for circuit 322301 (a Measuring circuit timeout 4-hop circuit in state doing handshakes with channel state open) to 60000ms. However, it appears the circuit has timed out anyway. [151 similar message(s) suppressed in last 4200 seconds]
tor_server_1 | Sep 19 16:08:55.000 [notice] Failed to find node for hop #1 of our path. Discarding this circuit.
tor_server_1 | Sep 19 16:08:55.000 [notice] Our circuit 0 (id: 323153) died due to an invalid selected path, purpose Hidden service: Establishing introduction point. This may be a torrc configuration issue, or a bug. [1 similar message(s) suppressed in last 6660 seconds]
tor_server_1 | Sep 19 16:43:51.000 [notice] Your network connection speed appears to have changed. Resetting timeout to 60000ms after 18 timeouts and 677 buildtimes.
tor_server_1 | Sep 19 16:47:12.000 [notice] Heartbeat: Tor’s uptime is 7 days 12:00 hours, with 26 circuits open. I’ve sent 1.93 GB and received 902.32 MB. I’ve received 0 connections on IPv4 and 0 on IPv6. I’ve made 35406 connections with IPv4 and 0 with IPv6.
tor_server_1 | Sep 19 16:47:12.000 [notice] While bootstrapping, fetched this many bytes: 615646 (consensus network-status fetch); 14094 (authority cert fetch); 5280470 (microdescriptor fetch)
tor_server_1 | Sep 19 16:47:12.000 [notice] While not bootstrapping, fetched this many bytes: 5505679 (consensus network-status fetch); 1776 (authority cert fetch); 3213754 (microdescriptor fetch)
tor_server_1 | Sep 19 16:49:56.000 [notice] No circuits are opened. Relaxed timeout for circuit 324109 (a Hidden service: Establishing introduction point 4-hop circuit in state doing handshakes with channel state open) to 146758ms. However, it appears the circuit has timed out anyway. [69 similar message(s) suppressed in last 3660 seconds]
tor_server_1 | Sep 19 16:59:17.000 [notice] Your network connection speed appears to have changed. Resetting timeout to 60000ms after 18 timeouts and 255 buildtimes.
tor_server_1 | Sep 19 17:03:44.000 [notice] Failed to find node for hop #1 of our path. Discarding this circuit.
tor_server_1 | Sep 19 17:09:14.000 [notice] Failed to find node for hop #1 of our path. Discarding this circuit.
tor_server_1 | Sep 19 17:09:14.000 [notice] Our circuit 0 (id: 324718) died due to an invalid selected path, purpose Hidden service: Establishing introduction point. This may be a torrc configuration issue, or a bug. [1 similar message(s) suppressed in last 360 seconds]
tor_server_1 | Sep 19 17:17:11.000 [warn] Guard TheGreatKing ($0824D7C7FB117D5C6AC01581FD798E670C37C804) is failing a very large amount of circuits. Most likely this means the Tor network is overloaded, but it could also mean an attack against you or potentially the guard itself. Success counts are 105/211. Use counts are 83/88. 161 circuits completed, 2 were unusable, 54 collapsed, and 101 timed out. For reference, your timeout cutoff is 113 seconds.
tor_server_1 | Sep 19 17:19:12.000 [notice] Your network connection speed appears to have changed. Resetting timeout to 60000ms after 18 timeouts and 377 buildtimes.
tor_server_1 | Sep 19 17:27:17.000 [notice] Your network connection speed appears to have changed. Resetting timeout to 60000ms after 18 timeouts and 186 buildtimes.
tor_server_1 | Sep 19 17:31:35.000 [notice] Failed to find node for hop #1 of our path. Discarding this circuit.
tor_server_1 | Sep 19 17:31:37.000 [notice] Guard QuakeVISOR ($117286A3F5DF7275F2EB1F28D8AAC72772D84939) is failing more circuits than usual. Most likely this means the Tor network is overloaded. Success counts are 116/166. Use counts are 2/2. 147 circuits completed, 0 were unusable, 32 collapsed, and 107 timed out. For reference, your timeout cutoff is 60 seconds.
tor_server_1 | Sep 19 17:49:32.000 [notice] Your network connection speed appears to have changed. Resetting timeout to 60000ms after 18 timeouts and 232 buildtimes.
tor_server_1 | Sep 19 17:50:21.000 [notice] No circuits are opened. Relaxed timeout for circuit 325805 (a Hidden service: Pre-built vanguard circuit 3-hop circuit in state waiting to see how other guards perform with channel state open) to 60000ms. However, it appears the circuit has timed out anyway. [68 similar message(s) suppressed in last 3660 seconds]
tor_server_1 | Sep 19 17:58:55.000 [notice] Failed to find node for hop #1 of our path. Discarding this circuit.
tor_server_1 | Sep 19 18:11:30.000 [notice] Your network connection speed appears to have changed. Resetting timeout to 60000ms after 18 timeouts and 387 buildtimes.
tor_server_1 | Sep 19 18:19:30.000 [notice] Failed to find node for hop #1 of our path. Discarding this circuit.
tor_server_1 | Sep 19 18:19:30.000 [notice] Our circuit 0 (id: 326750) died due to an invalid selected path, purpose Hidden service: Establishing introduction point. This may be a torrc configuration issue, or a bug. [2 similar message(s) suppressed in last 2880 seconds]
tor_server_1 | Sep 19 18:32:09.000 [notice] Your network connection speed appears to have changed. Resetting timeout to 60000ms after 18 timeouts and 406 buildtimes.
tor_server_1 | Sep 19 18:39:21.000 [notice] Failed to find node for hop #1 of our path. Discarding this circuit.
tor_server_1 | Sep 19 18:40:38.000 [notice] Your network connection speed appears to have changed. Resetting timeout to 60000ms after 18 timeouts and 120 buildtimes.
Attaching to tor
tor | Sep 19 18:09:01.000 [notice] Your network connection speed appears to have changed. Resetting timeout to 60000ms after 18 timeouts and 1000 buildtimes.
tor | Sep 19 18:21:54.000 [notice] Have tried resolving or connecting to address ‘[scrubbed]’ at 3 different places. Giving up.
tor | Sep 19 18:23:56.000 [notice] No circuits are opened. Relaxed timeout for circuit 486310 (a Measuring circuit timeout 3-hop circuit in state waiting to see how other guards perform with channel state open) to 114370ms. However, it appears the circuit has timed out anyway. [15 similar message(s) suppressed in last 3780 seconds]
tor | Sep 19 18:26:15.000 [notice] Failed to find node for hop #1 of our path. Discarding this circuit.
tor | Sep 19 18:26:44.000 [notice] Have tried resolving or connecting to address ‘[scrubbed]’ at 3 different places. Giving up.
tor | Sep 19 18:27:07.000 [notice] Have tried resolving or connecting to address ‘[scrubbed]’ at 3 different places. Giving up.
tor | Sep 19 18:34:49.000 [notice] Failed to find node for hop #1 of our path. Discarding this circuit.
tor | Sep 19 18:39:39.000 [notice] Failed to find node for hop #1 of our path. Discarding this circuit.
tor | Sep 19 18:46:28.000 [notice] Have tried resolving or connecting to address ‘[scrubbed]’ at 3 different places. Giving up.
I’m getting similar problems trying to bootsrap a brand new node version 0.5.4. It’s not a 100% connection failure, since I was able to sync up to 3%. Using basic Debian linux:
tor_proxy | Feb 29 17:09:38.000 [notice] Failed to find node for hop #1 of our path. Discarding this circuit.
tor_proxy | Feb 29 17:09:38.000 [notice] Our circuit 0 (id: 80) died due to an invalid selected path, purpose Hidden service: Pre-built vanguard circuit. This may be a torrc configuration issue, or a bug.
tor_proxy | Feb 29 17:12:12.000 [notice] Failed to find node for hop #1 of our path.