Opened 2 years ago

Closed 23 months ago

#23784 closed defect (not a bug)

Loading relay information failed (connection timeout - 109.163.234.9:443)

Reported by: Nom Owned by:
Priority: High Milestone:
Component: Core Tor/Tor Version: Tor: unspecified
Severity: Normal Keywords:
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

on debian wheezy only version 6.5 will connect. newer versions will not connect, using anything like obfuscated, bridges, etc... taking into consideration that the clock is correct, the error log as follows:

10/08/2017 16:16:46.700 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
10/08/2017 16:16:46.700 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
10/08/2017 16:16:46.700 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
10/08/2017 16:16:46.700 [NOTICE] Opening Socks listener on 127.0.0.1:9150
10/08/2017 16:16:46.700 [NOTICE] Renaming old configuration file to "/home/user/Downloads/tor-browser_en-US/Browser/TorBrowser/Data/Tor/torrc.orig.1"
10/08/2017 16:16:47.200 [NOTICE] Bootstrapped 5%: Connecting to directory server
10/08/2017 16:16:47.400 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server
10/08/2017 16:16:47.900 [NOTICE] Bootstrapped 15%: Establishing an encrypted directory connection
10/08/2017 16:16:48.000 [NOTICE] Bootstrapped 20%: Asking for networkstatus consensus
10/08/2017 16:16:48.200 [NOTICE] Bootstrapped 25%: Loading networkstatus consensus
10/08/2017 16:16:52.800 [WARN] Received directory with skewed time (DIRSERV:131.188.40.189:443): It seems that our clock is ahead by 7 hours, 59 minutes, or that theirs is behind. Tor requires an accurate clock to work: please check your time, timezone, and date settings.
10/08/2017 16:16:52.800 [NOTICE] I learned some more directory information, but not enough to build a circuit: We have no usable consensus.
10/08/2017 16:17:05.800 [NOTICE] Bootstrapped 40%: Loading authority key certs
10/08/2017 16:17:05.900 [WARN] Received directory with skewed time (DIRSERV:131.188.40.189:443): It seems that our clock is ahead by 7 hours, 59 minutes, or that theirs is behind. Tor requires an accurate clock to work: please check your time, timezone, and date settings.
10/08/2017 16:17:05.900 [NOTICE] Bootstrapped 45%: Asking for relay descriptors
10/08/2017 16:17:05.900 [NOTICE] I learned some more directory information, but not enough to build a circuit: We need more microdescriptors: we have 0/6709, and can only build 0% of likely paths. (We have 0% of guards bw, 0% of midpoint bw, and 0% of exit bw = 0% of path bw.)
10/08/2017 16:17:06.300 [NOTICE] Bootstrapped 50%: Loading relay descriptors
10/08/2017 16:17:06.400 [NOTICE] I learned some more directory information, but not enough to build a circuit: We need more microdescriptors: we have 0/6709, and can only build 0% of likely paths. (We have 0% of guards bw, 0% of midpoint bw, and 0% of exit bw = 0% of path bw.)
10/08/2017 16:18:10.600 [WARN] Problem bootstrapping. Stuck at 50%: Loading relay descriptors. (Connection timed out; TIMEOUT; count 10; recommendation warn; host ABF7FBF389C9A747938B639B20E80620B460B2A9 at 109.163.234.9:443)
10/08/2017 16:18:10.600 [WARN] 9 connections have failed:
10/08/2017 16:18:10.600 [WARN] 9 connections died in state connect()ing with SSL state (No SSL object)
10/08/2017 16:18:46.500 [WARN] Problem bootstrapping. Stuck at 50%: Loading relay descriptors. (Connection timed out; TIMEOUT; count 11; recommendation warn; host 587E0A9552E4274B251F29B5B2673D38442EE4BF at 95.130.12.119:443)
10/08/2017 16:18:46.500 [WARN] 10 connections have failed:
10/08/2017 16:18:46.500 [WARN] 10 connections died in state connect()ing with SSL state (No SSL object)
10/08/2017 16:18:46.500 [WARN] Problem bootstrapping. Stuck at 50%: Loading relay descriptors. (Connection timed out; TIMEOUT; count 12; recommendation warn; host 8672E8A01B4D3FA4C0BBE21C740D4506302EA487 at 188.166.23.127:443)
10/08/2017 16:18:46.500 [WARN] 11 connections have failed:
10/08/2017 16:18:46.500 [WARN] 11 connections died in state connect()ing with SSL state (No SSL object)
10/08/2017 16:18:46.500 [NOTICE] Closing no-longer-configured Socks listener on 127.0.0.1:9150
10/08/2017 16:18:46.500 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
10/08/2017 16:18:46.500 [NOTICE] Closing old Socks listener on 127.0.0.1:9150
10/08/2017 16:18:46.500 [NOTICE] Delaying directory fetches: DisableNetwork is set.

Child Tickets

Change History (4)

comment:1 in reply to:  description Changed 2 years ago by arma

