Opened 14 months ago

Closed 6 months ago

#27134 closed defect (user disappeared)

connect issue

Reported by: ElecLib Owned by: phoul
Priority: Medium Milestone:
Component: Community/Tor Support Version: Tor: unspecified
Severity: Normal Keywords:
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

8/14/2018 9:03:13 AM.000 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server
8/14/2018 9:03:13 AM.000 [NOTICE] Bootstrapped 15%: Establishing an encrypted directory connection
8/14/2018 9:03:13 AM.000 [NOTICE] Bootstrapped 20%: Asking for networkstatus consensus
8/14/2018 9:03:13 AM.000 [NOTICE] Bootstrapped 25%: Loading networkstatus consensus
8/14/2018 9:03:15 AM.600 [WARN] Our clock is 56 minutes, 47 seconds behind the time published in the consensus network status document (2018-08-14 08:00:00 UTC). Tor needs an accurate clock to work correctly. Please check your time and date settings!
8/14/2018 9:03:15 AM.600 [WARN] Received microdesc flavor consensus with skewed time (CONSENSUS): It seems that our clock is behind by 56 minutes, 47 seconds, or that theirs is ahead. Tor requires an accurate clock to work: please check your time, timezone, and date settings.
8/14/2018 9:03:15 AM.600 [WARN] Problem bootstrapping. Stuck at 25%: Loading networkstatus consensus. (Clock skew -3407 in microdesc flavor consensus from CONSENSUS; CLOCK_SKEW; count 1; recommendation warn; host ? at ?)
8/14/2018 9:03:15 AM.600 [NOTICE] I learned some more directory information, but not enough to build a circuit: We have no recent usable consensus.
8/14/2018 9:03:15 AM.600 [NOTICE] Closing no-longer-configured Socks listener on 127.0.0.1:9150
8/14/2018 9:03:15 AM.600 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
8/14/2018 9:03:15 AM.600 [NOTICE] Closing old Socks listener on 127.0.0.1:9150
8/14/2018 9:03:16 AM.600 [NOTICE] Delaying directory fetches: DisableNetwork is set.

Child Tickets

Change History (2)

comment:1 Changed 14 months ago by rl1987

Component: - Select a componentCommunity/Tor Support
Owner: set to phoul
8/14/2018 9:03:15 AM.600 [WARN] Our clock is 56 minutes, 47 seconds behind the time published in the consensus network status document (2018-08-14 08:00:00 UTC). Tor needs an accurate clock to work correctly. Please check your time and date settings!
8/14/2018 9:03:15 AM.600 [WARN] Received microdesc flavor consensus with skewed time (CONSENSUS): It seems that our clock is behind by 56 minutes, 47 seconds, or that theirs is ahead. Tor requires an accurate clock to work: please check your time, timezone, and date settings. 

Did you check that time and timezone are correct on your machine?

comment:2 Changed 6 months ago by phoul

Resolution: user disappeared
Status: newclosed
Note: See TracTickets for help on using tickets.