Replying to Nom:

10/08/2017 16:16:52.800 [WARN] Received directory with skewed time (DIRSERV:131.188.40.189:443): It seems that our clock is ahead by 7 hours, 59 minutes, or that theirs is behind. Tor requires an accurate clock to work: please check your time, timezone, and date settings.

Sounds like you are mistaken that your clock is correct.

If the clock is correct, then most likely your time zone is incorrect.

comment:2 Changed 2 years ago by Nom

It does not explain why v6.5 connects and not later ones. I changed the time zone to the actual one which is dangerous, even though the clock is correct, but the results are the same:

10/10/2017 23:04:24.200 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
10/10/2017 23:04:24.200 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
10/10/2017 23:04:24.200 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
10/10/2017 23:04:24.200 [NOTICE] Opening Socks listener on 127.0.0.1:9150
10/10/2017 23:04:25.600 [NOTICE] Bootstrapped 5%: Connecting to directory server
10/10/2017 23:04:25.600 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server
10/10/2017 23:04:26.100 [NOTICE] Bootstrapped 15%: Establishing an encrypted directory connection
10/10/2017 23:04:26.100 [NOTICE] Bootstrapped 20%: Asking for networkstatus consensus
10/10/2017 23:04:26.100 [NOTICE] Bootstrapped 25%: Loading networkstatus consensus
10/10/2017 23:04:27.400 [NOTICE] Bootstrapped 45%: Asking for relay descriptors
10/10/2017 23:04:27.400 [NOTICE] I learned some more directory information, but not enough to build a circuit: We need more microdescriptors: we have 2227/6627, and can only build 4% of likely paths. (We have 36% of guards bw, 35% of midpoint bw, and 36% of exit bw = 4% of path bw.)
10/10/2017 23:04:28.200 [NOTICE] Bootstrapped 52%: Loading relay descriptors
10/10/2017 23:04:29.100 [NOTICE] Bootstrapped 59%: Loading relay descriptors
10/10/2017 23:04:29.300 [NOTICE] Bootstrapped 69%: Loading relay descriptors
10/10/2017 23:04:29.500 [NOTICE] Bootstrapped 76%: Loading relay descriptors
10/10/2017 23:04:29.600 [NOTICE] Bootstrapped 80%: Connecting to the Tor network
10/10/2017 23:04:30.000 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.
10/10/2017 23:04:31.000 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.
10/10/2017 23:04:32.000 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.
10/10/2017 23:04:33.000 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.
10/10/2017 23:04:34.000 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.
10/10/2017 23:04:34.800 [NOTICE] Bootstrapped 85%: Finishing handshake with first hop
10/10/2017 23:04:35.000 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.
10/10/2017 23:04:36.000 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.
10/10/2017 23:04:37.000 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.
10/10/2017 23:04:38.000 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.
10/10/2017 23:04:39.000 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.
10/10/2017 23:04:40.000 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.
10/10/2017 23:04:41.000 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.
10/10/2017 23:04:42.000 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.
10/10/2017 23:04:43.000 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.
10/10/2017 23:04:44.000 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.
10/10/2017 23:04:45.000 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.
10/10/2017 23:04:46.000 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.
10/10/2017 23:04:47.000 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.
10/10/2017 23:04:48.000 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.
10/10/2017 23:04:49.000 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.
10/10/2017 23:04:50.000 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.
10/10/2017 23:04:51.000 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.
10/10/2017 23:04:52.000 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.
10/10/2017 23:04:53.000 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.
10/10/2017 23:04:54.000 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.
10/10/2017 23:04:55.000 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.
10/10/2017 23:04:56.000 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.
10/10/2017 23:04:57.000 [WARN] Failed to find node for hop 0 of our path. Discarding this circuit.
10/10/2017 23:04:58.900 [WARN] Problem bootstrapping. Stuck at 85%: Finishing handshake with first hop. (No route to host; NOROUTE; count 1; recommendation warn; host 587E0A9552E4274B251F29B5B2673D38442EE4BF at 95.130.12.119:443)
10/10/2017 23:04:58.900 [WARN] 2 connections have failed:
10/10/2017 23:04:58.900 [WARN] 2 connections died in state connect()ing with SSL state (No SSL object)
10/10/2017 23:05:08.000 [NOTICE] Closing no-longer-configured Socks listener on 127.0.0.1:9150
10/10/2017 23:05:08.000 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
10/10/2017 23:05:08.000 [NOTICE] Closing old Socks listener on 127.0.0.1:9150
10/10/2017 23:05:08.000 [NOTICE] Delaying directory fetches: DisableNetwork is set.

comment:3 Changed 2 years ago by Nom

You were right. I set network time to "on", as the clock would not be correct after changing the zone. Now TOR opens immediately.

Thanks for your help.

comment:4 Changed 23 months ago by nickm

Component: - Select a componentCore Tor/Tor
Resolution: not a bug
Status: newclosed

Thanks for the speedy reply!

Note: See TracTickets for help on using tickets.